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.
As usual with Firefox features, if you don't like it, you can probably fix it. Try the oldbar extension. There is probably a way to disable it without an extension, ISTR there is a setting in about:config for 3.0 at least, but you can google that yourself. Personally I love the awesome bar, although I don't think I will flip out about the new version for a whole 6 months, but each to their own.
Oh no... it's the future.
Uh, yeah, you do if you're running 3.1b2. They have a beta update channel.
It looks like they did. Firefox 3.1 beta 3 is still not available on the All Betas page, and when you click on the Download Now link on the Release Notes page, you get Firefox 3.1 beta 2.
The release linked to in the summary may not be the final, completed version, as Firefox 3.1 beta 3 has not been officially released yet. Download it at your own risk. You should wait until it's available through the links I give in this post.
What a fool believes, he sees, no wise man has the power to reason away.
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.
Hey everyone - glad you're excited about the new beta, we're pretty excited to release it. We actually haven't finished the QA on the download page, the update snippets, etc, yet. What you're seeing here is that last night we started sending out the final bits to our mirror network. So yes, you could go get it directly off the FTP servers, but that can overload mirrors and make it hard for other people to download it.
We'd prefer if you waited a few hours until about 2pm PDT when we'll be ready to update:
http://www.mozilla.com/firefox/all-beta.html
which uses our mirror-rotation script to ease the load of downloads.
Mike Beltzner
Director of Firefox Development
"Yes, many people are actually refusing to upgrade because of it."
Do you mean many as a lot of people or many as in a very vocal minority?
Knowledge is power. Knowledge shared is power lost.
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.
Flameware sounds like a great name for some forum software.
He means people who still wear onions on their belt because that was the style then, and they'll be damned if they look for something new.
My blog. Good stuff (when I remember to update it). Read it.
>So after shoving a freaking DATABASE into Firefox 2,
yes, a db that is under a quarter of a MB. It is vastly superior (with regards to interoperability, speed, flexibility, and scaling) to the poorly documented, brain-damaged Mork history format they where using, and it much more powerful and useful than flat html file that was used for bookmarks.
>they're now adding a freaking VIDEO playback feature?!
Yes. The web is a different place than it was even 5 years ago. Video is the norm, and once the video tag takes off, this will be very valuable to most users. Those that may not need or want video are probably smart enough to find a different browser that is more suitable to their needs.
>On the upside, it's nice to see Firefox is finally supporting JSON.
JSON has been supported in FF since 3.0. FF 3.1 drops JSON.jsm for native JSON. https://developer.mozilla.org/en/JSON
Climate Progress - Hell and High Water
What's the new location bar? Is it something like the old location bar, aka the UnAwesomeBar? I'm pretty much sick to death of the awesomeness of the present location bar, what with Slashdot being listed as "Server 500: Internal Error" in the dropdown because about 4 months ago I got a 500 error message?
Highlight in bar. Press delete.
"You can either have software quality or you can have pointer arithmetic, but you cannot have both at the same time."
AwesomeBar is not search. AwesomeBar is made so you can make shortcuts that don't require you to enter the URL. It gets smarter over time. Just use it some.
I can't understand why people are so pissed over it, I love it. It really did change the way I use the browser.
Good. Cheap. Fast. Pick Two.
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.
Then you'll be happy to know 1 and 2 are both fixed. I'm not sure what you mean by 3. You can delete whatever entries you want by hitting Delete. They've added the following about:config options in 3.1:
* browser.urlbar.match.title: Returns results that match the text in the title.
* browser.urlbar.match.url: Returns results that match the text in the URL.
* browser.urlbar.restrict.bookmark: Returns only results that are from the bookmarks.
* browser.urlbar.restrict.history: Returns only results that are from the browser's history.
* browser.urlbar.restrict.tag: Returns only results that have been tagged.
You can also prefix any address with @ to match it to URLs without going in in changing that option.
Whoa there, guess you didn't see the news...
The upcoming release of 3.1 is going to be named 3.5.
See https://wiki.mozilla.org/Firefox3.1/3.5
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
It's easy to have a clean codebase when...
* No fullscreen mode.
* No detection of click-through
* Cut and paste uses icon-shape style instead of dragging an image
* Can't grow selection using cursor
* Not cross platform
* History is just a list of titles (can't even get URL info)
* History looks like a webpage, but you can't do text search or select or right-click on links
* Downloads looks like a webpage, but same problems as history
* Closing a window with multiple tabs nukes them with no warning.
* No 'view page info' showing links, media, etc
* No 'page style' css choices
* Poor handling of many tabs (they shrink forever).
* Can't control what sites are in the screenshots on start page
* Can't search inside and outside a text field at once (either or)
* Can't see pages that are in the cache (work offline mode)
* Print... just silently does nothing if no printer installed
* No rss support at all
* No multiple profiles
* With lots of bookmarks, it doesn't remember where you were in the list so you have to scroll to the bottom again to click more than one
* Can't allow/prevent pages from choosing their own fonts
* No whitelist for cookies
* No clearing of cookies on closing browser
* No separate proxy settings, have to use OS ones
* No settings for enable/disable Java, Javascript.
* Can't restrict Javascript behaviors, such as moving windows
* Can't disable image loading
* Can't modify MIME type mappings
* Can't set max history time in days or entries
* Can't set cache size
* No master password
* No whitelist to avoid site warnings
* No support for security devices
* Can't control update behavior
* Poor accessibility
* No autoscroll (fixed?)
* Can't clear all transfers (have to remove one by one)
* Buggy UI, for example Text Encoding menu doesn't autoscroll up despite having arrows (have to click arrow, can autoscroll down if wiggle mouse)
* No firebug equivalent.
* No mouse gestures.
* Plugins perform badly and/or fail
* Has bad rendering on many non-perfect sites (same with all WebKit browsers)
Oh yeah, and they stole the name 'chrome' from Mozilla, which is pretty scummy. They don't even give props to Mozilla for the name.
Let me know if these are outdated... I don't have my Windows vmware image handy.
This is slashdot, the same website that looks down on people who don't want to switch from Windows to linux, become proficient with the command line or learn console editors like vim and emacs. Yet these same crybabies then go on to say that it will take them 6 months to adjust to a glorified text box.
I love slashdot because I love the irony.
Similes are like metaphors