[ecjhdnc2025]

I remember someone trying to recruit me for a London-based startup whose developers were obsessed with async and Meteor. They struggled to ship (it was a silly idea anyway) and I don't think they survived their pivot. But the tools choice was a good part of the problem: it wasn't ready and they were imagining it had harnessable pixie dust.

I can see applications for async work within the wider backend all over the place.

But the objective justification for the async stuff being involved in the rendering of page content is thin.

And since the other applications are for sort of "high level systems" programming -- that boundary between the app and the OS -- I personally prefer Go for all of that.

Node is a significant devOps/package management pain that belongs in as few places as possible.