Recommended Posts

erm , yeah ie9 is faster coz of dropping support for xp and not coz of some chakra (or dead code elimination :shiftyninja: ) , so yeah xp is the one to blame :)

attachment.cgi?id=525501

Some new stuff regrading the branches :D

Which build has this rolled out to? Or has it not rolled out yet, Aurora's current build is not updated with this UI yet, and it looks more refined than current builds.

Which build has this rolled out to? Or has it not rolled out yet, Aurora's current build is not updated with this UI yet, and it looks more refined than current builds.

it is JUST A MOCKUP , and tracking bug for it is : https://bugzilla.mozilla.org/show_bug.cgi?id=649480

Does this mean there is two sets of nightlies now, one set for Firefox 5.0 and one set for Firefox 6.0?

I'm getting a bit confused :(

No . Nightly now = Firefox 6.0a1pre(dated 13 april) , Aurora = Firefox 5.0 , but yeah for time being we have 4.2(dated 12 april) in trunk folder

No . Nightly now = Firefox 6.0a1pre(dated 13 april) , Aurora = Firefox 5.0 , but yeah for time being we have 4.2(dated 12 april) in trunk folder

Okay, thanks for clearing that up!

So think of it as Nightly = Chrome Dev, Aurora = Chrome Beta, Stable = Stable.

Yup, adopting that mindset now. I'll probably try running the nightlies now that they've revamped the icon/graphics. Bit wary of extensions breaking though, but we'll see - Chrome doesn't really have this problem on dev.

It works with extensions.CheckCompatibility6.0a.

Thanks but tried this command (even making the first 'c' lower-case) but my addons are still disabled. Tried adding a extensions.disableCheckCompatibility == true also seems to have no effect. Are you sure it was that command you added and not some other tool that disables compatibility checking? What am I missing?

Nice to see that once again Firefox is becoming primarily a Windows browser with Mac and Linux users supported by accident rather than actually deliberately designing for the platform. Promises of OpenGL accelerated layers in Firefox 5.0 and low and behold they've failed to deliver - why aren't I surprised.

Blame the platforms (OS X 10.6+ and X.org) - not the browser. Mesa has not even caught up to *Windows* in terms of OpenGL support, and even OS X 10.7 DP2 is even further back.

Also, both OS X and Linux distributions have continually refused to allow the same UI as Firefox 4 uses on Windows today. (Firefox 4's UI on Linux is identical to that of Firefox 3; what's up with that?)

True, but x64 browsers ATM, aren't ready for primetime yet. They're kinda like Office x64, nice to have, but not really needed by 99.9% of users.

That said, I hope IE10 x64 has the new JS engine IE9 x86 has.

If you have multiple mailboxes (say, GMail/GoogleMail and that of your ISP), Outlook 2010 x64 is a better choice than the same mail application in x32. The problem with Office 2010 x64 (like IE x64) is the lack of add-ons and plug-ins; most of the x64 plug-ins and add-ons that do exist were Microsoft-written.

I switched up with 2010 for exactly that reason - I have GMail and my ISP mail acount; both of which get a crapton of e-mail. Outlook 2010 x32 would bog down, if not flat-out fall down, while 2010 x64 runs like a champ, even using GMail's IMAP defaults.

Where x64 plug-ins and add-ons exist, Office, like IE (or even Firefox) is a lot more stable in x64 (stability FTW).

Wait so is it better to be on 6.0 nightly or 5.0 aurora ?

If 5.0 is still in the works and 6.0 at the same time, then will changes from 5.0 be added into the 6.0 channel and more ? Or will the changes made in 5.0 not be added to 6.0 until 5.0 is released or near release ?

Wait so is it better to be on 6.0 nightly or 5.0 aurora ?

If 5.0 is still in the works and 6.0 at the same time, then will changes from 5.0 be added into the 6.0 channel and more ? Or will the changes made in 5.0 not be added to 6.0 until 5.0 is released or near release ?

nightly = all latest patches will land there , not tested , can crash etc

aurora = selected patches from above ones would land here , i.e. changes in aurora will be in nightly , but not vice-versa , lil QA done on it , more stable than nightly

Here is my main issue with the 4.x release they just did and I hope it is much better in the new releases.

There had been quite a few incompatible extensions and add-ons that would not run in 4.0 for quite some time. (Firebug, Febe, Greasemonkey for example), but were later fixed after 4.0 went gold. I sincerely hope that during the big version rush into 7 for later this year, they don't abandon all of the extensions and then cause more update issues.

I am a big fan of bleeding edge software, but it was sort of hard during the betas because of the extensions. To me also, it seems like they are pushing the numbers too freely. Why bother with a 5.0 when you are going to go to 6.0 and then 7.0? Seems pointless to me. I personally would rather go with a version 4.6 with all the fantastic speed and features that version 7 will eventually have.

