Transitioning Firefox's rendering engine from Gecko to Servo
1–10 of 219 posts
Re: Transitioning Firefox's rendering engine from Gecko to Servo
#2I was disappointed after reading the title when I saw the article...
Re: Transitioning Firefox's rendering engine from Gecko to Servo
#3I was disappointed after reading the title when I saw the article...
Yeah, talk about setting people up for a letdown. :)
I was expecting some insane experiment from the golden era of aviation.
Re: Transitioning Firefox's rendering engine from Gecko to Servo
#4This didnt deliver.
Re: Transitioning Firefox's rendering engine from Gecko to Servo
#5Even though the title might disappoint, it's super interesting to see where Firefox is going. I can't wait for 2017!
Re: Transitioning Firefox's rendering engine from Gecko to Servo
#6Missed opportunity to name the CSS engine replacement project "Gangnam".
Re: Transitioning Firefox's rendering engine from Gecko to Servo
#7Even though the title might disappoint, it's super interesting to see where Firefox is going. I can't wait for 2017!
Looking forward to it too; this is a big deal because it will put a Rust implementation on many millions of desktops. I'm totally fed up with CPU and memory hogging browser bloat on my laptop. My dev env runs so much better when I kill all Chrome processes. I know that the article is only talking about the render engine, and not JavaScript, which I suspect is the main browser bloat culprit , but I'm still hopeful. Bring on the Rust JS engine I say!
Re: Transitioning Firefox's rendering engine from Gecko to Servo
#8The 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
#9I'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!
Re: Transitioning Firefox's rendering engine from Gecko to Servo
#10It will definitely be welcome to see the fairly aging Gecko replaced. The nightly build of servo barely renders a number of websites and won't at all for more media laden sites (as you'd expect). I hope this merge via Quantum[1] will be forthcoming soon, so we can test it.