3 ms·
As a bit of history, in case you're interested: Opera releases often used to be staggered, with Windows out first (since, as you say, they're the biggest), MacO
by SEMW 13y ago
As a bit of history, in case you're interested: Opera releases often used to be staggered, with Windows out first (since, as you say, they're the biggest), MacOS following, and Linux several weeks behind. Around Opera 10ish (I think, can't remember the exact one), they made a thing of changing that, promising that MacOS and Linux releases would from then on be simultaneous with Windows, as equal-first-class platforms. And with the switch to blink, they've quietly dropped that. Obviously I see the economic logic of releasing for the most popular platforms first, but that doesn't much blunt the emotional disappointment (from me and other Opera for Linux users) of seeing them drop their commitment.
(On a more practical note, for why I switched to FF - the latest Presto may not be much more than a year old, but you'd be surprised how fast the web changes when you're using an unmaintained rendering engine. New website functionality often doesn't work - html5 file uploading on most sites is broken, can't get the new google maps, g+ and fb are slow, etc. Web devs don't test on presto now that opera for windows/mac doesn't use it, and opera have stopped packaging website shims).
- gsnedders 13y ago10.50 was Windows-only too (the day after the brower ballot screen went live, 2 March 2010); Mac/Linux not catching up till 10.60 (1 July 2010). (Note also that there had been large delays in Presto reaching Desktop before — most notably with Opera 10 (2.2.115) and 10.10 (identical but with Unite enabled), Mobile shipped a beta of Mobile 10 with Presto 2.3.something before 10.10's release, and a second beta with 2.4.15 shortly after. Note from late 2.3 Presto releases, the final digit is the most significant one.)