While Bun proved at-scale rewrite, these are proving huge at-scale re-dos of the entire software ecosystem.
I suspect 24 months from now the landscape of daily software is going to be vastly changed.
I'm curious about this part. As a user you're finding them extremely buggy - what kind of bugs are you seeing?
It sounds like you're expecting the bugs to be ironed out in six months. I guess I'm wondering if the same process that led to buggy software in the first place can actually be used to get rid of the bugs without creating more.
With a human in the loop, iterating on bugfixes can work. It’s just more human-labor-intensive than an initial implementation.
I suppose you could invite users to submit bug reports, give them some guidelines on how to write them, and then have an LLM monitor the bug reports and fix them. But then I think you’d be more likely to see the creation of more bugs, as you say.
Like so many open source GUI projects, it's clear they have solid technical developers who are building good underlying tech, but they have no one on the project doing any kind of user research or spending time thinking about what good UI/UX looks like.
Is there any evidence that LLM development practices result in code that is more reliable or easier to maintain?
And is software truly open source if the preferred way to maintain it is via proprietary commercial services whose behavior is subject to frequent change without notice?
Is this true for large & mega corps as well with deep enterprise integration? Thats where the money is for most of them.
Not so sure about that one
This is software's radiology moment.