Zen is the way to use Firefox these days. Zero slop, great UX.

Hoppscotch?

Hah, I remember that metal-looking nav bar :)

This is deeply concerning. Stay safe ❤️

Okay, but I can still turn this stuff off because it is annoying...

Are they mostly just harassing you via the media, or full-on trying to sue you?

Yea, you're probably right.

I'd kill for file/directory-based routing in Node BE framework world. Been thinking of ripping the TS router route gen out and hacking it together with Fastify somehow...

Okay, I'll explain, I guess 🤷

Rockets are designed to minimize dry mass, are _just barely_ structurally sound when tanks are empty, and rely on pressure to maintain integrity. Think coke can but with relatively MUCH thinner walls. This kind of failure is likely SpaceX optimizing booster mass.

It's almost like grain silos aren't designed with the same constraints as rocket tanks 🙄

Ah grid, always seems like a good idea for layouts, and almost never is.

On the other hand, raw CSS has gotten a lot more powerful, so I get folks being excited about things like conditionals and container queues. If you're stuck having to write raw CSS, these things are very useful. You just... don't really need them when you style through JS components. 🤷

This is only "weird" in the same way that learning how something unfamiliar works is "weird". Promises are "weird". Prototypes are "weird".

I didn't know about this 😅 Also, apparently dvh is dynamic and can cause content to resize on scroll? But there's svh (smallest value) and lvh (largest value)? So many units...

You could implement access to ctx via .this, but IMO that's pretty limiting as far as composable functions go. Works better if you're into classes rather than functions, and most JS folk lean away from classes. 🤷

Speaking from React's POV, these aren't the same thing? It's not '.this'. Context in React is like a portal between parents and children, with no manual passing of ctx args around. In vanilla JS, you either have to manually pass a context arg, or rely on global scope, both of which have trade-offs.

I'm guessing he's asking for {}.keys(). length or similar. Other reply covered why chaining is risky.