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

11–20 of 108 posts

Re: Apple Safari users suffer crashes

#11

Post by harryf »

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…

For me it's the address bar - (desktop) Safaris hiding of everything to the right domain name annoys me - over hiding useful info

Re: Apple Safari users suffer crashes

#12

Post by untog »

harryf wrote: post #11
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…

For me it's the address bar - (desktop) Safaris hiding of everything to the right domain name annoys me - over hiding useful info

You can change that - "Show full website address" in Advanced options.

Re: Apple Safari users suffer crashes

#13

Post by amelius »

Anybody else noticed how Safari doesn't seem to get Javascript exceptions right? Errors often have no stack trace, or their information is of limited use.

At least, that is what I am experiencing lately.

Chrome/Chromium, on the other hand, almost always gives me the information I need.

Re: Apple Safari users suffer crashes

#14

Post by germanier »

harryf wrote: post #11
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…

For me it's the address bar - (desktop) Safaris hiding of everything to the right domain name annoys me - over hiding useful info

You can change that by going to settings. In the "Advanced" tab you can check "Show full website address".

Re: Apple Safari users suffer crashes

#15

Post by rangibaby »

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…

I think you're just used to Chrome. There isn't really that much seperating Chrome, Safari, and Firefox these days.

Re: Apple Safari users suffer crashes

#16

Post by untog »

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…

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.

Re: Apple Safari users suffer crashes

#18

Post by vlunkr »

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…

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.

Re: Apple Safari users suffer crashes

#19

Post by gruez »

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…

disclosure: I'm a firefox user.

>I think it's the tabs. [...] It's also the best file downloader

In what way? The only difference I can see is the download status bar, but that's available on firefox as an extension.

>the most configurable

debatable, considering firefox has a bunch of about:config options, whereas chrome has a few configurable flags.

>has the best extension ecosystem.

Can you elaborate this? My impression was that firefox's ecosystem was better because addons can do more (thanks to XUL), whereas chrome addons are limited to glorified userscripts.

Re: Apple Safari users suffer crashes

#20

Post by acdha »

amelius wrote: post #13

Anybody else noticed how Safari doesn't seem to get Javascript exceptions right? Errors often have no stack trace, or their information is of limited use. At least, that is what I am experiencing lately. Chrome/Chromium, on the other hand, almost always gives me the information I need.

No, but if you're relying on sourcemaps to get useful information you might want to confirm that the toolchain is producing fully-valid sourcemaps. I saw some very odd failures while that stabilized.
Post reply on HN