Here it is broken out for readability.

Ok, here is my version 😉

I’ve been asking «Why is there no way to produce "robust code" by simply writing robust code» for a very long time now. I wish I had insight.

Safari is the worst when it comes to developer experience! I also feel this pain when targeting Safari/Webkit.

New AI MCP/Agent: fetch random URLs till you get a 200 response.

Claude, go home, you’re drunk!

Do this for Iterators please! They have map, flatMap, filter, every, drop, take, find, some, reduce, and forEach

developer.mozilla.org/en-US/docs/W...

Called, “Monkey Patching” a very declarative code pattern. Issue is that without the tribal knowledge this is a surprising and frustrating thing to encounter. Debugging, a nightmare. And onboarding, nearly impossible. Hence an antipattern on std-lib/globals. I like the decorator pattern for this.

This has always bothered me. Especially since the Chrome browser handles the same work as an Electron app handles only to be ok but Electron gets a bad rap. Node does way more and doesn’t get half the flack Electron gets. It is not JS, HTML, or CSS. It is FUD. Bad actors making the tech look bad.

Not that I condone but the industry hiring relies more now on developer marketing then they do on developer skills. This incentivizes more garbage. Quality is not needed when it comes to showing hiring decision makers of your worth. Quantity is what they look for. Blame hiring.

I wish you could register custom tag names through importmap like we can with JS import.

JSX is awful, confusing, and useless without build steps (no more view source). It mixes languages in a terrible way making reasoning and context switching a horrible exercise. I much prefer how lit-html went about it using tagged template literals.

Bleeding edge means giving up on supporting Safari and using tech that the rest of the web industry supports but Apple refused to play nice with.

To this day I still never have issue with four spaced indents. If anything it incentivized me to make flatter code design choices.

I also think tabs are interesting as it allows the developer to choose their preference instead of forcing that preference on them.

The hill I’ll die on is ending \n

Have you considered breaking that up into smaller things with clear names? As is it lacks any clarity on what it does. This is very imperative code. Breaking it up makes it more declarative. Express what you want to do and push the how to do it into functions.