Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
I use Safari as my primary web browser, but only because Mozilla is too slow to load, and Camino has been too buggy and so has Firebird. I will periodically load a page in Mozilla if it doesn't render right in Safari, or if I need security features of Mozilla like telling me the kind of encryption I'm using, but otherwise I stick to Safari. And I always report bugs to Apple through the bug reporter found in the Safari menu. Hopefully all of you are doing the same.
 
Psychological...

Rushed? What difference would it make to ANY of you (who are complaining), whether Apple dubbed the current release version 1.0, or beta 3? Absolutely none. Apple is working to make Safari the best it can be, and every release brings it closer.

It's quite possible that the decision to label this version 1.0 had more to do with MS announcing IE was dead on the Mac than whether Safari was quite ready. But most of us have been saying since beta 2 that it was good to go. So what's the issue?

We all know Safari will get frequent updates. Safari 1.01 or 1.1 is being readied as we speak. Since it's a free application, I just can't see why people are getting their panties in a wad over what version is labelled 1.0 or beta 3 or whatever.

It works fine for me, as it does the majority of other users. So quit yer b!tchin!
 
STOP COMPLAINING!

I have very little trouble with Safari. Sometimes, when I have trouble with a site, I open IE or Netscape and often find that the problems persist. Safari is an awesome, young browser.
 
I found that the public beta right before 1.0 (v67? I dont remember anymore) was the buggiest. 1.0 has been good for me. I've also noticed Safari is a very per-computer program. I think until 1.0 i got smoother scrolling on my 500mhz G4 than my 800mhz iMac G4. Go figure. Some things are still a llittle slow, but in my personal testing Safari has been fastest in benchmarks or at least usable page loads (loads all but one file on a web site and draws it before another browser can). I dunno, Safari just feels like the fastest there is.

Besides after Apple's recent apps (iSync, iCal, iMovie 3) we shoud be damn thankful of Safari's performance/CPU load. :D
 
My two gripes with Safari;

- eBay. Submitting/Revising listings and Country protection page
- BBS. It "unexpectedly quits" when posting to some of my favorite sites.

Originally posted by avus
Apple's criteria for being "buggy" is too stringent compared to, say, Microsoft, IMO.

I agree. It's what makes Apple so good :)

AppleMatt
 
secure site access, advanced pop up blocking

Two things I'd like to see added asap are access to secure sites. I can't use my credit card's site or sell on ebay with Safari, and I'd prefer to.

The other thing is a more intelegent pop-up block. Granted the pop-up blocker is greatest, but if you could choose to block certain windows like the one you're doing random browsing in, and allow pop-ups in the window you're using to access a secure database (which requires pop-ups for data entry), that would just about the best thing ever.

btw Safari load faster and hardly ever crashes unless I've gotten really out of hand with the number of open windows, and down loading.

As far as the local secrure database goes. It looks a lot better in Safari than it does in IE.
 
Buggy?!

Safari 1.0 has been near perfect for me. The only issue I've had is displaying my Outlook Web Access email (for work) and even then it doesn't crash; the page just looks messed up. The beta before 1.0 would crash all the time on me (especially on Yahoo Sports) to the point where I wouldn't even use safari for a lot of surfing. But I have had almost 0 problems with Safari 1.0.

Are there specific sites that people can list that give it problems?

In my day to day surfing, I really haven't encountered anything that Safari can't handle.

-p
 
Well I use Safari reguarly now that we have cable and things work pretty well. Except Java creates alot of headaches, my mom tried to use the USA swimming website which is full of Java and Safari had major coniptions, it was displaying an error message every 4 seconds. Except for that things have been great.
 
This baby is a work in progress. IE is valuable when Safari doesn't cut the mustard. I love Safari, don't get me wrong, but it has a little ways to go before it's perfect.
I'm sure Apple recieved a great number of bug reports and will have a smoother running browser soon.
 
Safari 1.0 has been probably the most reliable browser I've used on both my mac and pc. I agree it has some problems on some sites, but then again I experienced that with Mozilla from ver 1.0 to 1.3.

This probably results from low expectations caused by years of using windows, but I think Safari 1.0 is pretty damn good. :)
 
Re: Safari 1.0 Rushed?


It was my impression that Safari 1.0 was released before the MS announcement regarding Mac IE development. Of course, Apple could have had wind of this before the rest of the world, but that isn't the definition of "announcement" is it?

Apple also had some trade shows coming up and people anxious for a version of Safari that could do tabbed browsing at the least.
 
All this being said, there have been a couple threads over in Slashdot recently that, upon loading, cause Mozilla to crash gloriously. When I try these evil threads in Safari, they load just fine.

My BIG HOPE for the next update will be that they allow us to drag a link to the blank area next to tabs to create a new tab with the linked page loading in it. Mozilla has this functionality and it's so natural, Safari really should have it.
 
yeah, Safari 1.0 is a bit poopy.

BTW - Camino is NOT languishing at 0.7. That is indeed the last official release - but if you want to try it out, make SURE to download the NIGHTLY version -

http://ftp.mozilla.org/pub/camino/nightly/latest/

It does almost everything Safari does, but better. Only wish it could sync bookmarks.

This is updated relatively often. Though with the shakeup at Netscape and such, who knows... hopefully the community will keep Mozilla alive. =)
 
My 10 cents worth...

I'm not sure if Safari is all that bad!? I use it as my primary browser now and there's only one web page I can think of that has problemsloading, there again the same page just doesn't happen in Netscape either.

Safari 1.0 is a sound build. Can it be iproved upon? Yes!

