taugust04_ai

sc_markt said:

Did Maverick's get updated or did Apple leave it alone like they did with the recent keychain fix?...

You’re not going to see any patches for Mavericks or Yosemite going forward. They are both end of life now that High Sierra is out. Mavericks hasn’t been patched since Sierra was released. Sierra and El Capitan will continue to get security updates.

asdasd said:

Rayz2016 said:

asdasd said:

quadra 610 said:

asdasd said:

The exodus from Apple is a bit scary. 

Right? This stuff practically never happens.

Everyone at Apple, regardless of position, pay, contribution, and other opportunities, stays at Apple, all the time, for the rest of their lives, even after death. 

Why, I just had a glimpse of a mummified Bertrand Serlet being wheeled toward the Apple HQ cafeteria! I think he's having the veggie wrap.

It was actually very rare to have people leave early or in the middle of their work during Jobs' reign. There were next veterans who were there for 20 years who were the major contributors to OS X and then to the iPhone. 

In the last few years this has been accelerating. 

Didn't Avie Tevanian left during Jobs's reign, while OSX was still half-baked? People come and go from Apple all the time. You only hear about it more because no other company is worth writing about, apparently. 

he had released plenty of OS X versions at that stage. Would be like leaving during the OS X beta program. 

OS X was essentially "beta" software until 10.3.0 was released.

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.