I don't understand what is supposed to come next. So its not Ruby on Rails anymore. What is it? Are agents going to magically convert all the RoR ecosystem to Rust or Whatever?
But yes, I think RoR's selling feature was developer ergonomics, which suddenly seems less of a benefit if developers aren't the ones writing the code. Readability and conciseness still has benefit, but the trade-off of worse performance (and less static checking) is suddenly more questionable.
Have a look at fly.io facing similar issues, another platform whose value prop was dev ergonomics: <a href="https://fly.io/blog/kurt-scott-money-sprites/" rel="nofollow">https://fly.io/blog/kurt-scott-money-sprites/
> Readability and conciseness still has benefit, but the trade-off of worse performance (and less static checking) is suddenly more questionable.
There is an issue with this idea - we write software, we read it, we make sure it does what it should do, that it’s implement in a sensible and efficient way, and, most importantly, we make sure the tests do what they should do.
If you no longer write the code, it’s harder to understand it. If you don’t write the tests, you need to trust the LLM did both jobs correctly (multiple adversarial LLMs can help), but, ultimately, it’s code you can no longer claim you understand. And you can’t really be sure it does what you want until you understand it.
Microsoft has a huge market share, and immense testing and QA resources, and it’s reasonable to assume this has driven down the number of unknown issues a lot.
That said, why do we think compilers produce correct code?
lbrito · · focus · HN ↗
usef- · · focus · HN ↗
But yes, I think RoR's selling feature was developer ergonomics, which suddenly seems less of a benefit if developers aren't the ones writing the code. Readability and conciseness still has benefit, but the trade-off of worse performance (and less static checking) is suddenly more questionable.
Have a look at fly.io facing similar issues, another platform whose value prop was dev ergonomics: <a href="https://fly.io/blog/kurt-scott-money-sprites/" rel="nofollow">https://fly.io/blog/kurt-scott-money-sprites/
rbanffy · · focus · HN ↗
There is an issue with this idea - we write software, we read it, we make sure it does what it should do, that it’s implement in a sensible and efficient way, and, most importantly, we make sure the tests do what they should do.
If you no longer write the code, it’s harder to understand it. If you don’t write the tests, you need to trust the LLM did both jobs correctly (multiple adversarial LLMs can help), but, ultimately, it’s code you can no longer claim you understand. And you can’t really be sure it does what you want until you understand it.
NetMageSCW · · focus · HN ↗
rbanffy · · focus · HN ↗
That said, why do we think compilers produce correct code?