I used to be like that but ever since I found my fans not spinning and the extra 2 hours of battery life under Safari, I haven't gone back to Chrome.
Truth be told, I have stability issues with Safari (and sometimes opening up new blank tabs takes 5 seconds... kind of ridiculous) but I prefer that my laptop not get too hot.
I'm heavy trackpad user (on macbook) and any browser except Safari is just terrible for me. Scrolling is terrible and laggy, random guestures I didn't want to issue, etc.
And icloud tabs, reading list, etc are very handful, because sometimes I want to use iPad instead of computer.
This happens to me all the time. So annoying... feels like something to do with how it locks the scroll direction when you first start the gesture. So even a perfectly vertical scroll will result in a back if the initial jitter has locked a horizontal motion.
Not the OP, but I found that Google Play Music wouldn't work with Flash disabled in Safari, but also wouldn't tell me why. I had to manually enable it, then it worked fine.
Does safari work better? I deleted or disabled it, and stopped using it for a while. After upgrading to yosemite I haves used it a bit. Mozilla firefox seems to crawl. Even with tab focus and other performance settings the fan seems to turn on after lengthy use and dev tools would just spin the beachball.
I am considering safari seriously as a primary browser unless I can find a way to optimize Firefox. How has your experience with safari been?
Software shouldn't be able to (and can't, I'm pretty sure) cause the hardware to literally overheat, such that it's damaged. But it can easily cause the hardware to become uncomfortably hot, because the hardware is more tolerant of high temperatures than squishy human flesh.
On chrome or Safari? Someone did a comparison of all the different blockers on HN a few weeks ago and I found out about uBlock Origin. But they didn't support Safari.
Have you owned a Mac laptop before ? The aluminium case is a giant heatsink and it's very common for applications to cause the laptop to become hot. Sometimes unbearable so.
It's well known that Safari is significantly better than Chrome when it comes to resource consumption. There are even some podcasts with ex maanagers of the Safari team where they talk about Apple prioritising battery life over anything else.
I used to be the same - I used Chrome as my "dev" browser, and Firefox as my "actual" browser. But Firefox has gotten worse and worse (hanging, slow response, etc) for no discernible reason (i.e. I disabled all the extensions and it was still bad).
So I gave Safari a try. And it's actually... fine. Nothing mind-blowing whatsoever, but has all the features I needed in Firefox. My one irritation is the trackpad gestures I don't want. A good few times now I've accidentally gone back by swiping with two fingers, zoomed out to tab selection by some oversensitive pinch gesture, etc etc
I'm in a similar boat. Safari has surprised me lately - particularly its speed.
That said, there are a couple things that always frustrate me with stock Safari:
1) You can't reopen an arbitrary number of recently closed tabs. (You can use Command+z to "undo" closing one, but if you've closed two, or three, you're out of luck. I prefer how Chrome handles this. Though perhaps there are good reason to avoid this feature.)
2) Tabs don't have a favicon. They may be ugly sometimes, but with many tabs open favicons really simplify navigation. Of course, this can be fixed via 3rd party SIMBL extensions.
Otherwise, using Safari has certainly been better than I expected.
> Requirements: Live streaming uses Apple’s HTTP Live Streaming (HLS) technology. HLS requires ..., or a PC with Microsoft Edge on Windows 10.
Interesting. They are limiting it to their own devices and software, except they allow Microsoft Edge. Is there a technical reason for this? Couldn't Chrome/Firefox work? Strange that they would give Edge an exception.
I think this is one of Apple's semi-standard protocols that just happens to be supported by Edge, not that Apple is "allowing" Microsoft's browser in any way.
Chrome supports its own streaming method, MPEG-DASH with H.264 which is what Youtube runs on where possible. Firefox stated it won't support H.264 on principle (although it does now, for WebRTC). Android supports HLS, as does iOS, out of the box. HLS was designed to supersede RTSP however we also have the equally-ubiquitous RTMP, which Flash supports natively. You can get an HLS stream via Flash with an add-on to some clients so now this will work on IE, Chrome Firefox, and there are also some custom, proprietary clients out there for h.264/HLS. It's not a pleasant ecosystem right now..
- Chrome (and other browsers) support MPEG-DASH via javascript through the Media Source Extensions (MSE) (which Safari actually supports[1])
- Firefox does not "bundle" H.264 (because of licensing) but has recently supported it where the OS provides it[2].
- HLS and MPEG-DASH are fairly similar in theory, but in practice HLS requires complete (with header/metadata) chunks whereas MPEG-DASH can "arbitrarily" chunk a video file and just feed into a MSE video stream. Both work with manifest files detailing different resolutions/qualities and chunk sizes + offsets.
Firefox supports H.264 via system codecs, and supports MPEG-DASH as of version 41 (currently beta, will be stable in a few weeks). MPEG-DASH is a more open standard, and has better support for adaptive bitrate streaming, so I think it's likely to become the defacto standard in the future. It's fairly new so isn't supported everywhere yet, but it's getting there, and seems to have a lot more industry support than other options.
and the code is better than I expected from a commercial project, it even uses may_alias properly. I wonder why the decoder doesn't support CPU multithreading, though? Slice threads are pretty simple to add.
Actually HLS is an IETF draft [1], but I'm not sure why Apple never followed through on making it a full standard because it's got a ton of clear advantages to traditional streaming technologies. I think it's more an issue of other browsers not supporting it, rather than Apple stopping them.
OK, this is one of things where you have to be very precise with the terminology. HLS does enforce the use of MPEG-2 Transport streams, but it does not force the use of the video encoding that is packaged in the stream. It is very typical (in fact it's the norm) to see HLS using H264 for the actual encoding work, and MPEG2 TS is actually a pretty decent specification for throwing around video streams.
I don't know that you can really say that DASH is more technologically neutral. I mean what are you saying, that HLS is not technology neutral because it forces you to use an MPEG specification, but if you opt to use an MPEG specification up-front, that's neutral?
Anyway, as someone that writes the client code for these things, I much prefer the HLS approach. If you go the DASH approach, you get into one of several potential messes. Either you have to say that you're only implementing one specific profile, in which case content providers complain that you're not supporting their chosen profile, or you have to write an absolutely massive client that can accept anything thrown at it.
Apple's affection for HLS stems from this same reasoning in my opinion. They too are more concerned about the client side - they want to keep the format simple for clients to handle, so that they don't have to bloat all of their code handling all of the different options. Because don't forget, the servers don't have to deal with this complexity - they choose which bits they want to use and go with it. Clients have to be able to handle everything in the spec correctly.
Seriously, what a shit elitist company Apple is turning out to be. You can't watch this on Chrome or Firefox. You can't watch it on Safari on a PC. Quicktime on a PC gives a friendly "Error 47: Invalid URL. 0".
In the meantime any 15 year old kid can get online and webcast anything they want to millions of people around the world watching on any browser on any device.
These limitations imposed by Apple are purely artificial. There is no technical reason for which they couldn't make this available on any device and any browser.
Unbelievable.
I'm so glad we got our apps off the iOS ecosystem and stopped developing products for free only to bolster Apple's standing. This is not a company you want to partner with in any way unless you happen to be another 800 pound gorilla.
Credit: http://www.networkworld.com/article/2981623/ios/how-to-live-...