manifesto

Part of AMP (1) is a web component library grounded in the extensible web manifesto (2). The plan was that the browser vendors give developers deeper access so that they could test new elements/standards through web components and polyfills. The AMP component library is one example of this, and stories are one of their forms. So basically if you use their tags to structure your content, it creates a ig/sc style Web Story. The structure that they have is (3): Story -> Pages -> Layers -> Elements Each page represents a tappable screen, Layers occupy the full screen, stack and have layout defaults like fill or lower-third and Elements can be regular html elements or other AMP components. I think that it's a neat way of organizing pages of information and made a clojure wrapper around it here: https://github.com/rainbow-bamboo/sargam 1. http

Agreed. And importantly, the fragmentation of the Javacript ecosystem is on purpose: https://github.com/extensibleweb/manifesto I think about the fragmentation that shows up in the form of multiple frameworks and patterns as a necessary part of that. It's not something that I want to fix. So to draw a line and say, "extending core Javascript features is fine, but compiling into Javascript isn't" -- I just don't get that. Typescript is a testing ground not just for typed programming in general, but also for features like decorators and meta-programming features. It's good to have a diversity in what people are building and using, that's how we get real world data on what works.

Nonetheless, its still mildly concerning that smaller players in the browser space are finding it difficult to keep pace with all the new APIs being introduced to the web these days. Even Microsoft sort of gave up and killed their browser engine in favor of a Chromium fork. It's a tricky situation with no obvious solutions. The Pale Moon dev's plea to slow down isn't going to work; devs want these new features and they're not going to stop using them just because a smaller browser developer with no significant market share can't keep up. There is, perhaps, the beginnings of a solution with the Extensible Web Manifesto[1], which aims to shift the focus of browsers from implementation of many high-level features to instead focus on smaller, simpler low-level features which high-level features can then be built on top of. (Though ironically