Live data from Hacker News

Transitioning Firefox's rendering engine from Gecko to Servo

jensimmons.com

41–50 of 219 posts

Re: Transitioning Firefox's rendering engine from Gecko to Servo

#41

I'm on this rust hype train for a long time. This move by mozilla is probably going to be the biggest success story that might give rust a lot of attention. I hope the new engine is fast as heck and uses less battery in all my devices. Please!

If performance is not competitive, it will not be much of a success story, but it will be more interesting to see how much better it will be in terms of security issues.

Re: Transitioning Firefox's rendering engine from Gecko to Servo

#42
post #32
post #18

Earlier quoted context omitted.

Others have pointed out that Netscape's rewrite gave us Firefox, so the rewrite was incredibly successful.

If you call Firefox incredibly successful.

As a charity with hundreds of millions in revenue and employing over 1000 people I'd call Firefox and Mozilla pretty successful.

Re: Transitioning Firefox's rendering engine from Gecko to Servo

#43
post #12

> And Firefox runs on Gecko. Which is old. Like really old. I think it's the oldest rendering engine still in wide use. Gecko may be oldest, but not with wide margin: KHTML (the origin of webkit and blink) was started in 1998, only a year after Gecko. Of course, probably not much (if any?) of the original KHTML source is still present in webkit, and because of the nature of open source development, there is blurry li…

> KHTML (the origin of webkit and blink) was started in 1998, only a year after Gecko. Of course, probably not much (if any?) of the original KHTML source is still present in webkit

At least this part is still there: http://www.hanshq.net/roman-numerals.html#khtml

Re: Transitioning Firefox's rendering engine from Gecko to Servo

#44
post #41

I'm on this rust hype train for a long time. This move by mozilla is probably going to be the biggest success story that might give rust a lot of attention. I hope the new engine is fast as heck and uses less battery in all my devices. Please!

If performance is not competitive, it will not be much of a success story, but it will be more interesting to see how much better it will be in terms of security issues.

It was better 2 years ago (with caveats) - https://www.phoronix.com/scan.php?page=news_item&px=MTgzNDA

But there's definitely place for speed gains due to multithreading.

Re: Transitioning Firefox's rendering engine from Gecko to Servo

#45
post #8

The submission title has been changed from "Replacing the Jet Engine While Still Flying" to "Mozilla’s project to replace Gecko with Servo" (at the time of this writing). Some of the other comments are pertaining to the "Jet Engine" title. For anybody that might be confused, like I was :)

Unfortunately the new title seems to be misleading in a different way. There is no "project to replace gecko with servo". There is a project to advance gecko so it is state of the art in browser engines. Much of the current state of the art has been developed in Servo, and the natural way to bring that technology to gecko is to integrate the components from servo directly. This has other nice properties like increasing the Rust-to-C++ ratio, which we believe will be a win for safety and maintainability. But it is nevertheless components, rather than the whole shebang. Servo, for example, only just got document.write support and still (as far as I know) doesn't have a correct representation of document history. So it is some way from being a production grade engine for use on the general web.

Re: Transitioning Firefox's rendering engine from Gecko to Servo

#46

I didn't look at the name of the writer when I started reading it but by the way the article is written I was suspecting it was written by a woman. Stupid analogies and fluff, lots of commas... What a loss of time...

I'm sure you didn't mean it that way, but that sounded a little bit sexist.

Re: Transitioning Firefox's rendering engine from Gecko to Servo

#47

I didn't look at the name of the writer when I started reading it but by the way the article is written I was suspecting it was written by a woman. Stupid analogies and fluff, lots of commas... What a loss of time...

I don't know how to say this in a civil way, so I won't: Please take your sexist bullshit somewhere else if you can't behave like an adult.

Re: Transitioning Firefox's rendering engine from Gecko to Servo

#48
post #32

Earlier quoted context omitted.

If you call Firefox incredibly successful.

As a charity with hundreds of millions in revenue and employing over 1000 people I'd call Firefox and Mozilla pretty successful.

It has enjoyed success during its lifetime, but the userbase has looked like an upside-down hockey stick for some years now. I would say that having your userbase drop from a dominant majority of the market to well below 10% of the market is indicative of failure.

Re: Transitioning Firefox's rendering engine from Gecko to Servo

#49
post #31
post #8

The submission title has been changed from "Replacing the Jet Engine While Still Flying" to "Mozilla’s project to replace Gecko with Servo" (at the time of this writing). Some of the other comments are pertaining to the "Jet Engine" title. For anybody that might be confused, like I was :)

Does that mean that the original title was bad, as the HN guidelines states, "Otherwise please use the original title, unless it is misleading or linkbait."?

The title wasn't misleading at all, I totally understood it was about web browser rendering engines.

Re: Transitioning Firefox's rendering engine from Gecko to Servo

#50
post #20

This seems apt: https://www.joelonsoftware.com/2000/04/06/things-you-should-... Mozilla spending time on this suggests Mozilla doesn't know what to spend time on.

It seems you either haven't read or understood either Joel's article or this article. They are going for small incremental changes, instead of rewriting code from scratch, which is what Joel warned against. They aren't saying, fuck Firefox, replace it with Servo. Instead the idea is use Servo as a way to discover better layout, rendering components and transplant it into Firefox. See Strangular Application pattern ht…

I see what you're saying, however they don't seem to be "strangling" Gecko in the Strangler-pattern sense of the word. Rather it seems they're borrowing smaller pieces (Stylo) written in a foreign language and integrating them with Gecko as the main engine.

To me that sounds like the end-state is a Chimera and not a Lion, without any incremental end-user benefits along the way.

Post reply on HN