But how many improvements could be made to Netscape or Internet Explorer and look how long they've been around.

Frankly, the faster rendering and easy UI means Safari blows the competition out of the water.

Chris, pro-Safari

Edit: grammar n' schpelling
 
Safari and Mozilla

Safari is not able to get to some sites I need: try http://www.nuemed.com/ and click on the Mac user button!
Mozilla gets through this site, which is a medical management program just as well as IE but NEITHER of these can print out patient appointment calendars. Once you hit the print button--> spinning beachball. In IE for Windows, everything works! You would at least think MS would have kept IE consistent on both platforms (of course, we know they don't and now, probably won't).

Mozilla (nightly builds) is getting better and better and I use it when Safari won't work. As for worrying about Safari's bugs and lack of features... Apple surely knows that the Mac platform has to have a fully functional browser tht keeps pace with Windows IE: otherwise, if Mac users cannot access the Internet properly, Apple WILL lose sales! That might be another opportunity to take legal action against MS which would then basically control all aspects of Web access giving only Wintellers full access... here we go again.
 
good for html, bad for java.

Apple put a focus on supporting standards well, and indeed, that works.
to bad that java, esp. java applets, are for from beeing standardized. Ever since all kinds of companies tried to improve speed on Guis, the 'run everywhere' of java has been torpedized, and as such, Safari represents just another victim of that.

Even though, you can tell where developers did good work - those applets usally run even in safari, and poor work.

However, an applet should never cause safari to crash, no matter how poorly written. crash the java sandbox - ok, don't run at all - ok, but don't cause other programs to crash - thats poor implementation.
 
Safari 1.0 definitely more buggy

I have had more problems with Safari 1.0 than the other betas.

For me the window resize widget and scroll bar widget, randomly get confused and overlap one another rendering the scroll bar widget useless.

The window size is different everytime I initialize safari, rather than remembering the last window size I used.

There are many more web sites that no longer render in safari.

Safari 1.0 has already abruptly crashed and blown off the desktop many more times than the previous beta.

My wife has the same issues on her ibook.
 
Mozilla Firebird?

Has anyone tried Mozilla Firebird for OSX yet? Its still WAY in beta but I've loaded it on ever computer I own and use it religiously day in day out. Not a crash. Not a single problem. Honestly I’ve used various browsers over the years but found myself going back to IE 5 or better simply because I found the Mozilla, Netscape experience lacking. Firebird is another matter altogether. Its fast to open. Fast to render a page and more importantly its stable.
Granted this is on a Wintel box (For the time being) so one's results may very on OSX. If anyone wants to give it a try:

http://www.mozilla.org/products/firebird/
 
I'm really shocked at the amount of people saying how safari 1.0 is unstable.

I've found it to be the most stable version yet. I have not had it quit on me and i use it heavily all day long to test my web development projects. Its the only mac browser that renders anywhere near similar to Win IE 6. Making it easier to debug for both platforms. Its my main browser both at work and home and i've had little problems with it other than it choking on MS IE specific coding practices on certain sites i go to.

I also haven't come across the caching issue yet, but i also dump my cache on a regular basis for debugging purposes.

I'm much happier having safari than i was without it. For me not having a snappy, good rendering browser was the biggest problem for me on the mac. Chimera was ok but i think safari is so much better.
 
Originally posted by Macmaniac
Well I use Safari reguarly now that we have cable and things work pretty well. Except Java creates alot of headaches, my mom tried to use the USA swimming website which is full of Java and Safari had major coniptions, it was displaying an error message every 4 seconds. Except for that things have been great.

I checked out this site to see what you were talking about as i have not seen any problems with safari and java.

The site you are talking about uses javaSCRIPT, not java, and the error message was not an error message, that pop up is a javascript alert function (probably a poorly coded) .

We use quite a bit of javascript here at work and i have not had any problems with my javascripts in safari if they are properly written.

some people only test in explorer so they never realize their coding errors, explorer for windows is pretty forgiving.
 
Apple would be smart to do incremental updates ever 2 months or so to get safari running tip-top shape. They should not update it once a year at expos, or including it as a "feature" of a new OS.

While I have had some problems (admittedly much less than some other people have had) it i most definitely my primary browser. IE out of my dock. And believe me that is a big deal-everything is in my dock. Once it goes it, it does not come out. I don't like change.

But I don't like IE even more than I don't like change. :)
 
no problems here

not sure what all the fuss is about either. I have been very happy with Safari.. my primary Browser. I occasionally need to use Camino, but that's just when I'm trying to use one specific feature of my online banking service. on a regular basis I can use Safari.. the only problem I have is if I want to "Transfer Funds" from one account to another.. then I have to use Camino for that session.
 
Doesn't surprise me a bit that safari 1.0 was rushed. That piece of software had more bugs in in than something that has a whole lot of bugs in it. Hopefully they will fix these and get a stable browser out soon.
 
Like others, I find Safari's performance on Javascript pages to be uneven. ESPN.com is an example: sometimes it loads fine, sometimes the formatting is all screwy, sometimes there are no scrollbars, etc.

I'd like to see Safari offer some user settings on caching. As I am usually on a broadband connection, I've really no need to have a bunch of stuff cached, and would love to be able to turn off caching. I consider inaccurate (old) image rendering to be more of a problem than milliseconds-slower load times.

And, I agree with the crowd: 1.0 seems to crash more than any prior version, and though this is seemingly unrelated, even more so since the most recent Security Update.

Still, it is my primary browser and it beats the pants off of IE.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.