Have you seen anyone claiming that this brand-new vibe-coded thing has better compatibility (and/or feature parity) with the proprietary applications it claims to replace than the mature free software solutions currently do?
Given that people are literally just reverse engineering these applications by having the LLM decompile it and observe what it does in memory, yeah I expect these will be compatible much faster than manual efforts. I did something similar recently where I had an LLM figure out the proprietary format for the way my Nikon camera stores RAW files. There's currently no open source implementation for it, and now I can read them using my own library. So, something that used to be a herculean effort before, is something you can now do in a few days using an LLM.
I haven't played with the Office stuff, but I am using his PhotoCraft and LightCraft, and they work fine for what I need. I can process my photos using completely open source tools now that have a UX I'm used to. Yet, I'm aware that LightTable exists, and I've tried using it, and it was not a great experience. Given how fresh these projects are, it's absolutely incredible to me. And with LLMs it's possible for me to fix whatever issues I have with the app myself. The reality is that most people don't really need to do anything incredibly complex with these tools. So, if they do what you need you have an app you can keep using indefinitely. The hard part has always been to build out the initial features and the UX which was just too hard to do by hand.
It’s made it so easy that there is currently a deluge new projects which often seem plausible at first but mostly turn out to actually be garbage upon closer inspection.
You're saying this as if NPM ecosystem didn't exist before LLMs. The reality is that there has always been a ton of garbage projects. Over time people gravitate towards projects that actually work and are useful to them. And this isn't hard problem people keep making it out to be. You look at the number of stars a project has, how long it's been developed, how many users it has, and so on. This gives you an idea of whether it has legs or not. I'll certainly trade having to rely on proprietary software for the problem of having too many open source options.
It’s irrational not to be skeptical of a two-week-old project claiming to be ready (or “almost” ready, lmao) to replace multiple 30-year-old suites of software.
Seems to me that the rational thing is to try the project, see if it does what you need and decide based on that. But that's just me.