I prefer the Android ROMs without GPL violations.

Essentially, all jQuery has done is drop support for Internet Explorer on Windows XP and Vista. Fully updated, XP runs IE8 and Vista runs IE9. Google Chrome did the same thing 2 months ago when it started requiring Windows 7 and up. Windows XP support was dropped a long time ago. Vista is still supported, but only used by a small chunk of users worldwide (about 1.4%). While XP still has a larger worldwide userbase (around 10%), most companies and individuals don't consider them worth supporting or advertising/marketing/selling to.

jQuery does still support both IE10 and IE11, so it's not like they're dropping all IE workarounds as stated in the title.

I know. It's been in OO since before LO existed. Just wasn't sure if the poster was aware of it.

Grab LibreOffice and check it out. If startup time is a key point for you, install and enable the QuickStart feature. It'll pre-load part of LibreOffice as Windows starts up and then let it sit idle in the background, just like Microsoft Office does to improve startup time.

You've got it the wrong way around license-wise. LibreOffice can pull anything they'd like from OpenOffice, but OpenOffice won't because they don't want LGPL/GPL code polluting their code-tree. OpenOffice spent a long time rewriting GPL/LGPL code to ensure they could keep their license pure which is one of the reasons they're so much further behind LibreOffice.

Safari works the same way. That's why folks with older Mac hardware who aren't running the latest OS can't run the latest Safari.

The TrueCrypt licensing doesn't permit relicensing and is incompatible with all OSI licenses, including the 'anti-GPL' MsPL license that VeraCrypt chose.

Ah, did not know that. There's still quite a bit of closed source bits in Chrome (unlike Firefox which is all open source code), but it looks like the PDF viewer is no longer one of them.

Yes and no. Chrome, in general, has more between version patches than Firefox. Version 33 was a notable exception due to the landing of off-screen GPU renderring though. So, even though Mozilla's release cycle is 15 days faster, Chrome is still pushing out more new browser versions. Source: I have to package every version of each for portable use, so I know about every new full version and patch version whereas most local users don't notice due to automatic updating.

> Don't worry about it, next week you'll be running Firefox 35 anyway. Which is funny and all, but you realize that Chrome is on version 39 despite the fact that Firefox is 4.5 years older than Chrome, right?

Firefox has no such issues these days. And Firefox has an open source PDF viewer, unlike Chrome.

It'll start with users on Windows that are using better browsers (Firefox and Chrome as well as variants) as well as some of the 8% of the world that runs Mac who've grown beyond the often-outdated Safari (since it's OS tied and you have to upgrade your whole OS to update it). And it'll start on the majority of smartphone users that use Android. So that means most users can either use this now or upgrade to a better browser that can use this now. It'll come to the #2 mobile OS later once Apple adds it in to Safari but then it'll work for every browser on iOS since every browser on iOS is actually just Safari with a pretty UI on top.

Firefox and Chrome have about equal market share.

Or just use a password manager and you can have unique high entropy passwords for every single site and service without taxing your brain.

Mexico's vaccination rates are higher than the US.