VoidWarranty

A compiler is more efficient than an 8 layer llm lasagna stack of tools. Likewise, to stay on topic: a strictly typed language is better than running five python type checkers if you really want type checking.

Its more efficient to have a llm write in a strictly typed language than to duct tape guardrails(either tools or more llm work) after the fact. Depends on what you're building of course. I speak from an industry that ships large executables. (games)

If I had said c++ would that have triggered you less?

Its about limiting surface area.

The gymnastics people are putting their ops teams through in order to validate oceans of generated slop is insane. Just use Rust and half of that work goes away.

Oops thank you, I did mean static. I should know better as I am a cpp fan. Updated.

Dynamically typed languages are going to decline with the rise of AI coding.

Statically typed languages provide the determinism necessary to efficiently anchor probabalistic coding agents.

You can throw as much type checking at dynamic languages after the fact, but youre just going to burn energy (and tokens) doing what another language gets 'for free'.

This reads to me like someone's mania project. I wish OP the best and hope they can get some rest.

When it completed a task from the same amount of guidance and specifications that I would have spent on a Jr engineer. It did it faster and better.

I always wondered how they messed portal up. It seemed so natural of a piece of hardware to fit into everything else they do. Tying it to horizon says all I need to know.

We're talking about different things.

Im talking about your own personal coding. You dont have to use the new things. You dont have to know them to decide to discard them. In fact, the criteria to discard something is to not know it. You generally shouldn't be using things you dont know anyway.

The fact that other people use things you do not know is not a reason to stress out about the dumb pace and direction c++ is moving in. It is possible to enjoy a life free from fomo about the c++ standards goalposts.

You don't have to use them. There's a handful of nice to haves in modern releases but its totally fine and sane to just ignore whatever the committee is distracted by at the moment.

Hell, if you wait long enough, they'll just deprecate it before you can care to bother.

Which is worse? std's mess or one you control? I'd take any random game engine's STL over std any day.

The reqs are likely a side effect of how the application is built and the fact that its made by a solo dev.

I find it more pleasant to do UI within the context of a video game renderer than to bother with ui libraries and native hooks.

You only have to deal with windows enough to get you a rendering context: then you can do everything in your walled garden.

Term limits.

Let's not be pedantic. Its quite obvious to anyone not living under a rock what "anti-vaccine" means.