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

31–40 of 468 posts

Re: Firefox 70

#31

Post by lordnacho »

GhettoMaestro wrote: post #12
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

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!

I just tried this. Interestingly I'd left it on v68 and it cooked my MBP, fans all on max immediately. When I updated to 70 it seems to work perfectly. CPU temp in the 40s. Gonna leave it on in the background and see if it suddenly spikes.

Re: Firefox 70

#32

Post by tyre »

> 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 ascenders. The default value, auto, causes them to only be drawn where they do not cross over a glyph. To allow underlines to cross glyphs, set the value to none.

I'm so excited for these. Implementing sane underlines for headers has been a pain in the ass for far too long. Writers rejoice!

Re: Firefox 70

#33

Post by ufo »

Does anyone know how Firefox Lockwise compares to other password managers? For example, can it store additional notes next to the password?

Re: Firefox 70

#34

Post by eyegor »

pedrocx486 wrote: post #9

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

Does anyone know of what useful/killer features chrome dev tools have that ff doesn't? I switched to ff full time a few years ago and only open chrome for testing sites. The only thing I notice is that they have slightly different habits as to where they jump in the html when you are using the inspect feature. The only killer Firefox "feature" I can think of is an extension which is much more recent -- eval villain (https://www.hurricanelabs.com/blog/making-easy-dom-xss-actua...).

Re: Firefox 70

#35

Post by pjc50 »

xvilka wrote: post #23

I wonder, why they implemented Baseline JS interpreter in C++? Why not Rust?

I believe the Rust rewrite of parts is proceeding, but this tech blog explains what's going on: https://hacks.mozilla.org/2019/08/the-baseline-interpreter-a...

> The Baseline Interpreter sits between the C++ interpreter and the Baseline JIT and has elements from both. It executes all bytecode instructions with a fixed interpreter loop (like the C++ interpreter). In addition, it uses Inline Caches to improve performance and collect type information (like the Baseline JIT).

Including elements [of code] from both would be considerably harder in another language.

If you read closely it appears the interpreter is "generated" - that it, it's not written directly in C++ or anything at all, but is instead an interpreter emitted by the JIT compiler!

Re: Firefox 70

#36

Post by mda »

overcast wrote: post #4
ar7hur wrote: post #2

The one thing that prevents me from switching to Firefox is the spell checker. Like many non-native English people, I'm constantly switching between languages when typing. Chrome is smart with that, and detects the right language sentence per sentence. Is there a way to have FF do this? Did I miss something?

I'm assuming Chrome is reporting back to Google everything you're typing. Privacy is probably what's holding Firefox back.

No. Default is Hunspell based offline spell checkers, since the beginning of Chrome.

Re: Firefox 70

#37

Post by danShumway »

> Pause on DOM Mutation in Debugger

Heckin finally!

The dev tool improvements all seem good. Still no support for inline code edits, which means JS debugging will still be something of a pain, but strengthening Firefox's position as one of the better tools for debugging and prototyping CSS.

Re: Firefox 70

#38

Post by eyegor »

SloopJon wrote: post #30
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!

On the contrary, I'd say that competition has been good for all involved. For such a maligned language that was born in a little over a week, JavaScript is better and faster than it has any right to be. The amount of resources that have gone into improving JavaScript is amazing. I just wonder what some other languages would look like now with that kind of attention.

Only a week? And I would slap python 3 right on top of that. Despite the language being inherently messy and fully dynamic (similar to js), there are tons of static analysis tools, compilers, alternate run times, IDEs, etc.

Edit: the "only a week?" question was genuine, it wasn't meant to be tongue in cheek.

Re: Firefox 70

#39

Post by re4ctor »

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

More details on the mac improvements https://mozillagfx.wordpress.com/2019/10/22/dramatically-red...

Re: Firefox 70

#40

Post by Orphis »

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.

Post reply on HN