Sometime ago I ranted about the fact that Firefox sucks when opening loads of ajax-ed websites. The posting, however, tend to draw more flame than discussion for its solution, unfortunately. Maybe I titled the post too harshly, as you can read the flame that ensued in a forum thread regarding this topic. But anyway, it’s still a fact.
A few days ago however I found a possible solution for it – Camino.
The description from Apple’s download site is “Mac OS X native web browser combining the Gecko rendering engine with Aqua user interface.”
I found this interesting.
Firefox uses XUL for its user interface, which is rendered by its internal Javascript engine which also renders the opened websites. Therefore, a slow ajax-ed website will also slow down Firefox’s user interface, or even making it “hang”.
Since Camino uses Mac OS X’s Aqua for its user interface, I guessed it will not suffer from the same problem as Firefox.
So far, I think it’s been proven true 😀
I’ve been browsing heavily with Camino v1.5.1 for several days now, and it’s on par with Opera, if not faster.
Here’s saying a big THANK YOU to the people at the Camino Project team.
What a relief it is to be able to browse with the Gecko rendering engine again, without the slow down of Firefox.
Gripes
No product is perfect, of course. Camino, for example, doesn’t support Firefox extensions. This is only natural, since it doesn’t have XUL, which is required by the extensions.
However, feature-wise, it’s already quite fully loaded. And you can add some more features to it via the nice PimpMyCamino.com website.
Now I’m happily browsing at full speed on this 512KB internet connection 🙂
Summary
If you’re using Mac OS X, do give Camino a try. If you are not, you can try Opera,
By the way; Safari sucks. Apple says that it’s the fastest browser – hello ? No bloody way 🙂
While Firefox usually chokes up when I opened about 25 websites simultaneously, Safari already choked on about 10 websites, or less. And while Firefox will recover after a while, or restore your session if it crashed, this is not the case with Safari.
Only use it for light browsing, or avoid it altogether.
i don’t know, but here, camino is always having problems with big downloads. when i need to download something big, i usually switch to firefox or even wget 🙂
kelemahan camino yg fatal bagi saya adalah masalah penyimpanan passwordnya.
saya punya beberapa account google, tapi camino cuma bisa ngesave satu doang…. 😀
udah itu aja. jadinya gag mikir mikir lagi untuk pindah lagi ke firefox.
I use Camino and WebKit (Yeah, it’s Safari’s engine) – http://webkit.org/ , both are great, fast and reliable (of course WebKit crashes more since I am using the Nightly Build – but it’s not choked so easily as Safari).
Overall, I like WebKit better than Camino, but comparatively both are great.
Awesomely fast yet no RSS reader support. Sorry, Firefox does more even it’s not fast.
Firefox does suck sometime. Humongous 50MB LRU cache really kills.
Related to your “claim”, you should have provide some sort of benchmark number, or else it’ll be vaporware :p
I’m now 31337 coder, nor I know the internals of Moz/FF. But I’m pretty sure that they won’t put the task for rendering webpage in the same pipe to render FF UI. I mean, that’s supposed to be what thread are here for right? Or I suppose :p
There may be many stuff causing Firefox to be claimable as slow. One can be those threadless javascript you’ve mentioned, other may be memory leak, other may be not good enough cache management (IO wise). Bah, I start talking like an expert :p
Fear not, the slowness issue has received some love. There’s a patch I found in some planet (Fedora? Gnome? Debian?) made by Mr. Federico to enhance FF image caching. I was able to compile it but FF 3alpha just crashed now and then. Don’t know whether it was the patch or the nightly build which triggered it.
Long live browser war! 😀
I may have been wrong: http://slashdot.org/comments.pl?sid=306595&cid=20730691
Does that former link should have been in your post? 😉
@toni –
But I’m pretty sure that they won’t put the task for rendering webpage in the same pipe to render FF UI
.
See this, this, this, and this.
@toni – yes, discussion about this can be found in many places in Slashdot. I’ve included one of it in my previous post.
I’d still have to take Firefox, for RSS support and SEO addons (which I’m pretty much reliant on these days).
I have been using Camino for Mac Pro a while now and I love everything about it. It is just as good as Firefox, if not, better.
I agree, Camino is faster and a lot better than Firefox.
A very informative and helpful blog. Enjoyed reading it and the tips were great and truely helpful. Keep it up.
Blog bookmarked and emailed to some friends.
i don’t know, but here, camino is always having problems with big downloads. when i need to download something big, i usually switch to firefox or even wget
I really enjoy using camino because I think it’s the fastest and it’s the best to use.
Thanks for the information, I will have to try this web browser. I liked safari too!
Very cool, thanks for taking the time to post!
Firefox is still my preferred browser. 🙂
Chrome is catching up. The best is yet to be from google.
I’ll go with firefox. lot of add ons that make my life easy
I really liked this good and excellent information post. Thanks for sharing this post.
Offering quality LV products with favorable prices, Louis Vuitton Outlet store is at your service. Hurry up, or you can not seize the chance.
Offering quality LV products with favorable prices, Louis Vuitton Outlet store is at your service. Hurry up, or you can not seize the chance.
العاب ودردشة منتديات بناتى
موقع تصميم التقنى
منتدى بناتى
منتدى تصميم
العاب بنات لها
Le monde de la médecine