‹ BackHN Continuity

Thread

The JavaScript Midlife Crisis

56 points · 75 comments · maroun-baydoun

  1. hn_submit · · focus · HN ↗
    JavaScript is an abomination that never should've been left alive.

    And yes, I ask myself the question: "Who in his right mind would run JavaScript on the server and even write business logic in it?" Lots of idiots in this world it seems. JavaScript is the reason our text editors need 16GB of RAM to run these days and a simple weather app 1GB.

    In the ol' days assembly programmers probably could've written the weather app in a couple of KB (that's a MILLION times less memory people).

    1. MiroslavPokorny · · focus · HN ↗
      Exactly!

      In todays of multi processors, its seems completely backward to adopt a runtime that is limited to a single thread.

      1. suplexer · · focus · HN ↗
        JS has Web Workers in the browser and Worker Threads module in nodejs for parallelism. Most apps don't need to them to be fast, but many slow apps would be less slow if Workers were used more often.
        1. MiroslavPokorny · · focus · HN ↗
          Node is a single thread per process.

          While other languages leverage sharing memory amongst multiple cpus, node requires a process per CPU.

Open on Hacker News to reply ↗

Unofficial Hacker News client; not affiliated with Y Combinator.