A system’s purpose is what it does.
If a standard is so complex and intertwined that only 2-3 mega corps can implement it … then that is not an accident, it is the point.
I’m not sure what new thing will be born after the Web has fully become Google-tech, but considering that Mozilla is killing vertical tabs this year, I can’t wait for it to happen rather sooner than later.
I’m not sure that was intentional with SVG. It pre-dates the HTML5 Google-driven push to roll back the separation of content and presentation and make it impossible to remove ads. SVG came to live at the same time as the XHTML push started to gain momentum. At the time, W3C was pushing to make everything XML with graceful fallback. If everything is XML, then you can embed everything in everything else. You Atom feed can contain XHTML, which can contain SVG. Because everything is XML and properly namespaced, if your feed reader doesn’t know about SVG and only understands a subset of HTML, it can render the text and the markup that it wants to and ignore everything else trivially.
My biggest problem with SVG is that it only half jumped on the XML band wagon. A lot of SVG is just PostScript in XML attributes. You can’t manipulate those structures uniformly (which is the main selling point of XML) but if they’d made each of the PostScript commands a separate XML node then they’d have easily doubled and probably quadrupled the file size. It was really an indication that XML needed a denser serialisation but none of the binary XML standards ever took off so SVG was forced to pay for the disadvantages of XML without being able to benefit from the advantages.
Killing vertical tabs? As in the tab tree extension? Can you link something about that please?
Some hints at userChrome.css going away.
I’m fighting tooth and nail against Google taking over the Internet. Hopefully I can get sizable enough to chip away at their monopoly.