drawfloat

Node dependencies are fine, add an npmrc file to have it default to exact versioning and you solve 90% of common day to day problems. It's not ideal, but nor is cargo's mystery meat approach to importing optional features from packages.

5 or so years ago, Next was a pretty solid option to quickly build up a non SPA, when combined with the static export function. It wasn't ideal, but it worked and came batteries included. Over time it's become more bloated, more complicated, and focused on features that benefit from Vercel's hosting – and static builds can't take advantage of them.

These newer features seem of limited benefit, to me, for even SPAs. Why is there still not a first class way of referencing API routes in the client code that provides typing? Once you reach even medium scale, it becomes a mess of inteprolated string paths and manually added shared response types.

Patently false, a slim minority in all countries is more optimistic than they are sceptical.

It’s ludicrous to pretend important ideas only come from the US and China.

Banning third party AI assistants but maintaining access to your own on one of the biggest messaging platforms in Europe will indeed get this kind of response, not really a surprise.

Doubt the result will be “using WhatsApp without a pointless ai assistant crammed in” though sadly

Whatever is going on there, I would not categorise a company backing that as morally “good”

As wireless charging never quite reached the level hoped – see AirPower – and Google/Apple seemingly bought and never did anything with a bunch of haptic audio startups, I figure that idea died....but they never cared enough to make sure the USB port remained top end.

The difference there is it became hated after it was established and financially successful. If you need to turn free visitors in to paying customers, that general mood of “AI is bad and going to make me lose my job/fuck up society” is yet another hurdle OpenAI will have to overcome.

They even say it in this blog:

"Our mission to design a web framework specifically for building websites — what we call content-driven websites, to better distinguish from data-driven, stateful web applications — resonated"

Would you rather there were no age checks?