Live data from Hacker News

It’s time to give Firefox another chance

techcrunch.com

41–50 of 733 posts

Re: It’s time to give Firefox another chance

#42
Give Firefox another chance, after Mozilla recently announced opt-out telemetry? Give them another chance now that they're siding with the likes of privacy-ignorant Microsoft? The same vendor that keeps bolting on features that seem irrelevant to its user base, such as "assumed touch", app store etc?

Surely one would only offer Mozilla another chance once they have extended an olive branch, rather than a closed-circuit television camera?

Re: It’s time to give Firefox another chance

#43
post #34

Firefox 57 is great. The interface is no longer ugly, and it's no longer oddly sluggish. Once Lastpass has their extension updated to work with WebExtensions, I'll switch.

After the most recent LastPass extension vulnerability, I no longer run LastPass extension in my default browser (Firefox). I have it installed on a different browser then copy/paste as needed.

Re: It’s time to give Firefox another chance

#44
post #2

I was extremely skeptical of all the changes they were doing - I said it myself 100 times, "they're just building a Chrome clone, they're killing all the features I like in favor of speed". But here I am, running Nightly because holy shit this thing flies. Their work has paid off and they're not even done yet. Webrender is coming, it's not quite stable enough for daily use yet (mostly just graphics glitching and inte…

One wonders why all the UI issues weren't solved long ago. Good that they're fixing them now, but what were they waiting for to decide to do it? (Rendering performance is a separate topic, that's been waiting on rust/servo.)

One might argue because they were "distracted" with making a phone OS and other endeavors.

Re: It’s time to give Firefox another chance

#45
> It’s no secret that Mozilla squandered a lot of time and energy on various projects that went nowhere (think its mobile phone OS, IoT services, creating a built-in video chat service, etc.).

The "built-in video chat service" is a webstandard. Called WebRTC, got mainly pushed by Google. Every modern browser implements this. Mozilla just decided to build a service which implements the server-side of this protocol. Which they needed anyways to test their client-side implementation.

So, the only squandered time and energy is that of the UX people that polished that server-side implementation up for public use.

And in return for that, Mozilla got excellent testing of their client-side implementation and direct feedback, if maybe people would want the Foundation to allocate some money to run such a service.

Re: It’s time to give Firefox another chance

#48
post #26

SeaMonkey (mozilla suite) is the only web browser I have ever truly enjoyed using. I use the browser, email client, irc client, address book, and calendar every single day. Extremely disappointed that Mozilla has basically given a big middle finger to the SeaMonkey/Thunderbird (comm-central) communities with the removal of XUL/XPCOM add-ons, necessity of multi-process, introduction of webextensions, removal of suppor…

Very few people are bothered by the movement to WebExtensions, multi-process, or removal of complete themes. Many, however, have stopped using the browser as it has felt slow and clunky for quite a while now. The recent changes have actually attracted me back to the platform after a decade of using Chrome.

Re: It’s time to give Firefox another chance

#50
post #2

I was extremely skeptical of all the changes they were doing - I said it myself 100 times, "they're just building a Chrome clone, they're killing all the features I like in favor of speed". But here I am, running Nightly because holy shit this thing flies. Their work has paid off and they're not even done yet. Webrender is coming, it's not quite stable enough for daily use yet (mostly just graphics glitching and inte…

One wonders why all the UI issues weren't solved long ago. Good that they're fixing them now, but what were they waiting for to decide to do it? (Rendering performance is a separate topic, that's been waiting on rust/servo.)

A Large part of the reason they couldn't easily address the UI performance was because of the old extensions.

The reason that Firefox switched to webextensions was in order to switch to a formal extension API that could be supported long term, instead of the old open integration API which made it difficult to readable without breaking all sorts of extensions.

There reason they adapted the web extension API that chrome uses, was because it largely made sense, was already pretty fleshed out and would allow extension writers that were already familiar with that to also target Firefox.

Post reply on HN