Live data from Hacker News

Firefox's JIT is getting significantly faster

groups.google.com

221–230 of 286 posts

Re: Firefox's JIT is getting significantly faster

#221
post #202

Earlier quoted context omitted.

What happens to the Firefox core dev team if the Mozilla Foundation's main revenue source -- the Google search tie-in -- dries up? Google is probably just waiting for the day that Firefox market share is below a threshold of viable competition, at which point they'll pull the plug on the search engine contract and it's game over for the Mozilla Foundation, unless the Mozilla Corporation can step in and save it, which…

It's possible Google will keep paying what is peanuts to them not to be technically an absolute monopoly (by keeping Firefox alive at insignificant usage level)

That actually seems like the more nefarious route, and thus the more likely one for Google.

Re: Firefox's JIT is getting significantly faster

#222
post #211

Earlier quoted context omitted.

Safari and edge are enough, I doubt google needs Firefox as a competitor like gates needed Apple (and injected funds)

I thought Edge was now a paint job over Chrome?

So is Safari, there's only really two engines now, Chrome (Edge, Safari, Opera, Brave, et al) and Firefox (Tor).

Re: Firefox's JIT is getting significantly faster

#224
post #28

Earlier quoted context omitted.

I think it will take more time to say that for certain. Warp is an exception, but most of the recent improvements to Firefox were initially prototyped and developed in the experimental Servo engine which was to my knowledge intended to eventually replace all of gecko. Most of the team for that has been let go. I think the thing to be worried about is: what will happen when they run out of stuff that's already in the…

> Or will they have to concede like opera and edge did. I am sad to say this, but I think it's only a matter of time. At this point, the list of parties driving Web standards basically consists of a whole bunch of organizations that rely on Blink, plus Apple and Mozilla. WebKit can probably hang on for a good long while because ~15% of user-agents are required by fiat to be WebKit. Gecko? At 5% marketshare, I fear it…

As a vue developer I don't have issues with Firefox's javascript engine, maybe it's different for react? I develop on FF exclusively these days as I know that if it works here it'll likely be fine everywhere - except IE11 which is going the way of the dinosaur.

Though as if to invalidate what I just said, today's actually the first day where I found a bug in Chrome that every other browser got right. Flex reverse row was right aligning my div and every other browser properly left aligned it... I was pretty shocked.

Re: Firefox's JIT is getting significantly faster

#225
post #113

Earlier quoted context omitted.

This is catastrophism. If Mozilla can make a browser that developers enjoy using as daily driver, developers will make stuff for it. If Mozilla can build bridges with framework makers, frameworks will work just fine. They just need to regain some of the focus that was squandered on too many moonshots and hazardous choices (FFOS, Pocket, etc).

I think that that may no longer be enough. The elephant in the room is the Web taking over non-Web apps. If Electron is part of your deployment surface, you can't escape Chromium. If Cordova is part of your deployment surface, it's Chromium or WebKit. A nice UI on the dev tools is nice, but I imagine most people would take an acceptable UI over a nice one if the acceptable one is how you get a development environment…

Electron is shit though, the only good Electron app that doesn't completely drain my battery and hoard my cpu is vscode, EVERYTHING else is a steaming pile of shit, looking at you slack.

Flutter will be the interesting newcomer to the multi platform game, they've been working closely with the big OS teams to optimize performance on Mac, Linux and Windows and truly compete with native. So far I've only used it for mobile but the temptation is there and I'll eventually try it.

Re: Firefox's JIT is getting significantly faster

#226
post #211

Earlier quoted context omitted.

I thought Edge was now a paint job over Chrome?

So is Safari, there's only really two engines now, Chrome (Edge, Safari, Opera, Brave, et al) and Firefox (Tor).

Safari isn't Chromium-based, it's WebKit; Chromium forked Blink out of it.

Re: Firefox's JIT is getting significantly faster

#227
I started using Firefox lately and like it but there are times when it really stalls and that hasn't happened in chrome in for like the past 10 years or so. Does anyone else have similar issues with FF? I want to stick to using FF but I expect/hope these issues get fixed.

Re: Firefox's JIT is getting significantly faster

#228
post #12

Nice! There's still cool cpp stuff going on in Firefox. This is one example. https://searchfox.org/mozilla-central/source/js/src/jit/Warp...

Please cite a line or maybe a git comment. No-one is going to filter through 3000 lines of cpp code.

Re: Firefox's JIT is getting significantly faster

#229
post #209

Earlier quoted context omitted.

> kill all of them except .com and .org A bit tangential, but ignoring reality for a minute wouldn't it make more sense to kill .com and .org as well and retain only the country codes (ie .us, .uk, .cn, etc)? At least it would make the various jurisdictional issues clear. (In a perfect world, I also wish there were legislation forcing any and all local government entities to use appropriate .gov. domains. It is incre…

Hmm that's an interesting idea. I personally like the idea of "cyberspace" transcending national boundries (i know, eyeroll), which is why i'm a fan of only .com, but your proposal makes a certain amount of sense.

What? How does limiting TLDs to only .com make any sense and how does that help with transcending national boundaries? I'm no fan of how new TLDs have been rolled out either...

Take a look at the Public Suffix List because you'll need to do away with a lot of TLDs.

Re: Firefox's JIT is getting significantly faster

#230

It's sad how these valuable optimizations are unknown to the average person. When I hear "the browser" discussed in almost any parlance, the implication is Chrome. It's rare to even hear someone say "Chrome," as it's the defacto choice for the non-mobile web. Convenience breeds ignorance.

But if it was just about convenience, wouldn't everyone be using Edge?

Because as far as I know, chrome doesn't come loaded on safari or windows

Post reply on HN