> "I think people generally choose Deno because of the stability and security-first architecture."
The appeal of Deno to me was always it's Go-like `std` library, so that building basic apps didn't result in a spaghetti web of dependencies like in Node.
> I get into this in A Nice Vanilla App Architecture Using Web Components and CSS Module Scripts. I just really like how we can keep CSS to CSS files which could live in a folder right next to a JavaScript component.
I forget when in the mid to late 2010s I started seeing CSS inside JS code for SPA frameworks, but I absolutely hated it, it felt so wrong. Why should I go through so many layers to get my CSS When the browser is efficient about loading CSS as-is. I'm okay with it being "aside" a component on the other hand.
> I get into this in A Nice Vanilla App Architecture Using Web Components and CSS Module Scripts. I just really like how we can keep CSS to CSS files which could live in a folder right next to a JavaScript component.
I forget when in the mid to late 2010s I started seeing CSS inside JS code for SPA frameworks, but I absolutely hated it, it felt so wrong. Why should I go through so many layers to get my CSS When the browser is efficient about loading CSS as-is. I'm okay with it being "aside" a component on the other hand.
So is Angular dead? Or why doesn't it deserve any mention?
The author mentions Angular in the comments as a personal blind spot
Alt text: Buzz Lighter sees functional programming paradigms everywhere.
PS - I don't follow JavaScript or use it much, but these are nice tools to have in any language.