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."
They changed the location bar again.
Now I can watch people flip out about it on the interwebs for 6 months as well as being personally annoyed with re-getting used to how it functions.
You can't take the sky from me.
I was going to download this using Mozilla Firefox, but Microsoft told me it would be faster downloading, and it's returning a exception. Too bad I wanted to use it.
It's all fun and games till someone divides by 0. Then it's hilarious.
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.
...It looks the same on the surface, but there are many changes under the hood."...
Will Joe Public be in position to notice them? The new engine might be indeed faster but I wonder whether an ordinary user will see a difference.
Uh, yeah, you do if you're running 3.1b2. They have a beta update channel.
I thought Firefox was going to be implementing the same type of preemptive threading and memory protection that Chrome and, I think, IE 8 have?
So far the latest FF beta all seem horribly slow with multiple pages. The more tabs the worse the overall performance.
Also, the latest FF betas still have the awful performance rot where overall performance degrades over time as you continue to open and close tabs.
After using Chrome for a while it is hard to keep using FF when I've been able to keep Chrome open for a couple weeks and it still feels as lightning quick as it was when first started up.
I know there is a tendency among some people to think of version numbers as decimal, since they use decimal points. I know I did when I was younger.
It's kind of annoying when major projects make this mistake though. It leads to all sorts of confusion when people see results like version 3.1.150 being after 3.1.50 and don't know why that's the case (".5 is more than .15!", which in the case of the Firefox release mentioned in TFS would be accurate, but in the case of properly-numbered software wouldn't), or other people truncate 3.1.50 to 3.1.5.
I wish major projects at least would use the traditional "increment by one" method. If it can be done for the X-Men 2.1 DVD (after nerds no doubt complained about the "X-Men 1.5" DVD), it can be done for Firefox et al too :).
"...always new atoms but always doing the same dance, remembering what the dance was yesterday." -Richard Feynman
is back!
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.
I'm looking forward to them resolving the bit where the *nix Firefox builds performed slower than the win32 builds, supposedly due to Profile Guided Optimizations in javascript:
http://www.tuxradar.com/content/benchmarked-firefox-javascript-linux-and-windows-and-its-not-pretty
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?
F*** yes.
And having "sl" pull up "slashdot.org", followed by half a dozen unrelated sites that happen to have "sl" in their name, followed by the site that I was looking for that actually starts with "sl" but is "below the fold" because it's not awesome enough... really ticks me off. If I want to "search", I'll enter the name in the "search box". If I want to go to a website, I'll enter the site name in the location bar. I don't mind you searching titles as well, but list them below the URLs, OK?
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
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.
Firefox 3.X being awful on a Mac is an understatement ... when running OSX 10.3.9
The world is made by those who show up for the job.
>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."
(And yeah, chalk up another brickbat for the Awfulbar. Spent the better part of the first day disabling it to restore most of the old bar's functionality. I remember URLs, not "title" elements. Please, for the love of Dobbs, if you're not going to back out this monstrosity, at least give users the option to ignore the title element while "searching" the URL history. The web is not AOL, and some of us do not navigate by keywords.
You're probably in the minority on this one. Firefox is targeting normal people, not nerds, and normal folks don't remember URLs particularly well.
"You can either have software quality or you can have pointer arithmetic, but you cannot have both at the same time."
Weirdly enough, that didn't work for me, on any of the installs I had.
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.
Yes, you do. But the auto-update is not activated until later on, usually a couple of days after having the new version available through direct download.
uh...looking at the Google Chrome team page, I can immediately pick out the following people as being ex-Mozilla employees or contributors: Ben Goodger, Darin Fisher, Brett Wilson, Peter Kasting, Mike Pinkerton, Jonathan Haas, Pam Greene, Jungshik Shin I'm sure there are more that I'm not aware of, but those are all certain.
Try Shift-Delete on OS X.
(OS X.5.6, Firefox 3.0.7)
My interest in the new Firefox betas is its official support of cross-site HTTP requests (documented at https://developer.mozilla.org/En/HTTP_access_control). It's following the new W3C spec (http://dev.w3.org/2006/waf/access-control/) for allowing the XmlHttpRequest to communicate with an external domain without the use of the filthy "script get" hacks. I've just spent some time implementing a proof-of-concept for this stuff, and am impressed with how well it works. It even allows POST requests so you're not limited by the usual GET length limits.
It does require server-side modifications, but they're mostly simple.
I see this as the best new feature of Firefox and plan on adding support for this method of XHR into my applications, with failover to the old "script get" stuff. I only hope that other browsers also embrace this new functionality in the near future.
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.
Plugin support?
* No multiple profiles
--user-data-dir='path/to/profile'
You can even simultaneously run two instances using different profiles. My partner and I use this on our shared desktop so we can stay logged in to all those sites we don't care if the other person sees.
http://www.chromeplugins.org/tips-tricks/how-to-create-profiles-in-google-chrome/
What is a nonconsole text editor, and what makes it so?
Not a terminal window. vim is a console editor. Gvim is not, as it won't run in a telnet session. (never mind that virtually no one uses straight telnet anymore... but saying ssh opens too many possibilities...)