3 ms·

I disagree entirely, and I can convince you I'm right with one sentence: More lines of JS/TS are written by AI than lines of Rust are written at all. We don't h

by 827a 1y ago

I disagree entirely, and I can convince you I'm right with one sentence: More lines of JS/TS are written by AI than lines of Rust are written at all. We don't have the data to assert this as true, but I think the vast majority of people would agree with that statement. This statement being true disproves the statement "the industry has been making huge efforts to push errors from runtime, to compile time." The industry is not a monolith. Different actors have different, individualized goals.

pas 1y ago
it's absolutely not a problem that people are writing more JS/TS than Rust. if that Rust is for decades and the JS/TS gets thrown out in 1 year. there's a lot of shitty C being written still around the world yet the Rust that goes into the kernel has real value long term. there's an adoption cycle. Rust is probably already well over the hype peak, and now it's slowly climbing upward to its "plateau of productivity". (and I would argue that yes there are pretty good things happening nowadays in the industry. for many domains efficient and safe libraries, frameworks, and platforms are getting to be the norm. for example see how Blender became a success story. how deterministic testing is getting adopted for distributed databases.)
raincole 1y ago
And I have a very hard time understanding why AI is "pushing the errors to the right". > Compiler -> code review -> tests -> runtime checks -> 'caught' in prod With AI we still compile the code. We still do code review. We still run tests (before code review, obviously; don't know why it's listed like this). We still do QA at runtime. I feel like anti-AI people are those one who actually treat AI as magic, not the AI users. AI doesn't magically prevent you from doing the things that helped you in pre-AI era.
- Balinares 1y ago
  No, but if a shop added overnight 5 fledgling juniors for each current employee on the project, not only would the delivery not be sped up on account of Brooks's law, but the stack would soon tank under the weight of its own issues. So outside of such situations as hilarious consultancy disasters, no one did that. Now with AI they do.

by 827a 1y ago

pas 1y ago

it's absolutely not a problem that people are writing more JS/TS than Rust. if that Rust is for decades and the JS/TS gets thrown out in 1 year. there's a lot of shitty C being written still around the world yet the Rust that goes into the kernel has real value long term. there's an adoption cycle. Rust is probably already well over the hype peak, and now it's slowly climbing upward to its "plateau of productivity". (and I would argue that yes there are pretty good things happening nowadays in the industry. for many domains efficient and safe libraries, frameworks, and platforms are getting to be the norm. for example see how Blender became a success story. how deterministic testing is getting adopted for distributed databases.)

raincole 1y ago

And I have a very hard time understanding why AI is "pushing the errors to the right". > Compiler -> code review -> tests -> runtime checks -> 'caught' in prod With AI we still compile the code. We still do code review. We still run tests (before code review, obviously; don't know why it's listed like this). We still do QA at runtime. I feel like anti-AI people are those one who actually treat AI as magic, not the AI users. AI doesn't magically prevent you from doing the things that helped you in pre-AI era.

Balinares 1y ago
No, but if a shop added overnight 5 fledgling juniors for each current employee on the project, not only would the delivery not be sped up on account of Brooks's law, but the stack would soon tank under the weight of its own issues. So outside of such situations as hilarious consultancy disasters, no one did that. Now with AI they do.