‹ BackHN Continuity

Thread

What to Know About JavaScript in 2026

21 points · 5 comments · eustoria

Loading the complete thread in the background. This saved snapshot is available now. Refresh

  1. davidee · · focus · HN ↗
    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.

  2. gavinray · · focus · HN ↗

      > "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.
  3. _ink_ · · focus · HN ↗
    So is Angular dead? Or why doesn't it deserve any mention?
    1. whythismatters · · focus · HN ↗
      The author mentions Angular in the comments as a personal blind spot
  4. giancarlostoro · · focus · HN ↗
    > 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.

    1. prinny_ · · focus · HN ↗
      > Why should I go through so many layers to get my CSS

      You underestimate the passion with which the average front end developer hates CSS.

  5. bra31k · · focus · HN ↗

    [dead]

Open on Hacker News to reply ↗

Unofficial Hacker News client; not affiliated with Y Combinator.