>
Google routinely floats out APIs, services, and platforms and encourages their use despite fatal flaws that mean they are doomed from day one.For most use cases, there are better options now than Chrome apps. ServiceWorkers didn't exist when Chrome apps were introduced. Neither did wasm, and its precursors NaCl and PNaCl were scoped to just Chrome apps, not to the public web.
Chrome did a very good job at a) building a platform that developers could use right then and b) working with other browsers and standards committees to get enough features implemented to replace what they built. They said, no, we shouldn't have a proprietary thing called "Chrome apps," we should just build it into the web platform so that people who don't use Chrome can use them too.
And they set a very long (many years) timeframe for shutting down their initial version of the thing.
This is exactly what I want a platform provider to do. I don't want "Chrome apps" any more than I want Flash or ActiveX or "Best viewed in Internet Explorer." But also, I do want platform providers to build platforms - I don't want them to refuse to build platforms on the grounds that they don't know the right answer yet and they can't immediately standardize something right now. I'm glad Flash and ActiveX are dead, but I'm glad they existed because they proved that the platform is valuable, if only you could implement it in a reasonable way. I'm glad ActiveX's original version of XMLHttpRequest existed because it proved that there was demand to standardize the version we now have.