That is why rewriting in another language is such a cheat. LLMs beat 10 years+ experts at the details of a single line of code (and I mean SYNTAX, not invariants), but suck at the design, at the level of functions, and higher up.
If you rewrite someone's stack ... you take out the design part of the work. No need to redesign. Obviously the high level decisions work. 99.5% work as well in python as they do in rust ...
Of course, this will never be the next big thing, and just doesn't help companies one iota. If you need a new thing, this will fuck up badly. Hell, even this translation will fuck up without a senior developer regularly telling the model: "WTF!!!!! Don't do that. Just don't". For a new product you need 100x that.
It has many nice applications, but those rewrites in general is something I don’t like.
1. Language semantics don’t translate, way people usually write python is not how you write rust.
2. There’s no such thing as line-for-line rewrite with llm, even if you’re really great at spec planning etc, if you don’t review each line, it’s going to be lazy.
3. Brings me to last point, it’s usually such a huge amount of code that llm “ports” and fact it is going to be lazy somewhere, means you get ticking bomb.
On the good side - abandoned software that needs to be migrated to compile on modern systems is for the most part solved and I love it.
Comments
With moves like this, I'm not so sure victory is assured... but yes. Pay to play.
I, like most, beat linting delay by running it in the background; asynchronous.
Having been negative, so far, I want to say something positive. I appreciate that LLMs weren't used for license washing in this case.
That is why rewriting in another language is such a cheat. LLMs beat 10 years+ experts at the details of a single line of code (and I mean SYNTAX, not invariants), but suck at the design, at the level of functions, and higher up.
If you rewrite someone's stack ... you take out the design part of the work. No need to redesign. Obviously the high level decisions work. 99.5% work as well in python as they do in rust ...
Of course, this will never be the next big thing, and just doesn't help companies one iota. If you need a new thing, this will fuck up badly. Hell, even this translation will fuck up without a senior developer regularly telling the model: "WTF!!!!! Don't do that. Just don't". For a new product you need 100x that.
Very good example. Translating the answers is not the same as having to think up the correct answers.
It has many nice applications, but those rewrites in general is something I don’t like.
1. Language semantics don’t translate, way people usually write python is not how you write rust.
2. There’s no such thing as line-for-line rewrite with llm, even if you’re really great at spec planning etc, if you don’t review each line, it’s going to be lazy.
3. Brings me to last point, it’s usually such a huge amount of code that llm “ports” and fact it is going to be lazy somewhere, means you get ticking bomb.
On the good side - abandoned software that needs to be migrated to compile on modern systems is for the most part solved and I love it.