Forum Moderators: travelin cat

Message Too Old, No Replies

Memory Bleed?

Safari RIP'ed on me this morning

         

Russ49Checkmate

4:06 pm on Sep 2, 2004 (gmt 0)

10+ Year Member



Cross-Referencing to the Thurnderbird thread, I think Netscape is the best for a browser and e-mail together, if they'd only have added a simple FTP client, I'd have been in heaven ...

... However ...

I gave up on it because it was very crashy on Classic. Apple gave me Safari with the iMac and I gave it a whorl and it's been really good until today. I'll not bore this forum with the details, us Mac users are all too familiar with the problem I'm having.

So what's the deal here? We've been developing http clients now over ten years, why can't anyone get it right? I've tried out all the main ones over the years, Cyberdog, IE, Opera, Netscape, Safari; I long for the days when Mosaic was still being developed ... sigh ...

My question is whether this is mostly a problem related to Microsoft's marketing approach with IE, or is there actual technical issues?

mivox

8:34 pm on Sep 2, 2004 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member



Have you tried the latest FireFox? Everyone I've heard who's tried it (myself included) fell in love.... And the minimal problems I do have with it mostly relate to webmasters installing bass-ackwards, out-of-date browser sniffers, or other IE-only javascript.

Then again, I'm a fan of single-purpose software too. I'd rather use Firefox, Eudroa and Fetch than some behemoth all-in-one "Internet Program".

dcrombie

10:18 am on Sep 3, 2004 (gmt 0)



The "problem" you refer to is that there are an 'infinite' number of web pages, most of which don't follow any kind of standard (or at least not very well) and any browser that wants to be recognised needs to render at least 95% of them. M$ has exacerbated the problem - either with the goal of crushing Netscape or through sheer incompetence.

The only problem I've had with Safari was the 'hangs' caused by having "Autofill forms" on - this is a documented bug and the problem (apparently) is in the OS rather than the browser.