Ava

setTimeout makes me feel like I'm punishing my JavaScript.

"Go sit in the corner for 3000 milliseconds."

We know that LLMs aren't a path to general intelligence right?

Like the entire stock market is propped up on the promise that labor is going to zero and not that people actually believe we are nearing AGI,

Right??

Nice of them to give the crows free rocks.

GitHub - lala-hakobyan/front-end-debugging-handbook: A comprehensive guide to debugging tools for modern, complex front-end applications. This handbook provides practical, real-world guidance on a com... A comprehensive guide to debugging tools for modern, complex front-end applications. This handbook provides practical, real-world guidance on a complete suite of tools, from Chrome DevTools and fra...

Ever wanted a comprehensive guide to DevTools and debugging front ends? Check out this ebook that Lala Hakobyan just launched:

github.com/lala-hakobya...

I’m impressed!!

Server side JavaScript was a mistake

I like my automation to be deterministic, not probabilistic.

Four slightly overlapping stacked modal windows with back arrow buttons. Each subsequent modal has less shading than the previous.

I blame this UI pattern on two historical development trends.

Poor form persistence, causing users to distrust the back button.

And SPAs abandoning browser history altogether and reimplementing it in UI.

git commit -m "When in doubt, setTimeout"

The top hn comment on a post about rationalist cults being positive, is so on brand it's like 360° irony.

If I was an accessibility audit vendor, I would submit a list of specific, concrete tasks to fix, and not whatever the hell I was just given.

Were the instructions unclear?

Why isn't it strawberry flavor?

Not extensively, just wrapping a design system component library so it's lower specificity for consumers and they can inject the styles between layers if need be.

Luckily they're also really good at losing wars.

😍

Meta💩

look, sometimes people shouldn’t blog — this is a wild pivot from me I know

DIVS

Gonna tell my boss I'm making accessible, server rendered pages for the LLMs.

Sounds like gender dysphoria.

Temporal is gonna arrive before the React Compiler.

Adam plays clawhammer?? This is awesome.

Meticulously debugging headers only to find out I'm hitting the wrong API.

DIVS!

The emotional whiplash that is Double Zeta Gundam.

じじじ Grandfather clock

But I find writing CSS directly in JS cumbersome and not a worthwhile trade-off for this terseness.

CSS Custom Properties (vars) are reactive, and you can pass values from JS to CSS via data attrs or style tags directly on elements.

I think that one of the "conveniences" that advocates for CSS-in-JS like is using JavaScript values to determine CSS. You can have terser syntax with a lib, and if these values are known at build time you can use a lib that doesn't introduce a runtime cost.

If you need stricter scoping there are things like CSS Modules which will give you a unique hash name. Admittedly then you are dependent on that, but the file content is just regular CSS and much easier to migrate away from if necessary.

With collocation I find scoping much less of an issue than we use to deal with in CSS. If your components have unique names you can have a top level class name scope and then whatever selectors you prefer within that.