Slashdot Mirror
Firefox 3.1 Beta 3 Released
ink writes "Mozilla has released the third beta for Firefox 3.1 (which may become Firefox 3.5). This beta includes the new location bar, Mozilla's new JavaScript engine Tracemonkey, new HTML5 features and many other enhancements. It looks the same on the surface, but there are many changes under the hood."
How pretty much everything we do uses JSON and until now there has been no love from the browser.
My question is, will all these new JavaScript goodies (both in Firefox and in IE8) get rolled into jQuery? That way if jQuery sees the browser can do JSON serialization, or timeouts on XHttpRequests, it will use the native stuff instead of emulating the behavior?
I'm gonna have to play with the VIDEO thing. The big problem such a new feature will have is codec support. Nobody is gonna transcode their streaming content to use this thing when they can just use flash player. That and I really dont want "normal people" trying to find codecs on google--most of the hits for "$AWESOME_CODEC" are usually just spyware installers.
FF isn't EVER going to have a pre-emptive threading and protected memory for tabs. Anyone who has taken a look at the stinking pile of shit that is the FF codebase can see that. It would require effectively rewriting the entire FF codebase from scratch. And if you were going to do that you might as well just go with Chrome that already has all of that fundamental work done and working incredibly well.
It is absolutely pathetic that Microsoft now has a browser that is the constant source of ridicule from open source users and developers that leaves their main browser technologically in the dust.
Chrome - pre-emptive threading and memory protection for tabs
IE 8 - pre-emptive threading and memory protection for tabs
Firefox - monolithic address space and all tabs are part of the same thread
Absolutely embarrassing.
What that means is Firefox will forever be riddled with memory and resource leaks over time as each tab gets opened and close leaving crap behind. And as more and more websites become more application like the lack of pre-emptive Javascript for Firefox is just going to become more and more painful. With Chrome and IE 8 you can have massive numbers of tabs with huge amounts of Javascript in each one and every single tab and the overall browser UI will remain lightning quick.
Everyone remembers FF devs flaming people in those FF memory leak stories from a few years ago. The anger comes from the fact they know they have a huge problem with the way FF is architected. Lashing out is a very common reaction from developers who are aware of some fundamental problem with their code that they know would require massive amounts of work they are unable or unwilling to fix.
The FF devs got away with it because they were compared to the horrible mess that IE was back then. Now IE has really gotten its shit together now with it great leaps forward with javascript performance, threading, and memory protection.
With Chrome and its incredibly clean and modern code base and extensions soon to arrive and the Linux version rapidly maturing, the only reason to keep using FF will be misplaced lingering fanboyism from the "IE sucks! I use FF so I'm cool" days.
Finally..finally!
Now I think I an transcode my snapshot video footage into a format that I don't have to worry about for ...at next 5-10 years.
The memory protection side of the multi-process implementation in Chrome results in incredible stability.
But, the preemptive threading of the multiple processes for tabs gives it a massive performance boost above Firefox in real world conditions.
It doesn't matter how much is going on in other tabs and Chrome will feel just like a single tab is open. What is most amazing about Chrome is I've left it open for close to a month and it still feels like I just started the app up with a single tab.
Firefox you pretty much have to quit a few times every day or you start to notice that the UI begins to get slower and slower as more tabs are opened and closed.