Unironically, with LLMs, everyone should be looking to cut their system resource consumption (memory, disk, network, GPU, I/O traffic in general) and rewrite everything natively. It's not even that hard, and has been done several times over. Have a platform-independent business logic layer, and a platform-dependent UI/UX layer. Done.

> Unironically, with LLMs, everyone should be looking to cut their system resource consumption (memory, disk, network, GPU, I/O traffic in general) and rewrite everything natively.

Depends.

There is a lot of value in man-made software where the man knows exactly what happened where when why.

If you just revibe in rust, you get something that works at this point in time, but this deep architectural knowledge is completely lost and you're at the mercy of Dario not locking down your account for wrongthink.

That can still be fine for smaller tools where the cost of recreating them from scratch is alright, but revibing your core business thingy is likely a horrible idea, which I encourage people to do, as I'd love to have the business opportunity to take over their frustrated customerbase ca 5 years from now.

[delayed]

>and you're at the mercy of Dario not locking down your account for wrongthink.

Inference cannot be controlled. The models are already out there. It's too late.

Good luck doing the full-hands-off one-shot revibe stuff this all is referring to with GLM-5.3.

That needs claude-like capabilities.

It also should not be done at all. But that approach needs it.

Using open weights models like GLM-5.3 can also speed up rewriting, but then you're rewriting and not revibing, which is a lot slower.

Yeah I have to agree here - the days of being scared of complete rewrites are pretty much over.