Live data from Hacker News

Transitioning Firefox's rendering engine from Gecko to Servo

jensimmons.com

131–140 of 219 posts

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

#131
post #71

Earlier quoted context omitted.

Servo makes incredibly good use of the GPU. Being able to do that, and iterate so fast on that work, is part of what Rust brings to the table. (I don't think they've swapped out the font renderer and image codecs yet, but there are quite a few bits and pieces they have swapped out as the Rust community delivers more pure Rust libraries.)

> Servo makes incredibly good use of the GPU. Too good, in fact: it won't run on any laptops that I own because their GPUs don't support a sufficient level of OpenGL. One great aspect of Firefox-with-Gecko is that you can throw it onto just about any machine with more than 512MB of RAM and it will provide bootstrap web access ( slow or otherwise ). That's going to be lost when everything is Servoised. I guess it's ba…

AFAIK that's not actually true, one option they have is going through Mesa's llvmpipe in such cases.

EDIT: to be clear, with the Servo nightlies you need to do this yourself but Firefox could bundle it eventually.

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

#132

I was honestly expecting an interesting story about a real jet engine being replaced in flight.

The story changed its title from being about Gecko and Servo to this literally in between me viewing the frontpage and clicking on the comments link. This story here is IMO should be extempt from the "original title" rule - the original title is annoyingly misleading.

Leave the title, append it with "Transitioning from Gecko to Servo".

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

#133
post #66

Earlier quoted context omitted.

Ironically Mozilla is the best counter-example to that Joel on Software article. The article specifically mentions that Netscape shouldn't try and re-write their browser. But if they hadn't done that, we wouldn't have Firefox. We'd still have an incremental improvement over Netscape 4.7. For those who can't remember Netscape 4.7, let me remind you, it wasn't very good at the end. If they hadn't rewritten it, causing…

Then again, Gecko itself started under Netscape, they just released it under an open license after the Mozilla thing was started. So in a sense it's still an incremental improvement over Netscape 4.7, at least when it comes to the rendering engine.

Gecko was the rewrite of the rendering engine for Netscape 6. Netscape 4.7 (and earlier) didn't use Gecko.

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

#134

I was honestly expecting an interesting story about a real jet engine being replaced in flight.

Me too! I was like "Whoa that's a novel idea...and it is about browsers...damn!" I was already conjuring up crazy scenarios similar to in-flight refueling.

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

#135
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…

Original Opera engine started somewhere in 1993, last update to Opera Classics was year ago.

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

#136
post #64

Earlier quoted context omitted.

> Wouldn't it be more appropriate to have written rust in a GPU language like OpenGL or OpenCL, since the aim here was to replace the display engine? That's not the aim of Rust. Rust, according to its own website is: > Rust is a systems programming language that runs blazingly fast, prevents segfaults, and guarantees thread safety.

Sorry I meant 'servo' not Rust.

Editing might be a good idea, it now sounds as if you have no clue what's going on while in a subcomment you mention it was just a mistake (can happen).

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

#137

Earlier quoted context omitted.

It's annoying and unprofessional. Stop trying to be cutesy and present the information in a way that people who are busy can consume quickly and make decisions on. Is this the tone of the whole project? I'd love to contribute, but I don't want to wade through a reddit-comment-thread-level of forced references and memes to do that. I get the reason for doing it, and I like that the internet isn't full of drab corporat…

> I'd love to contribute, but I don't want to wade through a reddit-comment-thread-level of forced references and memes to do that. I'm going to have call you out on this. You have no wishes to contribute. Because asking this question reveals you haven't even bothered to look at the repositories, join IRC channels, or subscribe to the mailing lists. You're here to complain and you're using hypothetical constructive m…

I love this comment.

The term for the grandparent comment is concern trolling.

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

#138
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…

I remember using Konqueror+KHTML much more recently than KDE 1.0 too :-). At one time it worked quite well.

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

#139

Earlier quoted context omitted.

No, "run" is Past Simple here. It took me a few moments to get that though.

Is that an Americanism? Ran is most common in the UK.

Yaggo had 'run' originally and has since edited the comment to read 'ran'.

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

#140
> Going forward, it will be much easier and more enjoyable to implement new CSS properties. Which makes it easier for folks in the open source community to contribute. Which makes new things come out faster.

I had never really thought of Servo in these terms before, but it makes a lot of sense.

Mozilla, being a nonprofit, can't compete with Google / Apple / Microsoft doing things their way. They inherently have a greater need for the free-time contributions.

Given that, if you can make contributions easier and "fun", by choosing a more modern language and toolchain, it could theoretically be a competitive advantage.

Thinking about it like this, the recent Rust marketing articles make a lot of sense. Rust marketing matters because the more Rust developers there are, the more potential Servo (and thus Firefox) developers there are.

Whether it pans out or not remains to be seen, but as a way to attempt to hack a problem, I really like it.

Post reply on HN