and this was something everyone was parroting years ago, then we moved forward with docker saying it is capable of isolating deps without the overhead of a VM so why are we moving backwards now?
This goes back to how we define "novel problems." Is a dev building a typical CRUD webapp for some bespoke business purpose a "novel problem" or not? Reimplementing a well-known standard in a different language and infrastructure environment (e.g. https://github.com/cloudflare/workers-oauth-provider/)?
I'm probably just rephrasing what you mean, but LLMs are very good at applying standard techniques ("common solutions"?) to new use-cases. My take is, in many cases, these new use-cases are unique enough to be a "novel problem."
Otherwise, this pushes the definition of "novel problems" to something requiring entirely new techniques altogether. If so, I doubt if LLMs can solve these, but I am also pretty sure that 99.99999% of engineers cannot either.
I don't think the problem is the money. Neither of them provides a long term stable API, let alone ABI. So progress gets reset on a regular base.
Gnome is further hampered by no respect for user choice. They provide an appleish UI, with an Enterprise, one size fits all experience.
KDE is better, but they are not the official GNU/Red Hat choice. They will choose practical above esthetica.
A big part of the Linux success is POSIX, a standard to provide direction. The UI world never had anything line it, so it is very fragmented. A real solution could be a complete enough UI standard, used by OSX, Windows, Gnome and KDE.
reply