taugust04_ai

AppleInsider said:

The previous recovery method, still done by hitting Command-R during startup, restores a Mac to the version of macOS/OS X that it was on before the problems started, blogger Thomas Brand noted on Thursday. The original behavior had been in place since OS X Lion, which shipped in July 2011.

With iOS, some users have complained of slowdowns after major updates. In fact Apple has faced multiple lawsuits over the issue, arguing that company knowingly ignored compatibility issues since it could push people into buying newer hardware.

This isn't true - Macintosh Internet recovery previously installed the original operating system that shipped with the hardware - not when problems were occurring.  This is a drastic timesaver in terms of bringing a machine up to the current OS in an easy fashion if booting from Internet recovery is required.

As for the "slowdowns after updates", its all about the cruff.  As much as Microsoft and Apple have tried, upgrades still never beat a clean install.  I've had friends with Macs and iOS devices with slowness problems, and a clean install usually resolves the issues about 99% of the time.  The problem is that most folks are "lazy" and don't want to put the effort into a clean install.

freeper said:

... 2) Where Google created their own browser from the Chromium open source project - which is also essentially theirs - both Apple and Microsoft essentially cribbed theirs from Netscape and Firefox. (Particularly since the people who created Netscape left to form Firefox after Microsoft bought it.) When Microsoft deviated from the Netscape base in order to try to keep up with Firefox and Chrome they made a mess of things. Apple didn't even try to keep up in the browser wars so they just left it limited, without even trying to compete with Chrome and Firefox on functionality. That is why the very instant I read about the test that Consumer Reports was running, I instantly knew "bug in Safari, or something in the OS that interacts with Safari." And sure enough, even though Apple did their best to obfuscate by (less than truthfully) claiming that the test results were due to "hidden settings that never get used by consumers" they are indeed issuing a bug to fix the problem. And when I say obfuscate ... wow. Every single browser has that disable cache setting. Every. Single. One. And it is not hidden; it is right there in the browser settings. LOTS of people turn it off for various reasons. And you know what? Such as ... when you do "private browsing." That is right. Whenever you do "private browsing" IT ENABLES THAT SETTING. Let me repeat: PRIVATE BROWSING ENABLES THIS SETTING.

Wow... there is so much wrong in your entire long winded post.

First: Google Chrome is a direct descendent of Safari.  For the longest time Google was using WebKit as the rendering engine for Chrome.  WebKit is an open source project managed owned by Apple.  WebKit has nothing to do with Netscape - It's based on/fork of the KHTML project which was mainly used for the Konqueror web browser in the KDE graphical environment on Linux.  Google then forked WebKit to a new code base called blink.  Opera also uses Blink as its rendering engine.  Microsoft never purchased any assets from Netscape regarding the Navigator web browser.  Those were passed to AOL before they were then open sourced, which became the "Phoenix" web browser, and then renamed Firefox.  While Safari doesn't keep pace with all the features that Google Chrome offers, it's still rather current and usually supports the most important parts of the HTML5 standard, and is on a slower release cycle than Chrome and Firefox.  If anyone "cribbed" a project, Google "cribbed" Chrome from Safari.

Second: Private browsing does not disable the browser cache.  What private browsing does do is make temporary locations for your browser cache and cookies for a specific private browsing window.  These temporary locations are then deleted immediately when the private browsing window is closed.  Other web browsers follow the same principal.  This is why private browsing is never a guarantee (and all the browsers warn you of this) of preventing someone to know your web browsing history if they have some type of access to the system while you are performing web browsing.

The preview web site has been updated and all A5 and A5X models have been removed from the supported list.

iPad 2 is on the iOS 10 Preview website, not the keynote.

As for why it's still supported, it's probably something as simple as the iPad 2 wasn't discontinued until March 2014. There are probably still iPads on AppleCare through 2017, so they feel obligated to fully support them until then.

Wow, Apple hasn't had a X.X.6 version since Snow Leopard. I'm wondering if El Capitan will be the last hurrah for a number of older models from the '08/'09 timeframe...