Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Firefox 58

mozilla.org

Post reply on HN
Print view View original

121–130 of 197 posts

Re: Firefox 58

#121

Post by samirm »

tdumitrescu wrote: post #22
k__ wrote: post #7

Switched back to Firefox a few months ago and I'm blown away by the speed. Last time I had this feeling after switching to Chrome from Firefox years ago, haha. Besides videos everything works like a charm. Somehow some videos won't start and sometimes I get a message that the video format could not be read, never had this issue in Chrome.

Yeah, the browser has gotten snappier. But then I pop open the dev tools and they're unbearably slow - like I simply can't do real dev work in FF anymore, have to use Chrome. It may be that I tend to do a lot of development with Web Components, which FF still doesn't have natively (though Custom Elements are live in 59/nightly, right?!), but either way it seems like a failing of the tooling that it beachballs for 5-1…

Have you tried the developer edition? https://www.mozilla.org/en-US/firefox/developer/

Re: Firefox 58

#122

Post by kuschku »

hutzlibu wrote: post #74
albertgoeswoof wrote: post #34

Earlier quoted context omitted.

Google inbox is terrible on ff, this is vendor lock-in by google, the new MS

Any proof of that claim? (that it is intentional from google and not just a ff issue?)

Google didn't even make Inbox available on Firefox for months because they didn't care, and when they did, they ended up serving entirely different HTML and JS to FF.

This is the same Google that is still keeping Allo Web and Google Earth a Chrome exclusive, the same one that has paid adware vendors to sneakily install Chrome, etc.

Sure, you can believe that this is jist a coincidence. But that's one unlucky streak of coincidences. In fact, you'd be more likely to win the Powerball ten times in a row than for all this to happen by coincidence.

Re: Firefox 58

#123

Post by [deleted] »

zintinio5 wrote: post #68
potch wrote: post #8

I wrote up a more detailed look at some of what's in Firefox 58: https://hacks.mozilla.org/2018/01/firefox-58-the-quantum-era...

How does one end up in a position to do this work at Mozilla? I'm currently looking for a new SWE role, would absolutely love to work on Firefox.

[deleted]

Re: Firefox 58

#124

Post by kuschku »

mdellabitta wrote: post #95
SAI_Peregrinus wrote: post #12

Earlier quoted context omitted.

And since this is HN, the download people here are most likely to want is the Developer Edition: https://www.mozilla.org/en-US/firefox/developer/

You can't disable telemetry in the Developer Edition for some reason, so I've gone back to Stable.

The official response — I asked — isthat by downloading dev or nightly you "automatically opt-in" into telemetry, because no one would download these "if they didn't want to help developing Firefox".

I've simply replaced all URLs in abou:config with https://example.invalid/, that makes sure telemetry is off.

Re: Firefox 58

#125

Post by potch »

zintinio5 wrote: post #68
potch wrote: post #8

I wrote up a more detailed look at some of what's in Firefox 58: https://hacks.mozilla.org/2018/01/firefox-58-the-quantum-era...

How does one end up in a position to do this work at Mozilla? I'm currently looking for a new SWE role, would absolutely love to work on Firefox.

I came to it from the web development world, and after getting into speaking transferred internally onto our DevRel team. We're a small team- we encourage any Mozilla employee to speak about their own work if they want, so there's only a few of us for whom it's a full-time job.

Since we're a small team, it's pretty uncommon for a specifically devrel role to open up, but the sibling reply from my teammate callahad is spot-on for how to get involved with Mozilla and Firefox!

Re: Firefox 58

#126

Post by shock »

andrepd wrote: post #13

Still on Firefox 56. My crucial addons still don't work. Still wishing Mozilla made FF56 into an ESR.

I was on FF 56 because of addons until Meltdown/Spectre happened. Just be aware FF 56 is missing the mitigations for those. Yeah, it would be great if Mozilla made FF 56 into an ESR.

Re: Firefox 58

#128

Post by jhasse »

callahad wrote: post #109
lucb1e wrote: post #38

Earlier quoted context omitted.

55 here because 56 breaks Mozilla's own Tab Center add-on. I see no mention of new APIs for add-ons in the release notes...

Tab Center was reimplemented using WebExtension APIs and released as Tab Center Redux: https://addons.mozilla.org/en-US/firefox/addon/tab-center-re...

That extension is missing several features the old extension had.

Re: Firefox 58

#129

Post by kbenson »

lod723 wrote: post #119
kbenson wrote: post #92

Earlier quoted context omitted.

Which shared a lot of roots with Chrome. It's probably that they are optimizing for things that are fast in Chrome's JavaScript engine, which isn't necessarily what's fast in Firefox's Javascript engine.

Safari's JS engine is different than Chrome's though, no?

Yes, although I'm not sure (and can't find god info on) whether they started from a similar lineage, or even if they just happen to just share some similarities that Mozilla's doesn't. If SquirrelFish (which became Nitro) happened to start with a similar architectural base, that could predispose them to make similar choices over time (e.g. if arrays are extremely efficient because the underlying types are well implemented, that could have survived and influenced later decisions. Array performance regressions might be seen as bugs that stop progress, and would possible cut of possible avenues of advancement).

There's a decade of history in these engines with a lot of man hours put into them, and they were actively competing with each other very loudly for a while. There's little you could tell me I couldn't find some possible narrative justification for if I consider the PR, bureaucracy, talent and design decisions that might stem from those over a decade.

Re: Firefox 58

#130

Post by fabrice_d »

callahad wrote: post #99
zintinio5 wrote: post #68

Earlier quoted context omitted.

How does one end up in a position to do this work at Mozilla? I'm currently looking for a new SWE role, would absolutely love to work on Firefox.

Current openings are posted at https://careers.mozilla.org/ . There should be a steady trickle of opportunities as 2018 budgeting wraps up and requests for headcount get approved over the coming weeks and months. We do most of our work in the open, so there's a wealth of information you can gather before applying for a role or interviewing. Lurking on mailing lists, reading Bugzilla, following GitHub repos, etc. are…

Working at Moz is usually nice, until it's not anymore for reasons that have nothing to do with how well you perform.

Examples: working from the wrong office (go tell the 70 people fired in Taipei that there will be a steady trickle of opportunities) or under the wrong VP. MoCo is in many aspects a company like any other, with its fair share of Dilbert worthy moments.

Post reply on HN