Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Apple Safari users suffer crashes

bbc.com

Post reply on HN
Print view View original

71–80 of 108 posts

Re: Apple Safari users suffer crashes

#71

Post by coldtea »

untog wrote: post #25
k-mcgrady wrote: post #21

Earlier quoted context omitted.

This was driving me mad for ages. I was blaming Twitter and my connection until I finally discovered it was Safari. This was the last straw for me. Having Safari on my desktop synced with my iPhone is so useful. Safari credit card and password storage works better than Chromes (imo) and I find it superior in almost every other way. But with todays issue, the t.co issue, and another issue where my entire Mac would ran…

They both show worrying things to me: - app crashing because a remote server is down? Bad coding. Bad QA. What else is lurking in that codebase? - weird bug affecting one domain? Fix it. Twitter is not a small site. But it's been months and they still haven't fixed it.

>app crashing because a remote server is down? Bad coding. Bad QA. What else is lurking in that codebase?

That happens all the time with all kinds of apps, which nethertheless might be indispensable.

Re: Apple Safari users suffer crashes

#72

Post by culturestate »

paulojreis wrote: post #27
untog wrote: post #16

Earlier quoted context omitted.

I was the same, but eventually Chrome's slowness and resource-intensiveness (this is on OS X, of course) drove me to Safari. Chrome is still my 'dev' browser though, and having the two separate is actually quite nice.

That's my setup, essentially. Chrome as my 'dev' browser, as I'm too familiar with its devs tools. Another nice thing about having a browser only for development is that, when you're demo'ing, there's less of a risk to show unwanted stuff (e.g. address bar suggestions). :)

> Another nice thing about having a browser only for development is that, when you're demo'ing, there's less of a risk to show unwanted stuff

I go a little further and use distinct Chrome profiles for every project to avoid this. It also helps to keep saved credentials for e.g. client-specific SaaS accounts separate without commingling them with my own 1Password vault.

*I know 1Password now supports multiple vaults, but I haven't had a chance to try that workflow yet.

Re: Apple Safari users suffer crashes

#73

Post by iamben »

autoreleasepool wrote: post #6

I've tried to like Safari. It's certainly snappier than the alternatives. It's fast and seems light. I'll go as far as to say I want to like Safari. As a heavy iPhone and Mac user, going all in on Safari would buy me a lot. In a similar vein, I want to like Firefox - even more so than Safari. An open source web browser by a non-profit? Sign me up. That's an excellent concept to rally behind. But... I can't ditch Chro…

'The Great Suspender' has been invaluable for me (a heavy tab user) in clawing back some system resources.

https://chrome.google.com/webstore/detail/the-great-suspende...

Re: Apple Safari users suffer crashes

#74

Post by coldtea »

mbillie1 wrote: post #34

Safari needs to start respecting HTML5 input validations.

From all the things mentioned in this post, that's probably the last thing it needs.

Most browsers out in the wild don't support them anyway, and that's something for developers to worry -- most pages implement their own JS based validations on the client anyway.

Re: Apple Safari users suffer crashes

#75

Post by culturestate »

acdha wrote: post #46
untog wrote: post #38

Earlier quoted context omitted.

If you read the article you'll see an Apple engineer confirm it is a problem with Apple's code.

They confirmed that they're working on it but it's not clear that it was a purely a problem with Apple's code. Given all of the well-documented general stability problems t.co has had over the years it would not surprise me to learn that Chrome has a more aggressive recovery mode from a bad DNS server, failures returned by only one of the multiple servers which that hostname resolves to, etc. I've seen plenty of t.co…

When Hatcher said it was "lower level than WebKit," I took that to mean it has something to do with iOS/OS X's built-in Twitter integration.

Re: Apple Safari users suffer crashes

#76

Post by darkr »

FungalRaincloud wrote: post #53
diggan wrote: post #9

Earlier quoted context omitted.

I can't ditch Firefox for the exact same reason! I NEED to have my tabs on the left side or the right side. I can't have it in the top because I end up not seeing any titles, just favicons, and that doesn't really give me anything. Try the Firefox Developer Edition or Aurora (Alpha channel, rarely crashes but the performance is much better than current stable) together with TreeStyleTabs. Maybe that will help you out…

I recently installed vimium on chrome, and being able to quick navigate to a specific tab via keyboard (by typing the title or selecting it from a list) has completely eradicated my issue with finding tabs on chrome. There's something like vimium on Firefox, but I haven't really looked into it. I mainly use chrome because I use chrome. I just don't feel like putting the energy into setting up Firefox how I like it. c…

> There's something like vimium on Firefox

Vimperator. It offers more functionality/hackability than Vimium as well (not that vimium is bad - I'm a happy user of both firefox/vimperator and chrome/vimium).

Re: Apple Safari users suffer crashes

#77

Post by JupiterMoon »

swozey wrote: post #57
cptskippy wrote: post #40

Earlier quoted context omitted.

I don't get how he thinks it's ugly or different. Not only is it very similar but, unlike Chrome or Safari, every aspect of it is customizable so you can make it look however you want. Out of the box you can rearrange the the UI elements to match Chrome or Safari.

I absolutely hate the FF UI. I WANT to use FF, I actually switched a few months ago and did it for a couple of months. I THINK my problem (I say think because I feel like someone will measure the pixel and say I'm wrong) is that it feels like there is a ton of wasted space between the tabs, above the tabs. etc. I can't control the size of the top bars and they're huge compared to chrome. I'm a fan of tiny icons and v…

Hang on the chrome UI at the top takes up a couple of mm more vertically than the FF one. What other differences are there?

Re: Apple Safari users suffer crashes

#79

Post by joesmo »

Upon upgrading to Yosemite two years ago, Safari stopped working completely on two out of my three Macs (one brand new, bought just months before) with the third one intermittently working. Apple's software quality is really a joke and Safari is the new IE in many ways. Its support for standards is behind every other major browser and it hardly ever opens without crashing. Why would I use such shitty software when I'm not forced to? I avoid iTunes for the exact same reasons except when Apple forces me to use it to put music on their devices. The core OS X system is generally solid (other than the myriad of wireless issues Apple can't seem to ever solve) but the apps that come with it range from substandard to total shit quality.

Re: Apple Safari users suffer crashes

#80

Post by corv »

sawwit wrote: post #32
vlunkr wrote: post #18

Earlier quoted context omitted.

This is me exactly. I can't stand the UI in FF. It seems to change too much and it's ugly. There are probably plugins to help with that, but I haven't invested the time to look into it. It's also hard to kick the Chrome dev tools.

How is FF ugly? I don't find the UI very different from Chrome and Safari.

I'd say FF Developer Edition has the best UI out of all of them.

Nothing fits better next to a terminal window or a code editor.

Post reply on HN