Earlier quoted context omitted.
Should we start calling it Servo by Linux now?
What's the connection to Linux?
The Linux Foundation ?
Servo’s new home
41–50 of 326 posts
Re: Servo’s new home
#42Wow, this is awesome. - Mozilla engineering finally gets the green light to beat Chrome through a from-scratch rendering stack - This skunkworks initative popularizes the world's first viable C++ contender and interesting "mainstreamable" programming language - Manglement suddenly lays off the teams responsible for both projects (Rust and Servo) - Some awesome person from the trenches convinces said manglement to rel…
Why is Mozilla not betting on Rust anymore?
It seems like they're just not placing big bets now. Creating an entire new programming language is a big bet, one that I'd argue already looks like it's paid off, but Mozilla has decided their future is as a much leaner company that does fewer experiments. It really is a shame.
Re: Servo’s new home
#43This is fantastic news. Servo has been doing exciting work, and it was disappointing to hear that Mozilla had disbanded the Servo team. I'm really excited to see where this will go. Will improvements from Servo continue to make their way down into Firefox?
> Will improvements from Servo continue to make their way down into Firefox? Unlikely.
It's difficult to characterize this as inherently bad, though. We could end up with three competing engines and major browsers, plus a long tail of webkit browsers. That's a pretty decent scenario for the rest of us.
Re: Servo’s new home
#44Awesome! I've been tire kicking their nightlys. I was thinking about building a "browser" but really mean just wrapping an engine. With the shakeup at M I was nervous that Servo would die, it's got a lot of promise. This is great news. Now, thoughts on a UI framework for Rust?
My personal opinion is that, for a servo based browser, it's probably better to just use UWP/C++ on Windows, C/GTK on Linux, and SwiftUI on Mac, and just embed Servo via its C-API layer. Rust shine when it comes to building a safe and fast web engine. For the OS "glue" code, I would stick to whatever is best for each platform.
You missed Android. Firefox for mobile is so far behind Chrome, it’s unusable for me, most plugins don’t work.
I would vote for HTML/CSS based browser (React / React Native?), though I know that a lot of operating system specific code needs to be written.
Re: Servo’s new home
#45Re: Servo’s new home
#46Earlier quoted context omitted.
Not yet, there is an embedding API, but it's designed for embedding into native apps. Servo uses Spidermonkey rather than v8 as the JS engine, so integrating into the node ecosystem would be tricky. But it would be nice to see a JS-first runtime system built around Servo!
I'd guess many Electron users don't care about the node.js parts at all, they simply choose electron because it's more popular than the alternatives like CEF.
Node has done a lot of work in defining a runtime outside of the browser. I'm guessing much of this work would need to be done with spidermonkey in order to match common functionality. It'd also help out an electron equivalent for gecko, too.
Re: Servo’s new home
#47We've been cagey about this over the months since the Servo team at Mozilla was disbanded, since there were various moving pieces that needed to fall into place. We're excited about the possibility for Servo to continue growing and evolving in its new home, though!
What's the plan exactly? Will there be a Servo browser that integrates the servo rendering engine with some open source components (for instance from Firefox, WebKit or Chromium) that will let us use the engine stand-alone, or is it "just" going to be an engine for embedding in third-party programs? The former seems like it would be a huge amount of work, but if it's the latter I fear for the long term survival of th…
This is also my concern. Everyone's cheering on, but I'm just thinking... What's the mission and end goal now?
Previously it was doing research, with the possibility of landing in Firefox. Now that's highly unlikely.
Re: Servo’s new home
#48Is WebGPU part of Servo? I know the guys at Mozilla were developing WebGPU API in Rust. Looking to see where it's going (I assume Firefox has to use it too. Chrome already has experimental support)
Any idea?
Re: Servo’s new home
#49We've been cagey about this over the months since the Servo team at Mozilla was disbanded, since there were various moving pieces that needed to fall into place. We're excited about the possibility for Servo to continue growing and evolving in its new home, though!
What's the plan exactly? Will there be a Servo browser that integrates the servo rendering engine with some open source components (for instance from Firefox, WebKit or Chromium) that will let us use the engine stand-alone, or is it "just" going to be an engine for embedding in third-party programs? The former seems like it would be a huge amount of work, but if it's the latter I fear for the long term survival of th…
With respect to the latter, I agree that it seems unlikely that the project would attract users. Maybe it’s my own ignorance, but I don’t know what kind of apps (besides web browsers) would want just the web rendering engine and not various other components in a web browser. What are the responsibilities of a “web rendering engine” anyway? How tightly coupled is it to the DOM? Does it “own” the DOM, or is that owned by some other component in the browser? In the latter case, how are the relevant aspects of the DOM communicated to servo? And does the rest of the web engine query servo for things (e.g., “what are the exact coordinates of this ?”)? If this engine ends up not being so web-specific, then maybe it could be used as a replacement for Skia, more or less.
Re: Servo’s new home
#50Earlier quoted context omitted.
What's the plan exactly? Will there be a Servo browser that integrates the servo rendering engine with some open source components (for instance from Firefox, WebKit or Chromium) that will let us use the engine stand-alone, or is it "just" going to be an engine for embedding in third-party programs? The former seems like it would be a huge amount of work, but if it's the latter I fear for the long term survival of th…
This is also my concern. Everyone's cheering on, but I'm just thinking... What's the mission and end goal now? Previously it was doing research, with the possibility of landing in Firefox. Now that's highly unlikely.
Is it really so unlikely? Firefox integrates all kinds of components from elsewhere; why shouldn't it continue adopting parts of Servo where appropriate?