Yesterday, it was made official that our group, by the intermediate of its founders, co-signed a manifesto for a more extensible web.
You may ask yourself what it actually means, and why this is important. Allow us to explain.
An extensible web is a web where developers are totally incorporated in the innovation scheme of the web platform, and can actually build new features instead of just relying on the ones browser vendors could agree on.
The second reason why an extensible web is more beautiful is that, even though APIs are crafted by smart people in standards committees, mistakes can be made from time to time. Don’t get me wrong, mistakes are normal: no process can be free of mistakes. However, the problem with the current standards process is that mistakes are generally irreversible; it’s difficult to make experiments with a broad audience.
Once something shipped in a browser, removing it is painful (at least) and often impossible. This is why this process is taking so much time: we have to be sure we’re doing the right thing. But, sometimes, web developers can’t wait. By shipping a very minimal set of features that allow web developers to build libraries around low-level features, we can see what works and what doesn’t work and take that in consideration when designing the final version of the API. This helps creating better in-browser features, and it also helps shipping early implementations faster. This approach is called prollyfilling.
In short, an extensible web leaves more room for short-term innovation and experiments, without compromising a stable and harmonious future.
In case you didn’t already, I invite you to read (and sign) the manifesto, and look at some of the links provided from there.
In the name of this community group,