What is Digg?Sponsored by Dragon Age: Origins
Can't get enough Dragon Age: Origins? Check out new footage. view!
DragonAge.BioWare.com - EA presents BioWare's new dark fantasy epic Dragon Age: Origins. '9/10' from Game Informer.
161 Comments
- liltbrockie, on 06/20/2009, -5/+244i heard from microsoft.com that IE8 is a superior browser
- benvds, on 06/20/2009, -8/+166This is almost news.
- damack, on 06/20/2009, -2/+80THE browser is nearly here.
Been using the beta and its been great. Release 3.5 already please :D - w3ber, on 06/20/2009, -8/+81109 tabs? why?
- 4321234, on 06/19/2009, -2/+70Release the hounds!
- acegi, on 06/20/2009, -2/+524chan porn threads...
- SmSpillaz, on 06/20/2009, -4/+52I hope tab sandboxing is on the agenda for 4.0 - I'm a pretty frequent tabber and when one tab causes 108 others to close I'm generally not happy :-/. Other browsers like Chrome cause tabs to clutter up and don't scroll.
- txentxubros, on 06/20/2009, -3/+40I love their comparison chart... too! xD
Here the evidence:
http://www.microsoft.com/windows/internet-explorer ... - orchidfire86, on 06/20/2009, -0/+34They truly live on another planet...
- LilRabbitFooFoo, on 06/20/2009, -3/+30***** you, apologist. The program should be written to sandbox the tasks and tabs and you know it.
- justdru, on 06/20/2009, -1/+27...and it comes with a shiny new logo, too!
- Giac, on 06/20/2009, -0/+23Using the prerelease and its geat. It sounds stupid but the new logo looks really nice on the windows 7 taskbar.
- srg13, on 06/20/2009, -0/+17They changed 3.1 to 3.5 because they decided it was a more significant improvement than a .1 release.
- jsebrech, on 06/20/2009, -1/+17If you're seeing frequent crashes, it's probably a plugin. For me (g4 mac), it's the flash plugin, which crashes like a drunk driver on friday night.
- kyle212, on 06/20/2009, -0/+15Mozilla link, Cnet didn't work for me.
http://www.mozilla.com/en-US/firefox/all-rc.html - jsebrech, on 06/20/2009, -1/+16Shiny.
I'm looking forward to all the new web developer goodies:
https://developer.mozilla.org/en/Firefox_3.5_for_d ...
Admittedly, IE is still a bottleneck there, but there's a bunch of stuff that we can start using immediately:
- downloadable fonts (no more generating an image any time tahoma or verdana aren't good enough)
- native json support (faster web apps without changing a line of code)
- dom workers: real javascript multi-threading, with the google gears plugin as a fallback support option on IE.
- progress events for xmlhttprequest, so complex server-side operations can provide progress bars (with just a busy indicator as fallback on IE)
Basically, what we're starting to see here is that stuff that was doable but highly convoluted or slow is becoming easier and faster. - tofagerl, on 06/20/2009, -2/+16Yeah. Use a custom skin and get the ***** over yourself.
- Kaiern, on 06/20/2009, -1/+14My guess is that 80% of the Microsoft staff secretly use Firefox.
- techdever, on 06/20/2009, -1/+13you are doing it wrong
- ridd1e, on 06/20/2009, -1/+12You gotta love CNET
http://img.skitch.com/20090620-r5j2h5uyu8yhu9eqtmj ... - TDDebug, on 06/20/2009, -1/+12You didn't even spell "miss-spells" right... and it's not even a word I don't think.
misspellings* - R0B0Ninja, on 06/20/2009, -0/+10It's a lot faster
- rhabdomancer, on 06/20/2009, -2/+12bing is awesome for porn!
- diggforworld, on 06/20/2009, -3/+13FIREFOX FTW!
- Mejogid, on 06/20/2009, -0/+9I've used the new release on OS X, Linux and Windows, and I've been stunned particularly by the improvements on the non-Windows OS's. On OS X, with Arronax's Tangy theme (http://www.takebacktheweb.org/ ) and a handful of addons I have a browser that feels just as native and a bit prettier than Safari (the new icon looks great in the dock too) and performs well enough that I really can't notice a difference from Safari or the Chrome alphas on my first generation Macbook. Similarly, firefox on Linux has somehow become noticably faster than the latest epiphany webkit builds (despite its allegedly slower rendering engine) and a lot of the annoying glitches with its GTK emulation have disappeared. The support for emerging standards is also very welcome.
Oh, and Weave, Ubiquity, CyberSearch and Adblock Plus are four excellent reasons to use it over any other browser.
In all, 3.5 feels like it's perfected everything that 3.0 set out to achieve - it's extremely fast (granted awaiting multi-process support), integrates far better with the OS and does everything a browser should do. - e1ace, on 06/20/2009, -0/+8Hopefully you mean the RC and not the beta.
Just get the Nightly Tool Tester Addon and force it to install. Then check if it works. - LordVance, on 06/20/2009, -0/+8What Lil said. It's not even downright crashing that's annoying, when a single tab causes the whole browser to hang for 5-10+ seconds (which happens fairly regularly) it's downright annoying. Sandboxing the tabs solves too many problems to continue ignoring it as an option.
- Hellahulla, on 06/20/2009, -1/+8Calm down young padawan ... don't rush a release.
- llbbl, on 06/20/2009, -0/+7dont think that is a firefox issue, bud. could be related to the flash player combined with your operating system (not all flash players created equal) or RAM or lack of CPU. any way you look at it, not a FF problem.
- jshhmr, on 06/20/2009, -1/+8That's funny. I've had FF for over a year and haven't had one crash. Are you sure that it's not a user problem?
- EvilJon, on 06/20/2009, -0/+7I would start by disabling all addons - it's probably a rogue addon that's consuming your memory. If it becomes stable, start turning them back on one by one until you find the one that's the problem. If it isn't stable with no addons, try reinstalling - with 250+ million users exhibiting little more than minor problems, the issue almost surely lies on your end (which isn't a bad thing, it's valuable information to know to fix the problem).
- Hellahulla, on 06/20/2009, -0/+7That won't be fixed until release though. The extension developers don't want to fix something then have it broken again all of a sudden.
- HonoredMule, on 06/20/2009, -0/+7"Which way to go to reach the desired page" is to click on the desired menu entry, *****.
- spaceyraygun, on 06/20/2009, -0/+7learn keyboard shortcuts and remove the nav ui.
- hfactor, on 06/20/2009, -4/+11Why not?
- Youssif, on 06/20/2009, -2/+8Soon the fox will be unleashed, and the fire has been fed with more cunning of foxes ..
- Neiby, on 06/20/2009, -0/+6I've been using 3.5 since beta 99 came out and I don't recall it crashing once for me.
- Vintage912, on 06/20/2009, -13/+19Gotta Trust that Fire Fox!
- inactive, on 06/20/2009, -6/+12so...does the beta crash nearly as bad as the current "stable" version of 3.0.11 -ugh-
- DentThat, on 06/20/2009, -0/+5Will my extensions work on 3.5 RC?
- sampath3, on 06/20/2009, -0/+5Its much better than earlier version, i am using beta version,
- netneutrality, on 06/20/2009, -0/+5If it's exhibiting problems that frequently then you have ample opportunity to diagnose the cause.
- etsung, on 06/20/2009, -1/+6Yeah, it's great. It is more like a desperate plea that IE8 doesn't really suck....all that much.
- Plonkely, on 06/20/2009, -0/+5Paganize, the page you're currently on has a blob to the left of it in the back/forwards list. Pages above that are forwards, pages below are backwards. You can make the buttons smaller by right-click > customise > tick 'use small icons' > done.
- bartpieters, on 06/20/2009, -0/+5As people use more and more webapplication and -sites at the same time, separation becomes a must. The advantages are:
1. one slow page/application does not slow down all.
2. one crashing page/application does not crash all
3. one insecure/untrusty connection does not have instant access to all others
4. when closing a page/application the associated resources can be neatly freed up.
5. you can better make use of multi-core processes and multi-processes.
Getting back to your arguments:
1. Crashing of webpages/sites is not limited to plug-ins or flash. It happens more often but it is certainly not limited to it, I have seen my deal of buggy webapplications :) Besides regardless of why it crashes, I do not want to see everything go down. On forehand I do not know if a page will be using a plug-in or not and also I just want to do my thing and not worry about stuff like that.
2. Sure the same bug could hit all tabs, but it is unlikely it will at the same time etc.
3. Process separation makes it much easier and also the separation does not take all that much more memory. Because of being able to free up resources after you close page/application, after some time, you'll end up using less resources.
4. Chrome works fine under Windows and also LCIE is doing an ok job with IE8. One of the problems with porting something to Linux is that the lack of focus: Linux is wonderfully open but that comes with some challenges as well. Besides alpha's are alpha's for a good reason :)
5. I do not see how seperation makes crashes harder to debug. In fact it should make it easier as you can link crash-information to specific processes and therefore know which page/application caused the crash. - HonoredMule, on 06/20/2009, -0/+5That's retarded though. Firefox final is pretty useless if the extensions still don't work, and the RC's are *Release Candidates*...they are a perfect target for fixing your extensions now so they WILL be ready for the release. Extension developers shouldn't even be setting compatibility limits at the RC, they should be assuming Final will work if RC does, and saving us all this /pointless/ headache.
Honestly, after already going through a year of solid development, what are the chances that the minor quick-turnaround fixes they're making to RC's now will actually break a crucial API somewhere or affect a hack *that you shouldn't have been using in the first place?* Even in the incredibly remote chance that something like that does happen, what are the chances your extension will do anything more damaging than simply not work?
One thing that really needs to change, which would render this point less relevant and fix many other compatibility issues, is that addons.mozilla.org needs to start retaining full back (and forward) log of versions. In addition to selecting certain old versions, users should automatically be presented with the latest version *that supports their current browser* and have the option of trying out development releases. Development versions of Firefox should be able to just automatically fetch development versions of extensions if no stable version is available, and allow users by prompt to ignore compatibility errors for said development extension releases. This functionality all needs to work on both the site and with updating. - inactive, on 06/20/2009, -0/+4According to the internet it is true.
- tspchen, on 06/20/2009, -0/+4diggers rejoice!
- aserer511, on 06/20/2009, -0/+4nice and stable! haven't had a crash since beta 4. but needs moar extension support
- jsebrech, on 06/20/2009, -0/+4You really don't want H.264. Why? Because it's covered by patents and licenses. If it became the standard, somebody would have to pay for every copy of every browser out there that supported video. Even if mozilla could find that kind of money (which they can't), the smaller browsers (camino, konqueror, most phone browsers) wouldn't, decreasing the web's ability, and decreasing the number of competitors in the browser space. We would all lose by this.
Besides, H.264 is not necessary. See this comparison for how ogg theora (which they do support) is just as good for common use cases: http://people.xiph.org/%7Egreg/video/ytcompare/com ... -
Show 51 - 100 of 167 discussions
© Digg Inc. 2009
— Content created and posted by Digg users is 