Exactly. Occasionally I'll give Chrome, Firefox, among others a try, but I keep coming back to Safari. I hate the way the other browsers look, especially Chrome, and Safari is super quick while being easy on the battery.
Its being the only major browser that respects battery life is pretty much the only reason I use Safari. It hurts to see that "time remaining" indicator drop by 2 hours just because I have Chrome open.
I really miss Chrome's multi-profile support, but it's just so much heavier. Last time I used Firefox (admittedly ~3 years ago) it was even worse. System-wide beachballs. Much worse than having Eclipse open. That's what got me to switch to Chrome for a time, after being a FF user since the Phoenix/Firebird days.
That's because Apple actively provides Safari with advantages with regards to API access and performance. They royally screw over the other browser vendors.
Apple also owns the app store and the default configuration of the OS is moving towards only allowing app store software (has it already finished that transition)?
They can and will reject anyone who uses private apis that they themselves use.
In addition, because they own the OS they can require that a private API is only accessed by software signed by them.
It also could cause firefox to break on OS updates and would require firefox to keep abrest of those changes.
You can still install any software you want on your Mac. As that bugzilla page says, Firefox already uses plenty of private APIs, so this doesn't seem to be a big deal in practice. And Firefox was not rejected from the App Store, another XUL client was (IMVU).
> Safari is super quick while being easy on the battery.
That's not surprising, considering it's the only product not forced to use the public web view object in iOS. It's like Microsoft Office, which has always used private MS apis that other products running on Windows were not allowed/supposed to.
