5 ms·
Well, this is all terrible. They mention having to use the nightly or developers releases instead of their walled garden versions. But both of those are unstabl
by superkuh 11y ago
Well, this is all terrible. They mention having to use the nightly or developers releases instead of their walled garden versions. But both of those are unstable and very crashy. And how likely are they to keep the unbranded version up and updated as time goes on?
And getting rid of the entire firefox add-ons community is just insane. The add-ons are what makes firefox good. It's why people use Firefox. I guess if they just want us to use Chrome this series of changes will work great.
- eli 11y agoFirefox Developer Edition is for web developers, not for browser developers. It isn't like a nightly -- it's stable. https://www.mozilla.org/en-US/firefox/developer/ https://www.mozilla.org/en-US/firefox/developer/
- superkuh 11y agoHave you used it? After I heard about the changes coming down the line in 41 a week or so back I immediately downloaded it and started configuring it to be my new main browser. The only problem was that it crashed constantly. It's just anecdotal but my personal experience backs up what I've said here.
- the8472 11y agoWell, to give a counter-anecdote: I've been using nightly for years and only experience severe problems maybe a handful times per year, the rest of the time it works fine. And that's with several extensions and many tabs.
- ohkine 11y agoFYI, i have used Aurora/DevEdition almost exclusively (outside of testing) on at least a dozen different Windows and OS X machines ever since the Aurora channel was created and i have never once had a serious problem. Occasionally i find little visual glitches or whatever, but it rarely ever crashes and i never get data loss or anything severe like that.
- dblohm7 11y agoDeveloper Edition should not be considered stable, by any means. It is still roughly equivalent to the Aurora (ie, alpha) channel.
- maxerickson 11y agoWhy do you think they are getting rid of the community? They are (presumably) making life easier for cross browser extension developers, and the first big deprecation is about 16 months away. We are implementing a new extension API, called WebExtensions—largely compatible with the model used by Chrome and Opera—to make it easier to develop extensions across multiple browsers.
- the8472 11y ago> Why do you think they are getting rid of the community? They're getting rind of those people who are willing to dive deep into the internals do develop something that nobody thought of before (if they did there would be high-level APIs for it).
- sp332 11y agoWe will also continue supporting SDK add-ons as long as they don’t use require(‘chrome’) or some of the low-level APIs that provide access to XUL elements. Seems like there's still a lot of power available, if you really want to dive in.
- the8472 11y ago> as long as they don’t use require(‘chrome’) or some of the low-level APIs That's the powerful parts. The high-level APIs are fairly restrictive, quite similar to chrome APIs, maybe even less powerful on their own.
- sp332 11y agoI don't know if that means that they will be disallowed, or just maybe broken.
- the8472 11y agoMozilla has an add-on review process in place. So you probably wouldn't get a new addon approved that relies on those APIs. And with enforced signature signing you can't even distribute it to users yourself. So effectively it will restrict extension-development to a whitelist of APIs. Everything else will be verboten, maybe with varying degrees of enforcement. It certainly doesn't sounds like an open system to me.
- charlesism 11y agoI don't have sufficient command of the English language to fully express how strongly I disagree with this. I have an extension which I made for Chrome and Firefox. The Chrome version basically consists of a single Javascript file, and a tiny json file with about 15 entries. I spent perhaps an hour to learn the basics from scratch. I don't have space here to describe all the crap I went through to get the same extension working on Firefox - and I was using their easy API. The Firefox extension development process is one of the most confusing, complicated, experiences I've ever had on a computer. Good riddance!
- CyberShadow 11y agoHave you tried the Jetpack SDK? New, simpler addon APIs are fine, but not when they replace more powerful ones. I guess that it's inevitable that Firefox has creeped from a "power user browser" to a dumbed-down maintstream one. I guess it's time to start looking for a new power-user browser.
- charlesism 11y ago> I guess that it's inevitable that Firefox has creeped from a "power user browser" Think about that statement in the context of Firefox's history. It's totally backwards. Firefox was not supposed to be a power user's browser. That was Netscape. Firefox was supposed to be a simple browser. And once upon a time, that's exactly what it was.
- maxerickson 11y agoThe mission of the Phoenix browser was to be end user focused. This did involve jettisoning a bunch of complexity that was there for the Mozilla suite or whatever else anybody with commit privileges had thought of, but simplicity wasn't an overriding goal.
- charlesism 11y agoThat's not exactly how I remember its origin story, nor how I remember it being written about when it rode its first crest of popularity. The last thing people talked about was Firefox being a tool for power users. It was "Tell your friends and relatives to switch to Firefox! Finally MSIE has worthy competition! Look at how uncluttered and easy to use it is!" I don't recall anyone talking about flexibility, or advanced features, unless they were tied into its ability to render webpages without a bunch a glitches. Here's the introduction they gave it over at boingboing.net: " Firefox, an Internet Explorer killer, has gone 1.0 By Cory Doctorow at 3:46 am Tue, Nov 9, 2004 Firefox, the finest, most secure Web browser ever created for average-user applications, went 1.0 today. You can download it below, toss out Internet Explorer, and be relatively assured that you computer won't be compromised due to Microsoft's bad design decisions and lax security maintenance."
- andzt 11y agoAs someone who has written several extensions across all the different browsers (IE COM Interop FTW!!!) over the last few years, Chrome's dev experience is by far the best in my humble opinion. Firefox's experience was hamstrung by having to learn XUL and a new and different set of tools and way of doing things. Their approval process and packaging scheme was surprisingly not as streamlined as I would have expected from them either. Chrome's experience is fairly standard and intuitive HTML, JS, and JSON interactions. In most cases it really shouldn't take too long for someone to port or migrate an old Firefox plugin to the new format.
- epidemian 11y ago> It's why people use Firefox. Extensions are probably the least reason why i use Firefox. The few extensions i use are also available in Chrome. Other reasons to use Firefox (at least for me): - It's free software. - Uses less RAM than Chrome (when having many tabs open). - The address bar is awesome; i can always find previous pages i visited from there without having to google them. - It's backed up by a non-profit organization, instead of an advertisement company.
- pekk 11y agoThe vast majority of Mozilla's funding comes from Google.
- wsha 11y agoIt's probably better to compare Firefox to Chromium which is as free as Firefox. I think the RAM and address bar comparisons could be addressed by extensions in Chromium. So really you are left with the last point about funding, but Mozilla gets its money somehow and it's mostly not coming from charitable donations.
- wtbob 11y ago> Well, this is all terrible. That's become my default response to Mozilla news. It reminds me a lot of what I started going through maybe 6 years ago or so with GNOME. 'Wait, what?' 'Why?' 'You've got to be kidding me!'