Looking forward to what the web is going to be offering over the next year or so.
Hardware-accelerated rendering (2d)
Hardware-accelerated flash
Non-flash interaction and video
etc
The static pipes sound like a really cool setup, but I can imagine they have the potential to be utter nightmares for server-side people if things aren't managed perfectly.
No specifics were mentioned in the presentation, but we can assume that the 64-bit build of Firefox will support 32-bit plugins. It'd be pretty useless to users if it didn't.
64-bit builds of Firefox in Linux have taken advantage of 32-bit Flash plugins for a while - I imagine they've figured a fair bit of it out.
I don't know if I'm a huge fan of moving to the Chrome UI paradigm of tabs above all else, but I'll give it a shot, at least. Here's hoping it's much faster and a bit more stable... my install has been prone to crashes of late.
^Seconded. Mac needs the ability to right click on a book mark, that drives me a little nuts.
FF4 so far looks like good and will keep me cemented in Fire Fox as my main. I keep trying Chrome with each build and just don't like it. The speed gain is so insignificant the rest of the stuff I don't like is.
When I first upgraded to Firefox 3.0 from the previous version, its noticeably better performance and less memory usage was a very pleasant surprise. Firefox 3.5 has been an insignificant upgrade compared to 3.0, but it is a minor revision anyway. If 4.0 can repeat the what 3.0 did, I will be more than happy. I have been using Firefox 3.5 on more than 5 computers with Windows XP, Windows 7, and Ubuntu with 100% stability. I am so content that I have not tried any other browser. IE8 does not count as a browser.
That seems to help a lot of people, who are basically doing that by switching browsers. Having a years-old Fx profile versus a brand new Chrome install always puts Fx at a disadvantage in comparison.
There's been craploads of effort put into memory use reduction and performance increases, even on Fx 3.6. Chrome is actually more of a memory hog than Fx these days, sometimes by an order of magnitude.
Thrax
🐌Austin, TX Icrontian
Comments
Hardware-accelerated rendering (2d)
Hardware-accelerated flash
Non-flash interaction and video
etc
The static pipes sound like a really cool setup, but I can imagine they have the potential to be utter nightmares for server-side people if things aren't managed perfectly.
(Still no 64 bit flash for windows)
I don't know if I'm a huge fan of moving to the Chrome UI paradigm of tabs above all else, but I'll give it a shot, at least. Here's hoping it's much faster and a bit more stable... my install has been prone to crashes of late.
FF4 so far looks like good and will keep me cemented in Fire Fox as my main. I keep trying Chrome with each build and just don't like it. The speed gain is so insignificant the rest of the stuff I don't like is.
http://support.mozilla.com/en-US/kb/managing+profiles
That seems to help a lot of people, who are basically doing that by switching browsers. Having a years-old Fx profile versus a brand new Chrome install always puts Fx at a disadvantage in comparison.
There's been craploads of effort put into memory use reduction and performance increases, even on Fx 3.6. Chrome is actually more of a memory hog than Fx these days, sometimes by an order of magnitude.