Live data from Hacker News

Firefox Quantum Lands in Beta, Developer Edition

blog.mozilla.org

201–210 of 446 posts

Re: Firefox Quantum Lands in Beta, Developer Edition

#201
post #68

Wow, it really is blazing fast, and just at a glance I like what they're doing with the dev tools. Unfortunately... > Vimperator : "This add-on is not compatible with your version of Firefox." Ouch. Guess I might need to wait a bit to make this my daily driver. All in all, though, I have to say I'm really glad to see Firefox is still solidly in this race - and with a kick ass and quite possibly superior product to bo…

There's also Saka Key [ https://addons.mozilla.org/en-US/firefox/addon/saka-key/ ] that has an vim keybindings mode. It looks like currently Vimium-FF cannot open new tabs...

Re: Firefox Quantum Lands in Beta, Developer Edition

#202

Earlier quoted context omitted.

Tree Style Tab is the killer feature for me and some of my scientist coworkers. If this disappears or doesn’t work, I’ll probably use Chrome.

I have switched from Tree Style Tabs to the Test Pilot vertical tab extension (I don't remember the exact name) plus the about:config option that makes them always small, plus a few lines of userChrome.css to make the close button larger, like it was in one of the first versions. I recommend it.

It was called Tab Center, but now the experiment has ended. Is there a way to install the extension now?

https://testpilot.firefox.com/experiments/tab-center

Re: Firefox Quantum Lands in Beta, Developer Edition

#203
post #114

Might switch to Fox, but only with full support for Chrome extensions. Last time I checked - most of them didn't work on Nightly (can install with chrome store foxify, but most of the functionality is dead).

Feel free to reach out to those add-on authors and suggest they port to Firefox. It should be pretty much painless at this point, and we even have an online linter at http://extensiontest.com/ that should give them a good idea of what work needs to happen.

Re: Firefox Quantum Lands in Beta, Developer Edition

#204
post #176

As someone that jumped ship from how slow Chrome has gotten and went to Nightly /w Stylo and (CPU threads - 1) e10s processes enabled about 2 monthsish ago... Holy damn Firefox is actually fast. Fair comparison, both having Pocket, uBlock, Evernote, OneNote, Pushbullet, and Bitwarden; neither of them having an extension the other doesn't. Above described Firefox Nightly config vs Chrome Dev. Test machines are a works…

And here I am just enjoying my Opera. Built-in ad blocker, built-in WhatsApp Web, great UI, ultra fast, supports all modern web technologies.

the WhatsApp web feature is something that i never thought i use as much as i do. Really nice to have in the sidebar.

Re: Firefox Quantum Lands in Beta, Developer Edition

#205

This a most pointless decision. making firefox fast at the expense of the extensions. why would it make people switch back to FF? because it's 1% faster than chrome? come on, it's 2k17 and few care about that. Edge might be faster than both and people still would not use it. FF had its selling point to power users which is why i'm currently browsing from ff. Now there is no reason at all to use it. I guess there is n…

Firefox's main selling point for many has always been that it's fighting for a free and open web. And simply "not being Google" (/Facebook, but they don't have a browser yet) still is a selling point as well.

Re: Firefox Quantum Lands in Beta, Developer Edition

#206
post #172

I made the switch from Chrome to Firefox a couple of months ago primarily because of the open source and privacy aspects. I have to say I was impressed by the speed improvements, and since I started using Firefox Nightly a couple months ago, it's gotten even faster. Only complaint is that I don't have a working LastPass plugin yet, though they claim they'll have it released by the time v57 is finalized. I'd recommend…

Haha, it sounds like you meant "from Chrome to Firefox" :)

Re: Firefox Quantum Lands in Beta, Developer Edition

#207

Earlier quoted context omitted.

Firefox sandboxing does not use Rust. Servo sandboxing (work in progress) does. It's not accurate to say that Firefox has no sandbox. Sandboxing work has been rolling out for many months now, and later versions have increasingly restrictive sandboxes. You can see the current status per version here: https://wiki.mozilla.org/Security/Sandbox#Current_Status Hardening the sandbox is a constant work in progress, but it's…

Sorry I didn't mean Sandboxing used Rust, It was a separate thing (That Rust is less susceptible to such class of errors, so the more code written in Rust the better) Also didn't mean it has no sandboxing (I knew about efforts), my point was its security is not a match for Chrome yet, as seen from the amount and type of critical errors. When it is there I would definitely use it along with Chrome.

In case it wasn't clear, it is now the case that content process compromise is no longer critical unless combined with sandbox escape.

Looking at historical vulnerability reports can be misleading in this regard, as the sandboxing features are rather recent (pre-stable-version in some cases).

Re: Firefox Quantum Lands in Beta, Developer Edition

#208

Running Safari 11 on High Sierra and got a 90 on the speedometer 2.0 test referenced. Why are they bragging about a 66? For reference, ran the test with Firefox Quantum on the same machine and got a 68.

I get 35.82 on Safari 11 on El Capitan. What is your hardware? I wonder if I'm slower because I'm on older hardware, because I'm on an older version of OS X, or both?

My hardware is a Mac Pro (Early 2009), 2.66 GHz quad core Xeon, 32 GB 1066 MHz DDR3 ECC RAM, GeForce GT 120 512 MB.

What I get:

  35.82  Safari 11.0 (11604.1.38.1.7)
  34.89  Firefox 57.0b3
  32.01  Chrome 47.0.2526.106
  31.44  Firefox 58.0a1
  26.77  Firefox 55.0.3
I also for comparison gave it a shot on my Surface Pro 4 (Core i7, 2.2 GHz, 16 GB RAM, Intel Iris 540 GPU).

Here are the results for Chrome 60.0.3112.113. Since I was running on battery I tried this at various power mode settings. Here are the results for Chrome 60.0.3112.113 arranged by power mode setting:

  70.18  Best performance
  69.61  Best performance (2nd time)
  68.03  Better performance
  50.84  Recommended
  41.33  Battery saver
There are two runs of "Best performance" because I did the tests in the order best, better, recommended, battery saver, and so all but the first may have benefited from caching from the previous. I ran best again after finishing battery saver to get a run of best that would have the same caching benefit the other may have received.

For Firefox 57.0b3 I get:

  54.34  Best performance
  58.91  Best performance (2nd time)
  57.91  Better performance
  40.51  Recommended
  34.28  Battery saver
Edge on best performance gave 34.69.

Re: Firefox Quantum Lands in Beta, Developer Edition

#209
post #88

I can throw my hat into the ring and attest to just how great 57 is. I can remember the Australis update coming out and receiving a mixed reaction, but I can't see this update receiving anything but praise. If you've been on Chrome for a while I'd definitely encourage you to try it out. As a developer one small thing that's irked me is the recent removal of the ability for the dev tools to render html responses. Ther…

Yeah, the whole pulling the API rug out from under Firebug really disappointed me. The FF dev tools looked good initially, but I quickly realized I couldn't actually use them. It was death by a thousand papercuts: all of the features seem to have some trivial-seeming problem that ends up hampering productivity past the point where switching to Chrome's dev tools gets the job done. It may lack some things I do like about FF dev tools, but the features it does have actually work in a responsive and glitch-free manner.

Re: Firefox Quantum Lands in Beta, Developer Edition

#210

This a most pointless decision. making firefox fast at the expense of the extensions. why would it make people switch back to FF? because it's 1% faster than chrome? come on, it's 2k17 and few care about that. Edge might be faster than both and people still would not use it. FF had its selling point to power users which is why i'm currently browsing from ff. Now there is no reason at all to use it. I guess there is n…

And yet for the last couple of years every new extension released is Chrome only. Even uBlock Origin was originally a Chrome only extension.
Post reply on HN