In our world I'm not sure whether a human even read the entire thing before publishing it. There's absolutely nothing of substance in here.

The traffic is about 100x more expensive on "the cloud" and it killed all the ideas I had for cloud usage. Clouds are not worth it, even for scaling you can always rent more VPSes (or dedicated servers for heavy projects).

I'm not going to give you a lecture. Here are the concrete numbers: RAM — the real deal

Node.js, on my latest version, was using 1.4 GB of RAM just to boot the app on one instance.

Go?

48 MB.

I'm not kidding. On the first test I ran, I launched a 15 MB Go binary on a t3.micro. The API responded in 20ms. I thought I'd measured wrong. I checked three times. It wasn't a mistake."

There is definitely something to be said for a self-contained high-performance server in 48 MB...

Apparently Tiger Beetle also started in node, before the founder reached out for Zig.

Meanwhile all JavaScript tooling is being rewritten in Go and Rust.

Maybe it is time to finally grasp it should be left to the browser?

If it indeed took this little time, I strongly suspect the backend wasn't doing too much in the first place. Usually you can rewrite those quickly and demonstrate speedups. Some real big software that had a misfortune to have been written in something interpreted and inferior, might be more problematic, especially if you can't afford downtime or are unsure about all important corner cases, and when the program itself is your only documentation.

Another thing that was very jarring was that the article as a whole sounded very LLMese. Or PowerPointy? Take your pick. This little example screams that an LLM might likely have writen it:

    > I'm not going to give you a lecture. Here are the concrete numbers:
    > RAM — the real deal
    > 
    > Node.js, on my latest version, was using 1.4 GB of RAM just to boot the app on one instance.
    > 
    > Go? 48 MB. I'm not kidding.

it used to be a gigantic endeavor. now a few days work.