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!
Transitioning Firefox's rendering engine from Gecko to Servo
41–50 of 219 posts
Re: Transitioning Firefox's rendering engine from Gecko to Servo
#42Earlier 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.
Re: Transitioning Firefox's rendering engine from Gecko to Servo
#43> 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…
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
#44I'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.
But there's definitely place for speed gains due to multithreading.
Re: Transitioning Firefox's rendering engine from Gecko to Servo
#45The 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 :)
Re: Transitioning Firefox's rendering engine from Gecko to Servo
#46I 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...
Re: Transitioning Firefox's rendering engine from Gecko to Servo
#47I 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...
Re: Transitioning Firefox's rendering engine from Gecko to Servo
#48Earlier 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.
Re: Transitioning Firefox's rendering engine from Gecko to Servo
#49The 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."?
Re: Transitioning Firefox's rendering engine from Gecko to Servo
#50This 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…
To me that sounds like the end-state is a Chimera and not a Lion, without any incremental end-user benefits along the way.