|
|
|
|
|
by bravetraveler
4 hours ago
|
|
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. |
|
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.