Apple Releases Safari 8.0.1, 7.1.1, and 6.2.1 [Update: Pulled]

apple should just stay away from any "8.0.1" update lol

Battery life has improved, haven't downloaded it yet.

Sneels fappier.

Its a limited, collectors edition browser.

Snow Leopard OSX 10.6

There are still a lot Snow Leopards out there. I wish Apple would grants us one more update Safari (PLEASE!). #

OK thanks for sending a browser update before an update to fix the wifi connectivity issues. :rolleyes:

I for one have gone back to mavericks and the older versions of Itunes and ditched safari for chrome.

I too have gone back to Mavericks. What's sad is that in another year or two Apple will cease support for Safari on older systems for no reason other than to push you to upgrade.

You'll have to move to Chrome or Firefox if you want an up to date browser. :(

Safari was a turd on Windows.

Firefox, Chrome & IE 11 are great browsers on Windows 7 & 8. As you are a bit weird and think your info is being syphoned off I'd recommend Firefox.

Safari is a turd on OSX :cool:

OK thanks for sending a browser update before an update to fix the wifi connectivity issues. :rolleyes:

You have a very naive way of software development.

Software Developers in companies like Apple are usually experts on a very particular area. A Safari engineer might be an expert in implementing HTML rendering, or in writing fast Javascript interpreters. But she might have little knowledge about drivers and wireless technologies.

You can't just tell her to help the Core-Wireless team. Her knowledge about HTML and Javascript is of no use over there. She could probably learn that stuff and become an expert in this area as well. But depending on the particular area we are talking about that might take a lot of training which costs a lot of time and money, because while in training software developers are not very productive. Wireless technologies is such a field were problems are very complex and experts are very hard to find.

And because of this and many other reasons it generally does not help to throw more personnel on development teams.
Or more colorful: that one woman can have a baby in nine months does not mean that nine woman can make a baby in one month.

That's why developers work best in small and medium teams that are for the most parts independent of each other. It does not make any sense to put them all onto the same subject. And you don't want to send all other developers on vacation while the Core Wireless team tries to fix issues.

And that is why Apple sometimes fixes things first that are less important (for you).

You think Tim Cook is responsible for the bad code?

He is not directly responsible for each code. But if the same **** happens over and over again, previously iOS now OS X, he is definitely responsible.