Comments on: Back to Safari http://terrychay.com/blog/article/back-to-safari.shtml You tell that other boy, not to touch the woodwork... Tue, 06 Jan 2009 08:15:59 +0000 http://wordpress.org/?v=2.8-bleeding-edge hourly 1 By: Andrew Mager http://terrychay.com/blog/article/back-to-safari.shtml/comment-page-1#comment-292348 Andrew Mager Wed, 19 Dec 2007 10:29:10 +0000 http://terrychay.com/blog/article/back-to-safari.shtml#comment-292348 It's weird how we just expect software to work all the time. I think Firefox is still broken. It’s weird how we just expect software to work all the time. I think Firefox is still broken.

]]> By: tychay http://terrychay.com/blog/article/back-to-safari.shtml/comment-page-1#comment-107192 tychay Fri, 22 Jun 2007 10:35:20 +0000 http://terrychay.com/blog/article/back-to-safari.shtml#comment-107192 <a href="http://www.xxeo.com/archives/2007/06/08/whats-up-with-firefox.html" rel="nofollow">Dru noticed the same things</a>. The hanging cursor is especially annoying. Dru noticed the same things. The hanging cursor is especially annoying.

]]> By: Ed Finkler http://terrychay.com/blog/article/back-to-safari.shtml/comment-page-1#comment-107023 Ed Finkler Fri, 22 Jun 2007 02:27:20 +0000 http://terrychay.com/blog/article/back-to-safari.shtml#comment-107023 FF is particularly slow on OS X. It still leaks on Windows (see my twitter about that the other day), but it doesn't seem to have the same severe performance issues. You should check out the web inspector stuff in the newest Webkit builds -- it's really good, and pretty comparable to Firebug. It lacks the JS debugger with breakpoints and watches, but I don't use that *too* often. FF is particularly slow on OS X. It still leaks on Windows (see my twitter about that the other day), but it doesn’t seem to have the same severe performance issues.

You should check out the web inspector stuff in the newest Webkit builds — it’s really good, and pretty comparable to Firebug. It lacks the JS debugger with breakpoints and watches, but I don’t use that *too* often.

]]> By: tychay http://terrychay.com/blog/article/back-to-safari.shtml/comment-page-1#comment-106840 tychay Thu, 21 Jun 2007 19:25:18 +0000 http://terrychay.com/blog/article/back-to-safari.shtml#comment-106840 Well yes, in defense of Mozilla, I could say that half the sites now don't work with Safari so I never got myself into a position to crawl it the way I do Firefox. :-D OTOH, I’m serious. Why did people move to Firefox in the first place (besides the developers)? I’ll tell you what it wasn’t for: it wasn't for the built-in RSS reader. I'm liking the performance improvements mentioned in the Ars Technica article I linked, and I hope that Mozilla doesn’t forget what brought them to the position they are in while they chase the next big thing. Well yes, in defense of Mozilla, I could say that half the sites now don’t work with Safari so I never got myself into a position to crawl it the way I do Firefox. :-D

OTOH, I’m serious. Why did people move to Firefox in the first place (besides the developers)? I’ll tell you what it wasn’t for: it wasn’t for the built-in RSS reader. I’m liking the performance improvements mentioned in the Ars Technica article I linked, and I hope that Mozilla doesn’t forget what brought them to the position they are in while they chase the next big thing.

]]> By: tobjar http://terrychay.com/blog/article/back-to-safari.shtml/comment-page-1#comment-106797 tobjar Thu, 21 Jun 2007 18:15:11 +0000 http://terrychay.com/blog/article/back-to-safari.shtml#comment-106797 <i>At work yesterday we were talking about how slow Firefox has become. </i> i don't think you can entirely blame firefox. I think it's a combination of: 1) more sites using Javascript. 2) Firefox (and other browsers, to be fair) leaking memory like CRAZY (and not properly garbage collecting it) when it encounters Javascript, even well-developed javascript (which probably makes up 5% of the js out there). A couple gmail, google reader tabs will shoot my FF CPU and mem up to 80%. There are sites that I know will immediately kill my browser under the JS load (ie, the dojo toolkit doc page. way to demonstrate why I shouldn't be using your library guys!) It also seems that firefox has made it *easier* to open up a billion windows with middle-clicking and decent tabbed support. In the 'olden days', you had to right-click/open new browser, and the taskbar clutter discouraged having too many windows open at once. Now, I might only have four firefox taskbar icons open (yes, i hate taskbar grouping), but easily 60 tabs open between them. I don't think I ever opened 40 sites at once before tabbed browsing (because that'd just be crazy). Heck, I probably open 6-10 tabs five minutes after starting my computer -- in 2000 that'd amaze the sales guy ("whoa look at all those browsers you got open!"). At work yesterday we were talking about how slow Firefox has become.

i don’t think you can entirely blame firefox. I think it’s a combination of:

1) more sites using Javascript.
2) Firefox (and other browsers, to be fair) leaking memory like CRAZY (and not properly garbage collecting it) when it encounters Javascript, even well-developed javascript (which probably makes up 5% of the js out there).

A couple gmail, google reader tabs will shoot my FF CPU and mem up to 80%. There are sites that I know will immediately kill my browser under the JS load (ie, the dojo toolkit doc page. way to demonstrate why I shouldn’t be using your library guys!)

It also seems that firefox has made it *easier* to open up a billion windows with middle-clicking and decent tabbed support. In the ‘olden days’, you had to right-click/open new browser, and the taskbar clutter discouraged having too many windows open at once. Now, I might only have four firefox taskbar icons open (yes, i hate taskbar grouping), but easily 60 tabs open between them. I don’t think I ever opened 40 sites at once before tabbed browsing (because that’d just be crazy). Heck, I probably open 6-10 tabs five minutes after starting my computer — in 2000 that’d amaze the sales guy (”whoa look at all those browsers you got open!”).

]]>