Some years ago I used Emacs for a while, and now setting it up again, following a Clojure-Course. All the little problems are coming back, like the meta-key (option) which prevents me from typing [ and ].
Checking out Clojure this morning. Cider didn’t work on Emacs following www.braveclojure.com/basic-ema… I had to throw out cider from init.el, and package-install it anew. stackoverflow.com/questions…
Googling for my old nickname “Kfeeras” led me to a Reddit Thread from 2021. They posted an infographic I made 2010-ish about Oil (university-assignment). No idea how they found it. It’s not really sticking to any rules for infographics. I just wanted to do something with Cinema4D.
While lots of people seemed to have lots of more free time during the pandemic, I had almost no free time during the lockdowns and restrictions.
I need 10 minutes by bike to the bubble-tea-store and back.
It’s one of either “using H3 because it’s too small for H1” (styling) or “there can only be one H1 on a page” (SEO-crap).
In my time interviewing at my current work (Junior–Senior Front-End-Devs), I didn’t have one applicant using H1-H6-Tags correctly.
Game-Dev: Have to remind myself that the engine doesn’t matter at first. Use something quick and known. When the game-prototype/idea is there, switching to another is not an issue.
Checking out Defold-Engine. Nice for 2D. Good showcase-game poki.com/en/g/zoom…
Pfusch to Talk
NTS: use Joey Jo-Jo Junior Shabadoo somewhere
.
💻 Not sure which kind of modal-component is more DX-friendly.
1: One which is used programmatically, like
modal = new Modal(); modal.open(content);
2: One which is used declaratively like
{modalShouldOpen ? <modal content="content"/> : null}
Currently using it the first way.
On Peppa Pig there are „normal“ doctors and vets.
Last day of therapy today after almost 2 years.
💻 One thing I would love to see in Lit: The option to make a component without creating a custom element. It would be the same, but without any shadow-dom. It could just render whatever is inside render() and have a div as root. Although usage then couldn’t be declarative in HTML, but would have to happen via manual instancing. This could be useful for components that don’t need to be custom elements, but still could utilise the overall architecture. of the project.
💻 Lit mostly provides a security-layer for interpreting HTML (Lit-HTML), and a couple of helper-features for element-classes. Especially TypeScript-Support. One thing that is non-trivial IMHO is to know, when elements will re-render. Not always straightforward, particularly with nesting. State on parent changes and triggers re-render. Will grandchildren re-render or not? With ReactJS you never ever have to worry about this.
💻 I really enjoy working with WebComponents/Lit. If I made a list of all the pros and cons, there wouldn’t be much on the “pro” side, and lots on “con”, but still I enjoy the simplicity. The one killer-con is, that it’s probably not very useful to have on my CV.
💻 Lit-ClassMaps are more useful than expected. Also I increased the print-width in my editor and project, since nested templates can get very indent-y and super-hard to read. From 80 to 140. Why not?
This is a nice ASCII-Zine. www.legowelt.org/shadowwol… Thinking about doing a punkrock-copy-paste-style zine for DevLids.