|
|
|
|
|
by kitsunesoba
1588 days ago
|
|
There’s no guarantee that lightning will strike twice in this case. When Firefox overtook IE6, Microsoft had been colossally mismanaging IE for years, which meant that IE had become a rusted husk of what it was in its glory days. This made for incredibly strong incentive for web developers to support an alternative, because having to develop for an utterly broken browser for an indefinite period of time was intensely unappealing. On the end user side of the equation, Firefox’s incredible speed, UX improvements, and robust support for extensions did a lot to win people over. Fast forward to today. Google is infinitely more savvy with web developer relations than late-IE-era MS could’ve ever been — they keep devs “fed” well enough with a steady stream of new shiny features that it’s unlikely that they’d ever revolt. For users, the difference in speed and UX between Firefox is negligible or even works in Chrome’s favor (which is tilting further in Chrome’s direction with every site that’s developed and tested only against Chrome). Additionally, the barrier to entry for new web engines is so high now that anybody trying to build a browser that is to Chrome what Firefox was to IE is almost certainly doomed to fail unless backed by a company with deep pockets and no expectation of return on investment for many years. |
|
If Google is treating devs and users well, there is no reason to switch. It's when they falter on one, migrations can and will occur (given past history as experience).