Profile picture
Justin Schuh 🗑 @justinschuh
, 8 tweets, 2 min read Read on Twitter
The whole "Chrome is the new IE6" argument is objectively wrong, and really the worst kind of FUD. So, I'm going to try to put it to rest by providing some relevant history, and calling out just how much Chrome differs from IE6. [1/8]
By the turn of the century IE had captured the Web ecosystem. And with IE6 Microsoft stopped development—stalling the Web. Meanwhile, potential competitors faced the prohibitive technical barrier of building a compliant implementation of a massive, closed source product. [2/8]
In the end it took 5+ years of Microsoft standing still and ignoring the Web (with IE in maintenance mode) before Mozilla's Firefox and later Apple's Safari were able to offer credible alternatives to IE's dominance. (Don't @ me Opera users.) [3/8]
Contrast that history with Chrome today. Chromium (Chrome's codebase) is community developed open source software. You can debate governance and direction, but we participate in standards bodies and the code is open for anyone to contribute to or—in the extreme case—fork. [4/8]
You have countless competing browsers built on top of the Chromium codebase—not to mention embedders and entirely new platforms like Electron and Node. None of these things would have been possible with IE6, because no one outside Microsoft had access to the code. [5/8]
Also contrary to IE6, Chrome is far from stagnant as a product. In fact Chromium is so actively developed that other browser makers have clearly found it easier to jump on board and pool resources rather than continue building their own engines. [6/8]
That's why the Chromium developer community includes such a diverse mix of contributors—ranging from competing tech behemoths to individual OSS developers scratching an itch. No community is perfect, but you certainly can't argue that it is closed. [7/8]
So, the tl;dr: IE6 was bad because it stagnated the Web after locking the ecosystem into its closed source runtime. Chrome isn't doing that—and given Chromium's open source development model it's hard to fathom how something similar could happen. [8/8]
Missing some Tweet in this thread?
You can try to force a refresh.

Like this thread? Get email updates or save it to PDF!

Subscribe to Justin Schuh 🗑
Profile picture

Get real-time email alerts when new unrolls are available from this author!

This content may be removed anytime!

Twitter may remove this content at anytime, convert it as a PDF, save and print for later use!

Try unrolling a thread yourself!

how to unroll video

1) Follow Thread Reader App on Twitter so you can easily mention us!

2) Go to a Twitter thread (series of Tweets by the same owner) and mention us with a keyword "unroll" @threadreaderapp unroll

You can practice here first or read more on our help page!

Did Thread Reader help you today?

Support us! We are indie developers!


This site is made by just three indie developers on a laptop doing marketing, support and development! Read more about the story.

Become a Premium Member and get exclusive features!

Premium member ($30.00/year)

Too expensive? Make a small donation by buying us coffee ($5) or help with server cost ($10)

Donate via Paypal Become our Patreon

Thank you for your support!