> I'd say it starts with dialing back the "new feature/change fetish" that a lot of web developers have I wonder whether this phenomenon is driven by HTML, CSS

> I'd say it starts with dialing back the "new feature/change fetish" that a lot of web developers have I wonder whether this phenomenon is driven by HTML, CSS, and JavaScript being such lacklustre tools for building applications? Many things that are completely reasonable to deal with in any “native” stack (animations, local storage, offline access, hardware access, accessibility just to name a few), while usually possible with a web stack, are often unnecessarily difficult or awkward. Things are improving fairly rapidly because of the insistence that everything should be web based these days, and I could totally see that driving people to the bleeding edge. I mean hell, I do it myself. I’m a web developer, and when reading about shiny new features I’m often eager to start using them ASAP — especially when it would replace a bunch of kludgy JavaScript I’d been relying on previously.