What to Know About JavaScript in 2026
eustoria
22 points
6 comments
September 23, 2026
Related Discussions
Found 5 related stories in 81.2ms across 7,510 title embeddings via pgvector HNSW
- Why Write Code in 2026 zdw · 20 pts · July 12, 2026 · 56% similar
- The JavaScript Midlife Crisis maroun-baydoun · 50 pts · September 22, 2026 · 53% similar
- Why Vanilla JavaScript guseyn · 118 pts · July 12, 2026 · 53% similar
- What I believe about the future of software development misternugget · 11 pts · September 21, 2026 · 49% similar
- Twenty Years of jQuery: How a Little Library Rewired Web Development theanonymousone · 27 pts · September 05, 2026 · 49% similar
Discussion Highlights (4 comments)
davidee
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.
gavinray
> "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.
_ink_
So is Angular dead? Or why doesn't it deserve any mention?
giancarlostoro
> 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.