Firefox 4 Beta 8 Up
An anonymous reader writes "Mozilla has released a new beta of Firefox 4 this morning. Originally intended as a quick update for the feature-complete Beta 7 release, the new Beta includes 1415 bugfixes, a fine-tuned add-ons manager, improved WebGL support as well as URL bar enhancements."
Will the next version of Firefox (whatever version it may be) be slower? Because quite frankly, FF has become a giant turd in that respect, so much so that, although I love it, I'm considering alternatives on my lower-end machines...
"A door is what a dog is perpetually on the wrong side of" - Ogden Nash
If I am not mistaken firefox(maybe 3.5) Went to beta 8 as well. Before releasing the final version. Nothing wrong with that. Just different philosophy how when and how to release.
Looking forward to getting this update, my beta 7 doesn't see the update available yet.
Only problem I've been having is that it crashes my graphics drivers periodically (Nvidia 189.5 I think). But performance is great and once I got my normal status bar back, I really like Firefox 4. Big fan of Sync too and looking forward to having Firefox 4 available in the Ubuntu repositories.
Reviewing just the first hour of video games.
as well as URL bar enhancements
If by "enhancements" they mean "throw the awesomebar out a window", I'm all for it.
Yes, part of that is resistance to change, but part is from my first experience involved typing a URL and seeing results getting pulled from the middle of a page's title that had nothing to do with what I wanted.
Can this thing prevent covert, un-removable install of add-ons (e.g. .NET Framework Assistant)?
Does it set layout.css.visited_links_enabled to false?
(See http://yro.slashdot.org/comments.pl?sid=1894680&cid=34430992)
Obama's legacy: (N)othing (S)ecure (A)nywhere and (T)error (S)imulation (A)dministration
How is it possible? Easy. Last month there was an entry in Bugzilla where they fixed a bug that was submitted in November 2000. That's right 10 years ago -- before Firefox even existed. It means that Firefox is still running old Mozilla code from a decade ago.
Take a page from opera's (11) book, I can be loading my default 20 tabs all at once and the interface is still responsive.
Firefox, good luck, the entire browser chugs to a grinding halt for 10 seconds, then the next 10 seconds it's hitchy but at least responsive.
This is on a quad-core machine running at 3.5ghz. Chrome maxes out all of my cores to 100% and is done rendering in about 4 seconds, AND it's rendering all the ads that are being blocked by adblock. Firefox never uses more than 30%. Bad programming. Opera doesn't use more than 30% at once either, but the user interface is incredibly responsive.
I hear multi-core support is coming, but it's not going to be here in FF4.
That and it's terribly slow. When I want to check websites, I check five. I type one press enter, then CTRL+T, and then start typing. But by tab 3, Firefox is too busy rendering to bother returning the URL results in any timely fashion. I can usually finish typing the url before it's found a result for me.
I credit this to the thugs in charge with superiority complexes who refuse to admit something is wrong and needs fixing.
Opera&Chrome are supremely smoother. One of these days I will just jump ship to Opera. I just don't want to have to learn yet another new interface.
It seems to me that if they cleared 1400+ bugs between Beta 7 and Beta 8, then there's a whole lot of significant bugs that still need to be fixed. That doesn't sound like what I'd call "Beta".
I like that firefox wants to be fast and everything but does it even matter anymore. I have at least 10-15 extensions in my browser and at least one of them keep crashing/leaking memory etc. Does this release have a better plugin container for these extensions? My overall satisfaction with FF is at an all time low because of this. I am not ready to move to chrome yet, but I am seriously thinking about it.
The download links are still pointing to beta 7.
https://www.mozilla.com/en-US/firefox/all-beta.html
The main reason I run FF is the wealth of addons.
Will 4.0 break compatibility?
i seriously need them to release ff4. enough beta-ing around already!!1
Wealth is the gift that keeps on giving.
Will it finally support languages other than JavaScript for client side programming? Just when we seem to be entering a point in time where people finally realize that they can choose the right language for the job, so much is moving to the web where there's only one language or nothing at all.
Cory Doctorow talking about cloud computing makes as much sense as George W Bush talking about electrical engineering.
Can't migrate til that is compatible.
(Yeah I heard the news.)
Where are we going and why are we in a handbasket?
i seriously need them to release ff4. enough beta-ing around already!!1
So you would rather have buggy code as long as that it is released? use IE!
Roll a d20, save VS Stupidity......
It's just as fast as Chromium now, and with many windows and tabs and after being open for days it seems less of a resource hog than Chromium. Only the startup takes longer, at least with several extensions. There's a Greasemonkey beta for it too now - the last reason that held me back from setting FF as my default browser again.
thegodmovie.com - watch it
This is not the interface, it's the SQLite database. Every time you access a page, it has to write to the database.
It doesn't _have_ to write to the database, it chooses to write to the database. I believe it's updating things like the time you last visited the page, which I totally don't care about.
If you file a bug each time you want to change the color of a bikeshed, and if you repaint the bikeshed in a slightly different color each year then you'll have 10 bugs just for one small bikeshed. The fact that the bikeshed is a slightly different color may reflect evolving trends or the intent of a designer to influence trends. It doesn't mean that the bikeshed was rotten, just that someone felt it could look prettier. And with time, a single person's idea of how to make something look pretty can change.
Note that we tend to file bugs for very small components, so if you think of a project as a building, then we might be talking about painting a single brick (it might be a cornerstone). If you're painting a mural on one side of the building, each brick might need to be painted in a different color, but the end result can look beautiful.
I'm not sure if he was defending Mozilla so much as pointing out that Firefox is not exactly running on all-new code, which takes them 10 years to fix on occasion.
"Our two-party system is like a bowl of shit looking at itself in a mirror." - Lewis Black
If you do get the beta, go and run this add-on, https://addons.mozilla.org/en-US/firefox/addon/200733/
It will help the Firefox developers learn how best to use hardware acceleration.
Firefox 4 goes up to 11!
^_^
...and not one of them is broken font rendering. Hell, it actually seems to have gotten even worse since Beta 7. I used to love FIrefox, but I'm definitely sticking with Chrome until they get that cleared up. That blurry nonsense hurts my eyes.
Are we fast yet.com shows the measurements used by the Mozilla Javascript development team, comparing performance of ff4 to chrome/v8 and safari/nitro using both the sunspider (Mozilla) and v8bench (Google) test suites. LOTS of movement in Firefox over the past few months, including the apparent surpassing of Safari's Nitro engine in both tests and even beating Chrome's V8 in the Mozilla test suite.
This boost is likely due in part to the recently added hardware acceleration. This is listed as supported on all major operating systems (see the Firefox 4 Beta Technology page).
Use my userscript to add story images to Slashdot. There's no going back.
Exactly. When some of your code is 10+ years old, it's not surprising that you can find lots of bugs.
I seriously hope Firefox doesn't change how the awesome bar works. That's one of the many things I prefer in Firefox to Chrome and all other browsers.
Wow buddy you're childhood is really coming through today.
After you get it, try out - http://bodybrowser.googlelabs.com/ I think it's neat anyhow and and I had never used a WebGL app prior. Awesome stuff.
I wonder what part of Firefox's functionality will be arbitrarily changed this time? I always delay upgrading until they cut off security updates for the old version, and every time I finally upgrade there is some part of the application that works differently, and I need to google some arcane config setting to put it back the way I like it.
why do you cower? what are you afraid of?
you're completely pathetic.
I think I'll wait intil it's less buggy. This one has 1415 bug fixes, how many more bugs are there?
Free Martian Whores!
Will you stop posting? You don't contribute anything to this discussion.
show me a system/big apps without bugs... the main problem is that in closed apps you dont even see the bugs and most people dont even report then, so they stay hidden for years (are you listen MS!!)
the fact that you can count bugs doesnt mean they are all the in the same level of importance, many of then might even be enhancement bugs
but hey, if you dont like FF, use other browsers, as long they respect the standards, its fine!
Higuita
A neat demo, to be sure, but it's not compiling. It's just interpreting Python into JavaScript which is itself interpreted. I would much rather see the ability to write in the language of my choice and have that compiled into bytecode which I would then serve to clients. That bytecode would be what is executed. Then we can use whatever language is best for the job.
Cory Doctorow talking about cloud computing makes as much sense as George W Bush talking about electrical engineering.
The download link on the original page is old. It reads http://download.mozilla.org/?product=firefox-4.0b7&os=win&lang=en-US, so just change the "7" to an "8" and voi-la! A download link like so http://download.mozilla.org/?product=firefox-4.0b8&os=win&lang=en-US . Those from other locales may choose a diff lang or OS.
Figure out what the plugin is and stop using it. Fixed.
This is why a lot of app developers hate plugins, etc. because their product gets blamed for some cute "dancing reindeer" add-on that leaks memory and now their product "totally sucks!"
If you think Chrome will solve your problem, you will be sad. The sandboxing is to prevent a plug crash from taking down the whole browser, but it's perfectly fine for it to consume memory. And Chrome, particularly the latest dev build, is a resource monster already. As more plugins accumulate for Chrome, all of these complaints will migrate to Chrome...circle of life, I suppose.
Then stop using HTML/CSS/JavaScript for applications and use Java Web Start. Write in Java, Ruby (JRuby), Python (JPython), Scala, or JavaScript (Rhino).
Go green: turn off your refrigerator.
But then it wouldn't be web pages.
Cory Doctorow talking about cloud computing makes as much sense as George W Bush talking about electrical engineering.
So true. Can't Mozialla just port the JavaVM into the browser? That way we could use JavaScript, Ruby, Python, Groovy, Scala, Lisp, and Java as a web language. Mozilla just need to add some web stuff into the JavaVM like DOM so the JavaVM can manipulate the HTML.
http://www.mueller-public.de - My site http://www.anr-institute.com/ - Advanced Natural Research Institute
That's odd. I downloaded beta 8 within minutes after this story was posted.
we_fast
I've found that having a fast Java(script) engine doesn't matter when your laptop has a 600 megahertz CPU, or slower ~2001 era hard drive. It sits there and momentarily-freezes while the page loads. The code is fast but too CPU intensive. (shrug). Puppy Lucid 10.04 Linux has a few nice browsers for limited, older computers like FirePuppy (very simple) and Non-google Chromium (small memory footprint).
SeaMonkey Navigator beta 2 is scheduled to release this week too (although it might get postponed 'til after the christmas break).
FOX NEWS.com should be BANNED from television and internet. Have the Congress take it over and give us Truespeak.
So?
Go green: turn off your refrigerator.
So lots of web applications and interactivity are moving to HTML 5 and JavaScript and companies like Apple and Google are pushing hard to move things in that direction. Some devices, like the Google ChromeOS laptop, are just a browser with no capability for Flash and Java. We're going to see more of that.
Believe me, I agree with you that Java would be a better solution, but it's not really an option now and probably won't be one at all in the near future.
Cory Doctorow talking about cloud computing makes as much sense as George W Bush talking about electrical engineering.
A neat demo, to be sure, but it's not compiling. It's just interpreting Python into JavaScript which is itself interpreted.
If it’s done all at once, it’s compiled. What’s more, the Javascript itself is probably being executed by something between an interpreter and a compiler. The boundaries are so indistinct anymore in this particular region that your making a point of it is not only wrong but more or less meaningless even if it was correct.
Distributed Denial of APK: It takes 15 seconds to reply to him anonymously, but wastes tons of his time if we all do it.
> Will it finally support languages other than JavaScript for client side programming?
No.
In fact, we're _removing_ such support. We supported using python for chrome (Firefox browser ui, not google's browser) programming for years, and no one used it. It's just a performance drag on the javascript and C++ side of things, so it's being removed.
The fact is, supporting multiple languages in a single runtime without leaking and without nasty performance hits on both is not really all that feasible. Given that, and the near-zero amount of actual use such functionality would get, based on our experience with chrome, it's not worth building it in....
In the case of Mozilla, all issues in the issue tracker are called "bugs". That includes feature requests, requests to give someone access to the version control system, tickets that track bumping the version number from "4.0b7" to "4.0b8", etc, etc.
So you end up with a pretty inflated bug count if you just count the "bugs".
IIRC it’s also possible to write the bulk of an extension in C++ and then hook it into the browser chrome with Javascript, or something along those lines.
But this discussion isn’t really about extensions, it’s about web-based applications...
Distributed Denial of APK: It takes 15 seconds to reply to him anonymously, but wastes tons of his time if we all do it.
> 1415 bugs in a mature release of a spec based media rendering engine?
That "spec based" thing...
One simple issue is that the specs are not stable in many cases (even in cases when they exist; in many cases they don't exist). There were dozens of bugs in one small component (form controls) that had to be fixed because the spec has changed yet again. Similar things for the indexeddb spec, parsing, etc, etc.
I mean.... have you tried implementing these specs? Or even finding a stable version of them?
If you file a bug each time you want to change the color of a bikeshed...
"That's not a bug, it's a feature." -- Bill Gates, 1981
no one can defend a corporation requiring 10 years to fix logical failures in their flagship product utilized by millions to process credit transactions.
Hate to break it to you, but browsers do not proces credit card transactions. Sure, people use them as a tool to submit their credit card information, but it's just (one of) the messenger(s).
Wow...client side credit card processing...scary thought!
> IIRC it's also possible to write the bulk of an extension in C++ and then hook it into the > browser chrome with Javascript, or something along those lines.
That's not quite the same thing. In that case the C++ would be running into its own world. What Firefox used to support is just putting:
in your XUL, which would run just like JS runs in chrome, with complete access to the DOM, etc. Again, no one used it.
> But this discussion isn't really about extensions, it's about web-based applications...
Right; there's just not much evidence that if any one browser (but not others) were to support this then anyone would use it. In fact, there's evidence to the contrary: even in the limited context of extensions, where compat with other browsers is not a concern, no one used it.
So why would a browser do this? It's a competitive disadvantage (since it slows down C++ and JS DOM manipulation, increases memory usage, etc) to be the first mover on this, it's a lot of work to do even a half-assed job and a _lot_ of work to do it "right", and there is no payoff for doing it...
Er... I keep forgetting that Slashdot's "plain old text" isn't. What you could put in was:
<script type="application/python" src="my-python.py"></script>
I strongly disagree. It is Mozilla's fault. Since the earliest days of the original Mozilla browser they have completely ignored backwards compatibility. Every new version breaks most extensions. Just going from FF4 beta 7 to beta 8 required me to update 2 extensions. Some of the major extensions (like Adblock) get updated quickly. Others get updated more slowly and many are abandoned and never updated at all, in which case, you're screwed. Sometimes you can hack the version number on an extension and get it to work, but not always.
But here's the point. Except for the occasional program that does low level stuff (typically anti-virus and disk defrag programs) I have very rarely had any problems with software not working when I move from one version of Windows to another. I have old software dating back to the days of Windows 95 and it runs just fine on Windows 7 x64 because Windows has a stable API for writing software and as long as you follow the rules your program will usually run on any version of Windows. And there's no reason why the Mozilla developers can't do the same thing. There's no reason why they can't create a stable API or framework for extensions so that any extension that follows the API will work across different versions of Firefox. For some reason they just have no interest in doing this.
I know. And you could also compile Python to a .dll and probably hook that in. And it is a whole different ball game, I realise. I was just pointing out that you can already use different languages client-side, if you’re talking about extensions. There are just a few other hoops you have to jump through to do it.
Distributed Denial of APK: It takes 15 seconds to reply to him anonymously, but wastes tons of his time if we all do it.
a bug is a bug. it is not a feature request. it is only an enhancement as so much as it is a removal of a logical FAILURE.
why would i ever use a browser 10 years into a production cycle that continues to have thousands of bugs identified? why would anyone?
but hey, if your mother named you "higuita" why wouldn't you tell people that is your name, "its" fine!
you're an idiot.
I've been running the nightly release version for a few months now without issues*. Very fast, great new features.
http://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/latest-trunk/
* I don't run many add-ons so your mileage may vary.
i understand open source software development completely... unskilled developers provide more bugs than features, and then frequent this internet web site chat room message board to whine about it while begging for praise and adoption.
keep committing those bugs... you're doing a noble service. ;)
there aren't 1415 form controls... there aren't even 1415 attributes.
the firefox codebase is quite obviously littered with logical failures.
> i most certainly have implemented them,
You've written an HTML parser? A JavaScript interpreter? A JPEG decoder?
Do you and I just disagree on the meaning of the word "implement" here?
> there aren't 1415 form controls... there aren't even 1415 attributes.
Did you miss the part where I said that form controls are a _small_ module that contributed a few dozen make-work bugs to the total?
> the firefox codebase is quite obviously littered with logical failures.
Yep. It sure is. As is every single large codebase of any sort I've looked at.
so "dozens" turns to "few" under scrutiny... i'm sure there was at least 1 bug attributable to form control spec changes.
you've obviously never seen any codebase that i maintain. there is a reason mozilla provides their products free of charge... what could that reason be? could delivering a broken product ever serve to benefit such a company?
yep. it sure could.
did your mother name you "BZ"? why do you cower behind a chosen pseudonym? what are you afraid of?
you're completely pathetic.
i architected custom languages with their own interpreters that power web server platforms which serve as their own operating system to power large scale content distribution networks.
i assure you, i know all of the reasons why everything mozilla is doing is broken and wrong.
bragging about 1400+ bugs existing is barely scratching the surface.
> it's really REALLY hard to utilize any of regular expression stream tokenizers
Uh... you can't tokenize HTML (correctly at least) with regular expressions. If you're trying to, you just lose. If you're doing it for security reasons, you _really_ lose.
> so "dozens" turns to "few" under scrutiny..
Uh... "dozens" and "a few dozen" are in fact pretty much the same last I checked. "few" and "a few dozen" are not. Please do read what I wrote instead of just trolling?
> i'm sure there was at least 1 bug attributable to form control spec changes.
Absolutely. ;)
> you've obviously never seen any codebase that i maintain
Clearly.
> did your mother name you "BZ"?
Nope, but it provides a convenient handle for Slashdot and irc and whatnot, being short. It's not like I make a big secret over who I am, exactly. Here; I'll even help you out:
http://letmegooglethatforyou.com/?q=bz+mozilla
A neat demo, to be sure, but it's not compiling. It's just interpreting Python into JavaScript which is itself interpreted.
Just to clarify, CPython is compiled (not interpreted) from C into JavaScript. (Then Python is interpreted inside that, just as CPython interprets code normally.)
The first step is compilation, since C is actually translated into JavaScript. There isn't a runtime that interprets it. Unless you mean the JavaScript engine itself, which interprets the JavaScript into which it's compiled - but that engine too, in modern browsers, will compile JavaScript into machine code, and not interpret it.
Anyhow, maybe that's what you meant and were just being brief, sorry if so. I just wanted to clarify that for other people reading.
you're an idiot.
slashdot = stagnated.
if you really are in any way associated with the mozilla development process, it's even more clear to me why they are accumulating so much broken code full of logical failures in their flagship products.
you're an idiot.
Dude, give it up. I don't know what's up with that MichaelKristopeit30x guy, but you notice that he posts from at least 5 accounts, yes? Check out these accounts' posting histories.
"When I first heard Daydream Nation it quite frankly scared the living shit out of me." -- Matthew Stearns
I did not in fact notice that, no. And I gave up, indeed. ;) Thanks for the good advice!
So, when are they going to fix the usability issue with the changing tab width? For some time people have been complaining about the inability to put the close button on the left side of the tab. They of course refuse to do this, but they still haven't gotten that the issue is really that people just want the close button of the next tab to line up under the mouse every time you close a tab. For those who don't what i'm talking about. Download Chrome, open up enough tabs so that the tabs have to shrink to fit the window. Now close a few. You will notice that in Chrome the tabs don't resize until you move the mouse away from the button. FF4 unfortunately resizes immediately on closing, making it a pain to close more than one or two tabs at a time.
Non sequitur: Your facts are uncoordinated.
But are they FINALLY gonna support protected mode in Windows Vista and 7? The tech has been out there since 07 for the love of Pete, and it kinda kills the entire point of having all the extra security of Windows Vista and Win 7 if FF is gonna punch a giant hole right through the security and do a little monkey dance.
So while I hope that Mozilla supports protected mode so I can keep recommending it, until then for myself and my customers I've been testing the Comodo Dragon browser which like all Chromium browsers DOES support protected mode, and adds some extra security features and turns off the Google phoning home like in Chrome. It is taking a little to get used to but so far I have found most of my extensions, and the secure DNS and other security features are nice and it is still fast as hell.
I would really hate to give up on FF, but with the browser being the #1 source of malware getting into a system not supporting protected mode is just too risky. I mean what is the point of all the extra security features if Mozilla doesn't use them? It isn't like FF runs as root in Linux, so why should it run at a higher user level in Windows when it doesn't have to?
ACs don't waste your time replying, your posts are never seen by me.
okay, but they should have a schedule. right now, they're just coding and coding without even having a tentative release date. 2011 is not a release date.
also, since they've delayed ff4 for perhaps a year now, they should hurry and fix the remaining bugs in later patches.
Wealth is the gift that keeps on giving.
Especially when it's restarting, I've wondered why it has to try to load huge numbers of tabs all at once. Why not load 3-4 tabs, then the next 3-4, etc?
You often have a large number of tabs at startup because you click on Restart after installing an extension, and you had tabs open.
Btw, what happens to the disk cache re: those tabs? When FF is running, it caches pages so they won't have to be downloaded again. So why does it download again when you restart? Why not read it off the disk?
I'm not a lawyer, but I play one on the Internet. Blog
i bet all of those 1415 bugs are just minor issues that won't hurt anyone. the benefit to coming out of beta is that extensions will start supporting ff4, which many of them do not right now.
also, they've been delaying release for a long time. the new features ff4 has over the current stable version are:
1. ui-which i can already get through a theme.
2. JägerMonkey engine- which has already been beaten by the current stable version of chrome, and which is closely followed by the current beta of ie9.
3. Direct2D acceleration- ie9 beta's been doing that since forever.
now i understand that ff4 beta also has these features, but that leads us to the conclusion that ff4 development has slowed down enough to match the glacial pace of microsoft.
Wealth is the gift that keeps on giving.
http://krakenbenchmark.mozilla.org
As is often the case benchmarks don't tell the whole story.
If you run Kracken and compare the results with Google (I'm using FF4 b9pre Minefield)
Now look specifically at the score for digital darkroom (image manipulation)
darkroom: 6.07x as fast Chrome - 1705.3ms +/- 1.6% Firefox - 281.1ms +/- 0.7% significant
Now click on the hyper link and check the actual test and try image rotation. Behold Chrome fails to remove the original image and rotates the new image over the top of the original. So not only is FF 6X faster it also works.
Honestly relying on something like Comodo secure DNS is not a great solution for your clients..what happens when that company goes or starts charging for the service?
If you ignore ACs because they are anonymous - you're an idiot.
actually, it's "just" (one of) the EXPLOITABLE messenger(s).
You're not an OpenBSD user by any chance, are you? Because even they've been on the /. front page recently about a few bugs that they had to fix. Any project with more than a few lines of code is bound to have problems, exponentially more as the LOC increase.
Unity? Screw that: XFCE. Slashdot Beta? Screw that: SoylentNews. Australis? Screw that: Pale Moon. UX developers DIAF
Just call each other's mothers fags and the flames will end.
This post contains benzene, nitrosamines, formaldehyde and hydrogen cyanide.
20 years experience? You started "web development" in 1990? What kind of webs did you develop back then?
While the python on that page is interpreted. The python interpreter itself is compiled from C to javascript using emscripten.
You can compile any other languages supported by LLVM to javascript. Alternatively, if you want to compile Java to javascript, use GWT which has been doing that for years. These aren't the only examples, it is becoming a popular strategy.
This is close to what you want, except that machine generated javascript has replaced your bytecode. Having a defined virtual machine and bytecode on the web was tried with the JVM, but didn't work out so well. Persuading the world to try again won't work; improving the browsers javascript implementations (and extending the JS spec) is more feasible and reaches much the same goal.
Listen to Brendan Eich on byte code in the browser in his podcast.
I downloaded and installed the "pre-release" version a week ago. Immediately experienced a BSOD (something related to an NVidia graphics driver). Rebooted, uninstalled.
Fired up the never-uninstalled Firefox v3.x still on my system. And guess what? All my bookmarks, favorites, GONE. My history: GONE. My add-ons: GONE!
Damned uninstall nuked my entire Firefox installation (except for the actual folder and executables themselves).
DAMNED good thing I had duplicates on my home system (thanks to the Sync addon). Lesson learned (again): don't even think of trying a Mozilla / Firefox BETA.
Actually (I have been running minefield since beta4): /. is an app tab me seeing the stories from weeks ago every time the browser is restarted)
* several of them at least were actual full browser crashes
* others were partial crashes (eg youtube stopped working for a few days in there because the flash plugin kept crashing)
* odd bugs like the addon bar disappearing (and without it there was no way to get to some extensions)
* bad UX in the panorama functionality (you could close panorama and lose all of the tabs you had open)
* app tabs were (and might still be, I haven't verified it yet) loading the page that they saw out of cache instead of online (resulting in when
On your "points":
@1: while this is true, the new ui is more consistent from a themer's perspective and so this is easier to do
@2: Bull. The JM engine (JM+TM actually) is only currently beaten by the last few revisions of the v8 engine trunk repository, and only in the v8-bench tests (which feature very repeated tests that are benefited most by the v8 optimization set, which progressively further optimizes as lines of code are repeated): http://www.arewefastyet.com/awfy2.php; the IE9 beta engine doesn't actually appear to be any faster than the IE8 engine, but it does have some new dead code matching algorithms so that it seems faster on the benchmarks (that is to say it looks much faster on sunspider because a lot of that code never even gets run due to it being recognized as dead code, but on a site with heavy js usage the changes are insignificant).
@3: Perhaps I don't understand what is so great here. Could someone enlighten me as to why we should care (as users and as web developers) about what particular windows specific hardware acceleration tech is being used?
Actual new features that matter IMO in ff4: ...)
1. JM engine
2. css border radius (proper support in all browsers will affect page sizes on a significant part of the internet)
3. css background image options (background-clip, background-origin, background-size)
4. css calc() function
5. html5 form elements
6. session history management (history.pushState,
7. indexedDb
8. shipping sync with ff4
9. multitouch api
10. HSTS
11. JS typed arrays
12. considerable refactoring and deprecated code removal from Gecko (which will allow future development to happen faster)
While this beta is indeed far better than the last one, there still are some problems that need to be ironed out before it is ready for everyone. It still has some teething issues in the UI that take some getting used to (the status bar is gone, hyperlinks show the new url in the awesomebar, the context menu items for open in new tab and open in new window have swapped, etc.). I believe some of these are still changing. There are still 180+ bugs targeting ff4 and the underlying gecko 2.0 infrastructure (note ff4 is using a major upgrade of the underlying engine which it hasn't done a major upgrade since before ff1):
https://bugzilla.mozilla.org/buglist.cgi?query_format=advanced&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&target_milestone=Firefox%204.0b9&target_milestone=Firefox%204.0&target_milestone=mozilla2.0b9&target_milestone=mozilla2.0&product=Core&product=Firefox
I was under the impression that the 1415 bugs were new bugs in the new version?
Free Martian Whores!
considering every line of code doesn't interact with every other line, it's quite obvious your claims of exponentiality are completely ridiculous.
you're an idiot.
did your mother name you "TangoMargarine"? why do you cower behind a chosen pseudonym? what are you afraid of?
you're completely pathetic.
i bring only THE TRUTH.
mainly quickbasic and pascal on platforms i designed myself.
Actually (I have been running minefield since beta4): /. is an app tab me seeing the stories from weeks ago every time the browser is restarted)
* several of them at least were actual full browser crashes
* others were partial crashes (eg youtube stopped working for a few days in there because the flash plugin kept crashing)
* odd bugs like the addon bar disappearing (and without it there was no way to get to some extensions)
* bad UX in the panorama functionality (you could close panorama and lose all of the tabs you had open)
* app tabs were (and might still be, I haven't verified it yet) loading the page that they saw out of cache instead of online (resulting in when
agreed. these are serious bugs. although it is surprising that so many crash bugs have been fixed only in the 8th beta, but okay.
@2: Bull. The JM engine (JM+TM actually) is only currently beaten by the last few revisions of the v8 engine trunk repository, and only in the v8-bench tests (which feature very repeated tests that are benefited most by the v8 optimization set, which progressively further optimizes as lines of code are repeated): http://www.arewefastyet.com/awfy2.php [arewefastyet.com]; the IE9 beta engine doesn't actually appear to be any faster than the IE8 engine, but it does have some new dead code matching algorithms so that it seems faster on the benchmarks (that is to say it looks much faster on sunspider because a lot of that code never even gets run due to it being recognized as dead code, but on a site with heavy js usage the changes are insignificant).
you are saying that sunspider test results are bull. that's a new one, because i thought everyone considered that to be a real test of js performance. the whole reason why chrome is considered to be fast is that it scores way ahead on sunspider and sunspider-like tests. i find firefox 3.6 to have the same load times as chrome on almost every page. and then there are some pages (like slashdot discussions with >1000 comments) that load and scroll much faster on firefox 3.6 than chrome. so, if you disregard sunspider scores then you can't compare js performance objectively at all.
@3: Perhaps I don't understand what is so great here. Could someone enlighten me as to why we should care (as users and as web developers) about what particular windows specific hardware acceleration tech is being used?
its important because windows users are the people firefox owes its success to. the only way for firefox to continue its success is to keep its userbase happy, to provide them with a browser that better utilizes their hardware. in fact i think that mozilla knows this. that is why they've let firefox on linux stagnate. imo on linux, chromium is clearly miles ahead of firefox. on windows, firefox continues to be the browser of choice for me.
Actual new features that matter IMO in ff4: .
.
.
.
multitouch api
.
.
multi-touch apis exist only on windows 7. so firefox supports multi-touch only on windows 7. when you acted all arrogant about direct2d support saying you don't care about windows specific improvements, how could you point out to me a feature that is even more hardware and software specific? that stinks of double standards and just a compulsive need to defend firefox without thinking about the matter.
i use firefox as my main and only browser, even on linux where i find it bloated and slow compared to other options. but i have the ability to identify major shortcomings in the development of ff4, without fanboyism clouding my judgment.
Wealth is the gift that keeps on giving.
okay, but they should have a schedule.
They have a schedule! And they had a setback which delayed everything.
since they've delayed ff4 for perhaps a year now
Considering the alphas came out in June, and the 1st beta in July it is hardly a year!
How about you stop making shit up!
Roll a D20, save vs. Stupidity,...again! (you failed the last one)
Explain please. If I have an app with A-d permissions, and a second app with only A, how is giving the attacker a MUCH larger attack vector not punching a hole in your security? I mean if FireFox would have insisted on Root in Linux, would anyone have used it? No, because it would have been stupid and an unnecessary risk. So please explain, how is presenting a larger area of attack to the world with the one piece of software most likely to be exposed to malware not equally dumb? You would have a point if ALL browsers offered an equal sized target, but they don't. Chrome, IE, Dragon, SWIron, Chromium, Safari, ALL of these allow for protected mode browsing. And I'm sure that if asked MSFT would be more than happy to help FF to implement this, just as they added X.264 support, so they can't even claim lack of funds.
As for Comodo? It isn't like this is some new startup here. We are talking about a company with offices in over a half dozen countries and something like 15,000 employees at last count. And why would they charge for it? They are making money hand over fist with their enterprise offerings and the good will they generate with products like Comodo DNS, Comodo Dragon Browser, and Comodo Internet Security being free for home and small business helps to get their name out. And it helps to generate them revenue, as I've personally watched as customers that enjoyed the ease of use and security of the Comodo products at home turned around and sold their bosses on the enterprise solutions. BTW not an employee, just someone who has had nothing but good experiences from their products.
But even if they were to magically go tits up tomorrow it isn't like it would take more than 2 minutes to switch DNS providers. And until then just like protected mode it simply makes good sense. After all, why increase risk and make yourself a larger target to attack if you don't have to? Simply saying "it isn't more dangerous" without any reasoning to back that up is simply opinion. I have given you MY reasons, because protected mode lowers the permissions and helps to isolate the browser from the rest of the system, thus lowering risk. So how is increasing risk "better" in this case?
ACs don't waste your time replying, your posts are never seen by me.
If you haven't gotten the memo here yet, MichaelKristopeit### is trolling many different parts of this page (roughly 10% of the comments here are his).
He has proceeded through several sets of insults via multiple different posts from multiple users. He is getting by the moderation system a little bit by the aspect that he is a new user and thus has neutral karma. I think he gets a new user id (increasing the number) whenever his karma becomes negative so that his trolls continue to show up. I am pretty sure that there is a way to apply a negative bonus to new users so that you could avoid seeing him and those like him, but that would cause you to stop seeing other users who are saying something useful but do not post often.
This person is exploiting a weakness in the current moderation system. I don't know how it could be improved to get rid of him without adversely affecting other users. One way to do it would be to make all new users wait a period of time before they are allowed to post. That would raise the level of commitment that this person would need to continue his trolling but might not stop it. It also may have too much of an impact on other users that the /. devs may not want to implement it.
You may be interested in https://jetpack.mozillalabs.com/ which is precisely such a stable API.
Of course, being stable makes it more limited. It can't totally rejigger your browser window, say; if it could it would break when the design of that window changed, right?
Now will extension authors write to the stable API or continue to do the Windows equivalent of writing custom drivers as part of their app? Who knows.
Install the "OldBar" Extension to change the "look" back to the old way:
https://addons.mozilla.org/en-US/firefox/addon/6227
Make the following about:config changes to get the "feel" closer to the old way:
browser.urlbar.matchOnlyTyped = True
browser.urlbar.matchBehavior = 2
dragonhawk@iname.microsoft.com
I do not like Microsoft. Remove them from my email address.
agreed. these are serious bugs. although it is surprising that so many crash bugs have been fixed only in the 8th beta, but okay.
Beta 7 is basically where JM landed for the beta. I have a feeling that this was a significant part of the actual bugfixes that have happened.
you are saying that sunspider test results are bull. that's a new one, because i thought everyone considered that to be a real test of js performance.
no I am saying find me a reference that says the stable version of chrome is beating beta8 or a comparable nightly release in terms of performance. The DEV build is certainly faster, but the stable build (8.0.552.224)?
the whole reason why chrome is considered to be fast is that it scores way ahead on sunspider and sunspider-like tests. i find firefox 3.6 to have the same load times as chrome on almost every page. and then there are some pages (like slashdot discussions with >1000 comments) that load and scroll much faster on firefox 3.6 than chrome. so, if you disregard sunspider scores then you can't compare js performance objectively at all.
Again I am not disregarding sunspider scores. In fact I linked you to the mozilla site which is testing 10 tip builds a day for 3 compile options of Firefox and a built from source version of the chrome engine using the latest source for that. Very clearly in the sunspider chart there, the version of Firefox's javascript engine which will be in the official release is beating the absolute newest publicly available version of the v8 engine used in chrome by 9.4 milliseconds. On the kraken benchmark (sunspider was built by apple, kraken was built by mozilla, v8-bench was built by google), ff4 is over 9 seconds faster. The v8-bench test is favoring google but it is the only one I have seen.