Jsonnet is pretty nice but the library support isn't quite as good. There are some nice libraries for yaml that do round trip processing for example so you can modify a yaml programmatically and keep comments. Yaml certainly has some warts (and a few things that are just frankly moronic) but it deserves some credit for hitting the sweet spot in a bunch of ways.

I wonder if it will ever be practical or economical to have humans and machines driving together on the roads we have now though. Maybe we'll skip that step and go to robot-only roads with more stuff built into the actual roads.

On Musk, he doesn't need PR so much as to keep his mouth shut for a while and try and deliver on some of his BS instead of spouting more.

It's very effective. Both times I've wanted to give them my money. But mac only, geeze

In the same boat myself... would be nice if they'd develop a more portable version... that said, could probably make an extension for VS Code or Zed to do similar.

They just haven't done the "now monitise it" step in the vibe-coding journey.

with all respect to the man himself, not sure tom blomfield needs to think about that part..

It’s ok! He’ll just ask the AI! It’ll solve it for us!

Blue windscreen of death you say

Glad to see diamond inheritance being a problem in other fields

It's not a problem, it's a feature.

Or rather, it's only a problem when you insist on rigid perspective that makes it a problem.

(The real problem is that so many people insist on viewing things as trees, when their natural shape is directed graph.)

They should rewrite biology in Rust.

Just to stay on topic, Rust Language was named after fungus. “over-engineered for survival”

The goal isn't to use AI, though, it's to be productive. Maybe for you AI + writing support tools to improve your workflow makes you more productive and that's great! For me, for the kind of work I'm currently doing, I'm more productive in other ways.

Why dumb down your work worse because the machine can't understand it?

Seems like the code is designed poorly if it can't be worked on in small chunks

Seems like you're dismissing the cost of artificially splitting what should be a monolith.

It outweighs the supposed productivity boost of LLMs by at least one order of magnitude if not more.

Most people have a smaller context window than LLMs.

> From the perspective of the traditional server business, such a developer is unfortunately often seen as rather helpless—someone who needs assistance with everything, can’t run their own database, and has no idea what a nameserver is.

Developers who have no idea about how things work (like nameservers and databases) are pretty helpless generally, regardless of whether they call themselves cloud-native developers or not.

That isn't always true, there's plenty of times where companies push features that users don't want. No Chrome users have been clamouring for more ads and more invasive tracking, for example.