I welcome your attitude, bring it on and I'll be more than supportive of it. But still, I'm maintaining that you can't work against the likes of WHATWG and W3C churning out specs, when they are subverted and financially dependent on Google.
In other words, we're toast ;( But hey, that might be exactly the kind of situation that motivates developers after all.
With my project [1], I'm attempting something less ambitious: I'm trying to re-establish SGML as an authoring format (HTML is based on SGML, and SGML is the only standard that can tackle HTML), to at least bring back a rational authoring and long-term storage format for content that matters and that you'd like to be able to read in a couple of decades still without an ad company or even a failed, over-complicated all-in-one document and app format of the 2010's getting in your way.
In other words, we're toast ;( But hey, that might be exactly the kind of situation that motivates developers after all.
With my project [1], I'm attempting something less ambitious: I'm trying to re-establish SGML as an authoring format (HTML is based on SGML, and SGML is the only standard that can tackle HTML), to at least bring back a rational authoring and long-term storage format for content that matters and that you'd like to be able to read in a couple of decades still without an ad company or even a failed, over-complicated all-in-one document and app format of the 2010's getting in your way.
[1]: http://sgmljs.net/blog/blog1701.html