EDIT: Okay now, I really don't know if this is a placebo effect, but for kicks, I downloaded the Nightly and it seems to be loading pages a lot faster than my FF4, but then again, it did dump 99% of my extensions so that might have been part of it. :)

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Posts

    • The fact that memory in general is so high I have to take a loan out to build a computer now is just beyond stupid. Who's really to blame here? Low supply or high demand?
    • Display Driver Uninstaller (DDU) 18.1.5.5 by Razvan Serea Display Driver Uninstaller (DDU) is a utility for completely removing AMD/NVIDIA/INTEL graphics drivers and related packages from your system, attempting to eliminate all leftovers (including registry entries, folders and files, driver store). Though AMD/NVIDIA/INTEL drivers can usually be removed via the Windows Control Panel, this uninstaller tool was created for situations where standard uninstall fails, or when you need to fully remove NVIDIA or ATI graphics card drivers. After using this driver cleaner, your system will behave as though it’s the first time you’re installing a new driver—similar to a fresh Windows installation. As with all such tools, we recommend creating a restore point beforehand, allowing you to undo changes if issues arise. If you're having trouble installing an older or newer driver, try it—there are reports that it resolves such problems. Recommended usage: The tool can be used in Normal mode but for absolute stability when using DDU, Safemode is always the best. Make a backup or a system restore (but it should normally be pretty safe). It is best to exclude the DDU folder completely from any security software to avoid issues. You do NOT need to uninstall the driver prior using DDU. Requirements: .NET Framework 4.8 Compatible with Windows 7, 8, 8.1, 10, and 11 (32-bit or 64-bit) Note: Using on Insider Preview builds is at your own risk. Display Driver Uninstaller (DDU) 18.1.5.5 changelog: Added 'Reset to recommended' button for the Options. General fixes and improvements. Download: Display Driver Uninstaller (DDU) 18.1.5.5 | 1.7 MB (Freeware) Download: DDU Portable | 1.2 MB Links: Display Driver Uninstaller Home Page | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • WACUP 1.99.51.24568 Preview by Razvan Serea WACUP (WinAmp Community Update Project) is a modern, enhanced version of the classic Winamp music player, designed for better stability, performance, and compatibility. Built for Windows, WACUP retains the familiar Winamp interface while adding 64-bit support, bug fixes, and new features like improved audio format support, customizable skins, and optimized playlist management. Unlike bloated alternatives, WACUP focuses on lightweight performance and regular updates, making it the best choice for fans of the classic Winamp experience. Basically, if you miss the good old days of Winamp and want a modern upgrade that doesn’t mess things up, WACUP is for you! WACUP key features: Classic Winamp Feel – Keeps the familiar interface and functionality. Bug Fixes & Stability – Fixes old Winamp issues and improves performance. 64-Bit Support – Works better on modern systems. More Formats & Plugins – Supports additional audio formats and third-party plugins. Customizable UI – Skins and tweaks for a personalized look. Better Library Management – Improved playlists, media organization, and search. No Bloat – Focuses on performance without unnecessary extras. Regular Updates – Community-driven development with new features and fixes. WACUP 1.99.51.24568 Preview changelog: Fixed a deadlock seen from the recent crash reports when doing some of the drag + drop actions within the media library window Fixed a loading crash seen related to a problem with some of the artwork cache image files being restored which should now be better handled allowing for the bad image to be removed without it failing Fixed a deadlock seen from the recent crash reports when the internal metadata cache clearing is triggered which could block the main ui thread for too long with this now being moved to a background thread Fixed some performance issues with some of the methods related to determining artwork support which mainly affected the local library import / refresh (this is still slower for some compared to other players because there's more data & artwork aspects being checked for which means doing more processing on a single file despite the best of attempts to reduce duplicate / heavy processing where possible) Fixed a crash with the JTFE based missing files hotkey which no one seems to have used for an age for this to appear (maybe it's time to seriously consider stripping out features that aren't being used) Fixed how some of the file types which use extra information to reference their sub-songs is handled which was preventing some from being correctly resolved back to their base file (noticed fixing above) Fixed an issue with the handling of files with underscores in their filepath which wasn't being correctly handled causing some of the filename to be lost when shown as the title if title reading is delayed Fixed a few things that might be behind NotSoDirect not being stable for some setups though am still not certain that the changes done for this are going to fully resolve the problem from the crash reports Fixed the OS toast handling when there's no prior shortcut in the OS start menu to now create the shortcut (needed to allow the yes/no buttons for the new build / post-release toast) to be done as a hidden one so it's less likely to cause annoyance for those not wanting to see it whilst still allowing this less than ideal OS api implementation requirement to be met to avoid toasts without the needed buttons Fixed a regression when moving from taglib1 to taglib2 which broke some of the handling in place to allow for external programs to still access files when wacup has a held open cached instance of the file Everything else Updated cppwinrt (gen_win10shell.dll) to 3.0.260520.1 (26 May 2026) Updated libcurl (libcurl.dll) to 8.2.1 (24 Jun 2026) Updated Monkey's Audio (in_ape.dll) to 13.15 (28 Jun 2026) Updated mpg123 (mpg123.dll) to 1.33.6 (6 Jun 2026) Updated OpenSSL (libcurl.dll) to 3.5.7 (9 Jun 2026) Updated pugixml to 1.16 (16 Jun 2026) Updated taglib (tag2.dll) to 2.3.0 (11 May 2026) Updated vgmstream (in_vgmstream.dll) to the latest Git commit from 28 Jun 2026 Download: WACUP 64-bit | 9.6 MB (Freeware) Download: WACUP 32-bit View: WACUP Website | Screenshots Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • "over a thousand engineering hours" and started selling it but could not take a couple of minuets to send an AI email to ask permission. What an expensive lesson.
    • just tested it yesterday, a simple page with autoloading ADS takes 60mb....just 1 page for 60 megabytes.   poor people with a limited internet never will visit neolose
  • Recent Achievements

    • Week One Done
      Collagen Project earned a badge
      Week One Done
    • Reacting Well
      Wakeen1966 earned a badge
      Reacting Well
    • Rookie
      Almohandis went up a rank
      Rookie
    • Apprentice
      jahara21 went up a rank
      Apprentice
    • Reacting Well
      NovaEdgeX earned a badge
      Reacting Well
  • Popular Contributors

    1. 1
      +primortal
      526
    2. 2
      +Edouard
      265
    3. 3
      PsYcHoKiLLa
      146
    4. 4
      Steven P.
      99
    5. 5
      macoman
      55
  • Tell a friend

    Love Neowin? Tell a friend!