Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

I recently switched to Safari for similar reasons.

Safari is much faster than it used to be. It's also tightly integrated with my phone, including password management functionality (similar to LastPass) that works on all my devices. You can also get AdBlock for Safari now, which wasn't always the case. It also has a snazzy built-in RSS reader and just looks better than Chrome.



Exactly, Safari handles 90% of web needs and doesn't clog up my memory the way Chrome does. It handles my battery exponentially better then Chrome as well. Then with adblock plus, lastpass and pocket I'm all set on extensions.


> doesn't clog up my memory the way Chrome

What exactly is "clogging up memory" that everyone here complains about? I can understand if Chrome is using 6 / 8gb of your ram and you are simultaneously running photoshop and it can't grab any memory due to Chrome, but is this the case?

Shouldn't Chrome use as much RAM as it can to ensure speedy performance provided its not starving out any other applications?

I have little experience in writing desktop applications & memory management in an environment of this nature. Genuinely curious what the normal practice is.

Edit: To clarify, I am assuming the memory growth is not due to any sort of leaks :)


Superfluous RAM use hurts battery life a lot. Using Safari over Chrome easily saves 2+ hours for me.


> Superfluous RAM use hurts battery life a lot

Do you have a reference for why this should be? A quick search yields results suggesting only the opposite (for instance, https://superuser.com/questions/738848/does-more-ram-usage-c...).


More ram in use generally means more javascript crap running. Which means higher cpu/energy use. Its not the memory use its what is using the memory.


So...the claim is that chrome runs a lot more javascript than safari?


I'll phrase it more that I see significantly more memory use in Chrome for long lived processes than I do with Safari.

That said, eventually both get to 6g of ram in use and a restart is needed anyway.


Ah could point! I could even imagine scenarios about pre-fecthing content (say loading the next page that may never be viewed) and throwing it in RAM. Definitely would not be good for battery life.

Cheers!


I have seen my battery life improve from 3 hours while using Chrome to 5 hours while browsing the same content using Safari on my MacBook pro. One downside I've experienced with Safari is that it does not reclaim the memory a tab uses after it is closed, which leads to a crash once a day.


My biggest issue with Safari over firefox is location bar - it's simply cumbersome and stupid compared to the Firefox Awesomebar. I like being able to type two distinct parts of a URL or title and that Firefox just groks it.

Otherwise, I agree completely.


I used to love Safari but they've lost me with the direction their UI has taken the last few years. There's something about not showing the full URL by default that bugs me.


I think Apple heard the widespread grumbling about that. Preferences > Advanced > Show full website address




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: