I think this + node:test makes Node.js a pretty compelling sensible default for most things now. Running things with `tsx` was such a QoL improvement when it happened, but it didn't solve everything.

Runtime type assertion at the edges is mostly solved through `zod` and tools like `ts-rest` and `trpc` makes it so much easier to do full-stack Typescript these days.

We're fast approaching the point where vibeX is becoming derogatory.

I've had a notion that LLMs can read Typescript types much better, than JSON schema types.

So, I've been tinkering around with a library that can generate schemas for structured JSON outputs, according to a Typescript-like custom schema definition: https://github.com/nadeesha/structlm

So far, I've been seeing promising results with accuracy on-par or better, but using 20-40% less tokens than JSON schemas.

I don't know how I feel about this one, honestly.

> Build a site like a site. Use HTML. Use navigation. Use the platform.

Sure, but what about all the other problems that aren't solved by View Transitions? There's some truth to the fact that frameworks like Next.js has jumped the shark. But they're not solving the problems of _just_ the SPA.

> Despite the large interest in agents that can code alone, right now you can maximize your impact as a software developer by using LLMs in an explicit way, staying in the loop.

I think this is key here. Whoever has the best UX for this (right now, it's Cursor IMO) will get the bulk of the market share. But the switching costs are so low for this set of tooling that we'll see a rapid improvement in the products available, and possibly some new entrants.

> including physical activity, smoking, alcohol, diet, sleep duration, socioeconomic status, and polygenic risk

Wondering how much of this is due to geography and air quality. City centers have relatively bad air quality and a high amount of ambient lighting at night, compared to non urbanized areas.

The cardiovascular effects of poor air quality is arguably well understood.