9 ms·
64-bit Firefox for Windows should be prioritized, not suspended
- mwsherman 14y agoAny Mozilla devs wish to weigh in? The article sounds reasonable but is speculative without a first-party response.
- jonchang 14y agoI believe the idea is that there aren't enough Windows people to work on both 64-bit and the Metro UI for Firefox. Metro is a priority, so 64-bit is getting mothballed for the near future. [1] https://groups.google.com/d/msg/mozilla.dev.apps.firefox/jpX_z5zieD4/dUp-FnItf8cJ https://groups.google.com/d/msg/mozilla.dev.apps.firefox/jpX...
- beedogs 14y agoThat's kind of a shame, because I don't think Metro will be sticking around for very long.
- dietrichepp 14y agoI'm not sure it won't stick around. People said that about Aqua (OS X) and the Gnome 3 shell.
- bad_user 14y agoMFC, Windows Forms, WPF, Silverlight ... all of them still around, but all of them being obsolete by whatever Microsoft's du-jour UI framework happens to be. Gnome 3 is not the same thing, as Gnome 3 is just a window manager, based on the same X, the same APIs and the same GTK, just as Unity and Gnome 2.
- zurn 14y agobzbarsky posted a longish comment on another subthread: http://news.ycombinator.com/item?id=4838078 http://news.ycombinator.com/item?id=4838078
- joenathan 14y agoI think Mozilla is misapplying its development time on stuff like social integration [1] and Firefox OS [2]. I would say these types of projects would be fine if they weren't ignoring their mainstay, by first canceling the process per tab project Electrolysis and now abandoning 64bit builds on Windows says to me that Mozilla seriously has its priorities screwed up. The web browser has become the most important app on the PC, with more and more web pages demanding more and more resources, I really wish Mozilla would refocus on making the best web browser available. A few weeks ago I tried to delete some of my history from Firefox, I opened the history window, hit Shift and selected about 6 months of history and hit delete, and it took Firefox about an hour to delete the history all the while the UI going from responding to not responding back and forth. Firefox has some serious performance problems. [1]. https://blog.mozilla.org/blog/2012/11/20/firefox-introduces-new-social-api-and-previews-integration-with-facebook/ https://blog.mozilla.org/blog/2012/11/20/firefox-introduces-... [2]. http://www.mozilla.org/en-US/firefoxos/ http://www.mozilla.org/en-US/firefoxos/
- jonchang 14y agoDevelopers are not fungible. The social integration work was mostly HTML5 and JavaScript, and Firefox OS is partly kernel and OS work (B2G), and partly HTML5/JavaScript work (Gaia). 64-bit builds on Windows requires Windows developers, who are focusing on the Metro UI. EDIT: I'm responding to your edit here: > A few weeks ago I tried to delete some of my history from Firefox, I opened the history window, hit Shift and selected about 6 months of history and hit delete, and it took Firefox about an hour to delete the history all the while the UI going from responding to not responding back and forth. I would imagine the Firefox developers spend their time optimizing the parts of their browser that users would most likely use. I suspect that they are not terribly worried about an action that users would take (at most) once every six months. EDIT2: I guess I'll respond to this one too: > The web browser has become the most important app on the PC, with more and more web pages demanding more and more resources, I really wish Mozilla would refocus on making the best web browser available. Making the best web browser is not Mozilla's goal. Their goal is to "promote openness, innovation & opportunity on the Web" [1]. Integrating social features into the browser is part of that, in the sense that users will be able to control their social presence from their browser, rather than being locked-in to a specific social provider's web site. Mozilla's actions are not inconsistent with their stated mission. (Whether you agree with that mission is another argument entirely). [1]: https://www.mozilla.org/en-US/mission/ https://www.mozilla.org/en-US/mission/
- webwanderings 14y agoNot too long ago, there were hardly any 64-bit hardware in the market for average users, until they flooded the market and now every other Ma and Pa owns a Windows running on 64-bit.
- potkor 14y agoDesktop hardware has been 64-bit since the 2003 Athlon 64, 2004 Pentium 4 and 2003 PowerPC G5. Servers 10 years+ earlier(X). I guess 9+ years on the desktop is "not too long" if your beard is long enough :) X) http://en.wikipedia.org/wiki/64-bit#64-bit_processor_timeline http://en.wikipedia.org/wiki/64-bit#64-bit_processor_timelin...
- masklinn 14y agoSoftware not so much though, 64b XP basically didn't exist, and for 7 I've no idea what the ratio is. And 64b on Windows is a complete fuck-up (even when running a 64b Windows), apple's "fat binaries" made the transition smooth as butter for most users (the only issue I ever had were a pair of kernel extensions), in 7 64b is still screwy and the vast majority of software available seem to remain 32b.
- kevingadd 14y ago64b on windows is a fuck-up? I haven't had a problem with 64/32-bit compatibility since windows 7 came out, other than devices that only have 32-bit drivers. And you'll have that problem anywhere - even Apple's marvel of engineering where you double the size of executables won't solve that. Software shipping as 32-bit isn't a bad thing. It means it will run on more machines. Shipping a Windows application as 32-bit has NO negative consequences unless your application needs more than 2GB of available address space, with a couple rare exceptions like shipping device drivers or debugging tools.
- Tloewald 14y agoApple's "marvel of engineering" actually does. You can launch an app in 32-bit mode (while running in 64-bit mode) should you require interoperability with 32-bit components. All actually pretty neat. And given that most of an app isn't executable binaries (and hasnt been since forever) the size of executables isn't a big deal. (A few years ago I had to run Safari in 32-bit mode to test unity web apps for the brief period where unity didn't offer a 64-bit plugin.)
- zurn 14y agoPretending this was a political decision (vs just being what the Windows hackers decided to use their time on)... Let's tally the arguments so far for prioritizing 64-bit Windows development. Pro: The Ars article lists some Win64-specific security-bug mitigation features, unclear how significant these are. Con: The Windows PC is a declining platform, and the current 32-bit product covers all of the platform currently. There's probably a shortage open source developers working on Windows-specifics. 32-bit is much more memory-efficient. 64-bit breaks compatibility with plugins. Address space shortage will likely be covered by the tab unloading feature mentioned in the article, before it becomes an issue in practice. Overall sounds to me like You Ain't Gonna Need It.
- pjmlp 14y ago> The Windows PC is a declining platform... That must be the reason I get am getting more .NET contracts than Java ones I suppose.
- potkor 14y agoYes, its triumph over the Java Desktop has been impressive.
- rbanffy 14y ago> That must be the reason I get am getting more .NET contracts than Java ones I suppose. The kind of contracts you have is entirely dependent on your skill set and your network. The last time I was paid to write C# code was 8 years ago. You need cooler friends ;-)
- lucerosama 14y agoHas anyone tried WaterFox? http://www.waterfoxproject.org/ http://www.waterfoxproject.org/
- yoshamano 14y agoIn light of this recent development that's what I just switched to. I was using the 64-bit builds over at http://wiki.mozilla-x86-64.com/Firefox:Download http://wiki.mozilla-x86-64.com/Firefox:Download when Adobe first kicked out a 64-bit beta of Flash. Later I switched to the official Nightly builds when they went 64-bit. Unfortunately I'm not able to offer much insight into if it was better. Aside from a couple of short strings of bad builds that caused crashes I never had any issues with them.
- pacmon 14y agoI've been waiting ages for Mozilla to get their act together and make a 64 bit browser. I had never heard of this before. I just downloaded it and I'm trying it right now. So far it seems great. All my extensions seem to be working with no problems and it feels like it's faster. Thanks for the link!
- aluhut 14y agoIt is great. Speed alone would be a reason to change but the best thing about it is that it is not banned on my companys PCs as FF or any other browser then IE are. I finaly experience speed and adfree browsing again.
- ck2 14y agoSuspended != Abandoned Sometimes it saves a huge amount of effort to wait for things to mature otherwise before proceeding. If your firefox is using more than 4gb of memory ( >2gb via LARGEADDRESSAWARE) you have other problems, and 32bit code is almost always faster than 64bit with current CPUs.
- rplnt 14y ago> Suspended != Abandoned Well, the original quote said that it won't "ever see the light of day".
- hackmiester 14y agoI fail to see how if "my Firefox" is using a certain amount of RAM, I have any problem at all. If I am using Firefox in a reasonable way (i.e., not 400 tabs open or something), why should my RAM usage even be a function of anything I am doing, at least to the point for it to utilize 4GB of RAM?
- konstruktor 14y agoI certainly hope that memory is a function of how much content is loaded because one would expect a modern desktop application to keep all its non-persistent working data in memory, and not try to outsmart the OS when it comes to memory management. After all, RAM is cheap, your OS is perfectly capable of managing virtual memory, and addressable memory isn't a problem on 64 bit systems. The irony is that one of the reasons why modern mobile OS often feel faster than desktop applications on much faster hardware is because their APIs force programmers to give up this kind of hubris. So basically, Mozilla is building FirefoxOS, which will enforce the reasonable behavior they aren't capable of themselves when in the role of an application developer.
- hackmiester 14y agoI think RAM usage should be a function of work load. However, here I sit with 12 tabs open and Firefox using almost 1GB of RAM. I don't know when this became okay, but I could see Firefox using 4GB of RAM, easy. At this rate, that would be due to the ungodly workload of 48 tabs.
- cpeterso 14y agoFor comparison, Chrome is 32-bit on both Windows and Mac OS X. Chrome's multi-process architecture means memory limits are less critical, but Chrome doesn't benefit from any of the 64-bit security features mentioned in the Ars article. (Firefox is 64-bit on Mac OS X and Linux.)
- comex 14y agoAs the article mentions, the same security arguments apply to Chrome for Windows and OS X - especially on OS X, where 32-bit applications really get short shrift of hardening measures. Right now on my Mac, there's some argument to be made that Safari is the most secure browser, simply because it has sandboxing (unlike Firefox) and is 64-bit (unlike Chrome), despite Chrome's healthy obsession with sandboxing and good security record.
- chj 14y agoNot surprised at all, and IMO a good move. Mozilla needs to focus on its Firefox OS development. By the way, MS doesn't want 3rd party browser on its Windows RT, that could be a very discouraging factor.
- DigitalSea 14y agoWith moves like this is it any wonder why Chrome basically hit the ground running with market share as soon as it hit a stable release? I got tired of the Mozilla bureaucracy a long time ago when they failed to acknowledge there were some serious memory leak issues with addons and the browser itself slowly consuming hundreds and eventually gigs of memory the longer it was left open, it wasn't until later builds (this year) they released a version that fixed this by sand-boxing the addons or something to that effect. I still remember the time Mozilla developers were fighting about removing front-facing version numbers from the browser, it's also at that point I realised there are some issues with the Firefox development team all while Chrome and even Opera gained more market share. Remember where your loyalties lay, Mozilla. I think they're starting to spread themselves too thin with wasted development of a Firefox OS and social integration. Halting 64 bit versions of Firefox for Windows for the time being might seem like a small, trivial thing, but it's not and I think it's a bad move.
- masklinn 14y ago> With moves like this [...] Chrome You mean the Chrome which can't even be arsed to provide 64b builds on platforms where it's easy (Linux) or trivial (OSX), let alone hard (Windows) ones?
- lvillani 14y ago> You mean the Chrome which can't even be arsed to provide 64b builds on platforms where it's easy (Linux) [...] $ file /opt/google/chrome/chrome{,-sandbox} [10:47:39] /opt/google/chrome/chrome: ELF 64-bit LSB shared object, x86-64, version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux 2.6.15, BuildID[sha1]=0x2df3f5f435cb5747ea72be922c428b9a0017cb50, stripped /opt/google/chrome/chrome-sandbox: setuid ELF 64-bit LSB executable, x86-64, version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux 2.6.15, BuildID[sha1]=0xd02cf32515390b01af9aa5b1a53cd1dfb4fb7a35, stripped
- deleted 14y ago[deleted]
- 14y ago
- Allower 14y agoOr maybe you could stop using windows since its a substandard OS with an embarrassing new release.
- lazyjones 14y agoAs long as Mozilla is 95% or so dependent on funding by Google, there's a conflict of interest present that will very likely not lead to Mozilla's Firefox being a competitive browser. If you think otherwise, you're a hopeless romantic... As a conclusion, it is not surprising at all that Mozilla is focusing on developing products that do not compete with Google's browsers and other software.
- freehunter 14y agoYou seem to believe that Google cares about Chrome more than their Firefox contract. I don't see this being likely. Chrome makes Google no money besides having Google as the default search. Firefox makes Google money in exactly the same way. Firefox is just as important to Google's revenue as Chrome is. All Google needs is search results to show advertisements on and a browser capable of running their applications. Both Firefox and Chrome meet this requirement.
- lazyjones 14y ago> Chrome makes Google no money besides having Google as the default search. Firefox makes Google money in exactly the same way. Firefox is just as important to Google's revenue as Chrome is. You forget that Google pays Mozilla a lot of money for something they can get for free every time a Chrome installation replaces a Firefox installation. So the potential savings for Google is (currently) $300M/year once they have killed off Firefox completely.
- ubershmekel 14y agoAm I the only one who can't believe firefox updates itself and add-ons when it starts? I just wanted to check something on the internet and now is when you decide to stop and delay the user?
- toyg 14y agoThe opposite is also true: "I just wanted to shut down and go home, and now is when you decide to stop and delay the user?" This is an old problem. Chrome solved it the right way by stepping out of the startup/shutdown dichotomy and doing everything in background. Just one of the many areas where Google ran circles around Mozilla (with the benefit of moving from a clear slate, and probably also of staying away from the Gecko clusterf*ck).
- blablabla123 14y agoThat's what I call irony... So it seems that Internet Explorer will be soon, at least on Windows, (again) the technological most advanced browser. Microsoft did their homework.
- gsnedders 14y agoIE10 and Opera 12 are the only two browsers shipping 64-bit Windows binaries today in preference to 32-bit: take from that what you will.
- jorisw 14y agoFirefox needs to grow up, or be suspended altogether. IMHO, its horribly behind. Technically behind on WebKit, behind usability wise on almost any browser. Yesterday I ran into a 5 year old bug in Firefox (https://bugzilla.mozilla.org/show_bug.cgi?id=405761 https://bugzilla.mozilla.org/show_bug.cgi?id=405761) that required me to write Firefox-specific JavaScript workarounds. I used to accept that from IE, but from Firefox, never.