That is exactly my thinking. This model goes contrary to the needs of propriety software, to lock you into a whole system you can charge for. (And FWIW, I don'

That is exactly my thinking. This model goes contrary to the needs of propriety software, to lock you into a whole system you can charge for. (And FWIW, I don't have the vendetta against proprietary software like a lot of HN seems to, so I'm sympathetic here about breaking the incentives for production of software that legitimately needs paid devs and can't get enough via donations. But if Open Source teams can make it work, I'm all for that!) OTOH, as a general model ... I can see why it has failed to pick up, at least with typical devs and prevailing software practices. It requires a level of care about interfaces and interoperability that is not very common. More often, you see APIs broken willy-nilly with no functional need to. Stable standards for exchange of data require a lot of work and are the exception -- even when you have them, there will be the warts that reveal abstraction leakage. (Another comment mentions how HTML was quickly broken.[0]) The no-app approach with basically be that fight, but for every external touch point, of every module. I do hope the dev world can make that work ... but also: understand what you're fighting against. [0] https://news.ycombinator.com/item?id=25021180 https://news.ycombinator.com/item?id=25021180