

While true, the issue is that Debian release cadence is such that they will always be “behind” kernel and wine wise.
Also they are more purist and less likely to facilitate proprietary bits. Last time I tried wine a lot of apps didn’t work because they had no work to enable non-free fints So they may have the same general packaging strategy, but the vintage of content and scope are distinctly different from more aggressive distributions.



It’s pretty much a vibe coding issue. What you describe I can recall being advocated forevet, the project manager’s dtram that you model and spec things out enough and perfectly model the world in your test cases, then you are golden. Except the world has never been so convenient and you bank on the programming being reasonably workable by people to compensate.
Problem is people who think they can replace understanding with vibe coding. If you can only vibe code, you will end up with problems you cannot fix and the LLM can’t either. If you can fix the problems, then you are not inclined to toss overly long chunks of LLM stuff because they generate ugly hard to maintain code that tends to violate all sorts of best practices for programming.