4 ms·
After 5+ years of developing in Chrome Dev tools, I switched to Safari 2 weeks ago (Mac) and couldn't be happier. Chrome has become bloated. Ever notice CPU f
by billions 10y ago
After 5+ years of developing in Chrome Dev tools, I switched to Safari 2 weeks ago (Mac) and couldn't be happier. Chrome has become bloated. Ever notice CPU fans ramping up? Only while Dev Tools is open. Memory hog is an understatement. Furthermore, while Chrome's light, prebundled Flash was an asset 3 years ago it's now a liability: most websites now gracefully fallback to HTML5 video. Safari's upcoming leading edge standard support announcement makes it a candidate for best dev browser. (Hint: try Safari's Responsive Mode)
- deleted 10y ago[deleted]
- Flow 10y agoMany news sites insist on Flash still. The shitty thing is that if you use the Developer menu in Safari and change user agent to iPad Safari they often play the video using html5.
- jayflux 10y agoThat's by design. Please read the "Are you planning to add support for Safari on Mac OS X?" bit on http://www.bbc.co.uk/blogs/internet/entries/8be5501d-43e7-4bf6-8f1e-e7037980a0f0 http://www.bbc.co.uk/blogs/internet/entries/8be5501d-43e7-4b...
- cel1ne 10y agoIs the profiler still tracing instead of sampling? I once lost a day optimising frequently called JS-methods only to realise that the profiler caused the time spent there.
- drinchev 10y agoI switched to Safari 2 months ago for the same reasons as you did. Definitely feels better speed-wise. Also with iCloud keychain I decreased 1Password usage. For development though, I still can't get use to Safari's developer tools.
- matt4077 10y agoPage loads feel faster in Chrome for me, but yes, the dev tools are much cleaner. There are at least worth a second look if you can't find the bug in chrome.