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

Firefox 70

hacks.mozilla.org

Post reply on HN
Print view View original

81–90 of 468 posts

Re: Firefox 70

#81

Post by alimbada »

redblacktree wrote: post #56
adfkbuvasdas wrote: post #10

Earlier quoted context omitted.

Game changer! Now from my POV Firefox is the best desktop browser, period. No caveats.

Is there a good transition path for someone who uses a lot of Google products? In particular, I use Chrome across all my devices, and I depend on the ability to search my history/recent tabs/etc from anywhere. Will Firefox give me the same ability? Is the transition literally just: Install Firefox everywhere and start using it instead?

> Is the transition literally just: Install Firefox everywhere and start using it instead?

Yep. I did this about a year ago. You have to create a Mozilla account (if you haven't already) in order to sync your tabs and history across devices, but that should be a given.

I find the Firefox sync a bit clunky compared to Chromes though. I think Chrome sends udpates to Google on each change whereas Firefox polls and updates on a schedule which means sometimes if you put a device to sleep (or if you're on iOS and the app gets suspended) your history and tab state won't be propagated and it'll be missing on your other devices which can be frustrating when you're away from those devices.

Re: Firefox 70

#82

Post by bzbarsky »

giancarlostoro wrote: post #55
pedrocx486 wrote: post #9

Compared to current Chromium based browsers (I'm using Edge/ium), how does this Firefox release's DevTools compare?

Some of those updates are to catch up to Chrome's developer tools. If I were in charge of Firefox, I would honestly have them hire a developer or two to focus solely on the Developer Tools. I'm sure there's many things that browser developer tools could do that we have not even scratched the surface of. I prefer Firefox overall, only use Chrome due to manager only looking at my work on Chrome (it will be deployed in…

Firefox has an entire team dedicated to developer tools, fwiw. I'm not sure whether your suggestion was "one or two more, in addition to the 7 or 8 already working on it", or "one or two more, instead of the 0 working on it now"...

Re: Firefox 70

#84

Post by bhj »

pier25 wrote: post #48
danlugo92 wrote: post #18

Earlier quoted context omitted.

Would this bring it up to par with safari's power consumption?

Safari still uses significantly less CPU while decoding video.

Also from the Q&A at the end:

> Safari’s compositor is entirely Core Animation based; Safari basically skips step 2.

(Step 2 is "the Firefox “compositor” assembles Gecko layers to produce the rendering of the window")

Re: Firefox 70

#85

Post by padenot »

volkk wrote: post #67
kemenaran wrote: post #3

Not mentioned in this article (although it's in the Release Notes [1]): the amazing work done regarding the macOS compositor. This should give pretty noticeable speed and battery improvements on Retina Macbooks. [1] https://www.mozilla.org/en-US/firefox/70.0/releasenotes/#new

does anybody know if all of these are available in nightly?

Yes, Nightly is (I'm simplifying a bit but it's generally true) release + a few weeks of patches + different default settings, sometimes experimental things enabled, etc.

I'm running Nightly on OSX and I confirm all those improvements are there, but more are coming.

Re: Firefox 70

#86

Post by antoineMoPa »

My message to the team would be: Please bring back the shader editor in devtools.

In a previous release, we had access to live reloading shader editor, which was really useful in my case, developing real time WebGL apps. It was a truly nice developer feature.

Re: Firefox 70

#87

Post by devy »

chenster wrote: post #69
GhettoMaestro wrote: post #12

Earlier quoted context omitted.

The performance is what has kept me on Chrome on Mac. Going to re-install FF now and give it a whirl. Thanks for this info!

You can also use Brave browser, it's basically Chrome with the ad tracking removed. With that, almost no reason to switch to another browser.

Brave looks amazing, the question I have is, just like how Google Chrome, can they be trusted as a private entity?

Re: Firefox 70

#88

Post by The_rationalist »

Orphis wrote: post #40
The_rationalist wrote: post #20

I would have wished a world where both the chromium project and Mozilla would collaborate to a unified JS compiler instead of having two separate implementations. How faster would have JS been? How more featureful and less buggy? BTW chrome 78 will be released today too!

Speaking as a member of one of the many W3C working groups, I would say that it isn't desirable. When designing a standard, we want to have multiple competing implementations of the standard to ensure it is well defined and understood by users. Should there be one implementation, we wouldn't be able to say with confidence that we have succeeded for that goal.

Your argument is moot, nothing prevent V8 to make two competitive implementations of a feature. With mozilla ressources focused on not duplicating effort, they would even have resources for making 3 or 4 compretitive implementations per JS proposals.

Re: Firefox 70

#89

Post by frenchyatwork »

frereubu wrote: post #74
tyre wrote: post #32

> Firefox 70 introduces three new properties related to text decoration/underline: > text-decoration-thickness: sets the thickness of lines added via text-decoration. > text-underline-offset: sets the distance between a text decoration and the text it is set on. Bear in mind that this only works on underlines. > text-decoration-skip-ink: sets whether underlines and overlines are drawn if they cross descenders and asc…

Don't want to rain on your parade, but this is a long way from being generally available: https://caniuse.com/#search=text-decoration-thickness 11% coverage, and almost all of that is iOS Safari.

This is one of these cases though, were coverage doesn't really matter. The fall-back is fairly reasonable.

Re: Firefox 70

#90

Post by pier25 »

bhj wrote: post #84
pier25 wrote: post #48

Earlier quoted context omitted.

Safari still uses significantly less CPU while decoding video.

Also from the Q&A at the end: > Safari’s compositor is entirely Core Animation based; Safari basically skips step 2. (Step 2 is "the Firefox “compositor” assembles Gecko layers to produce the rendering of the window")

You think this affects video decoding?

Anyway, I imagine that's the price to pay for being crossplatform. You can't implement everything for every platform. Safari only has to work on macOS/iOS.

Post reply on HN