[deleted]
Servo’s new home
111–120 of 326 posts
Re: Servo’s new home
#112Very good news for Rust.
Re: Servo’s new home
#113I am confused. I thought it is the raison d'être of Mozilla to develop a browser. So how does it come that the brand new browser engine they developed is being given away? I mean, even if they need to cut costs, isn't Servo part of the team they should keep until the end?
My understanding is that Servo was more experimental research, with an eye towards possibly being integrated at some point.
Re: Servo’s new home
#114Earlier quoted context omitted.
Every thread tangentially related to Mozilla has a bunch of people who don't understand how non-profits work come in and complain about executive compensation.
I'd say >$2.4M in exec comp[1] isn't just making up for a lack of stock options. [1] - https://www.cnet.com/news/mozilla-cuts-70-staff-as-part-of-p...
The absolute number doesn't matter. Non-profits participate in the same labor market as for-profit companies. You have to compare it to executive salaries for other similarly sized companies in their market segment to make the argument that she is overpaid. Otherwise you're just arguing against income inequality, which is not a problem exclusive to Mozilla, and crippling Mozilla's ability to participate in that labor market will not fix it.
Re: Servo’s new home
#115Earlier 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…
A third-option that I would like to see is extending the latter to an Electron alternative (aka using Servo as a cross-platform GUI). There's definitely positives to Electron, but it would be nice to see a more performant, less memory hungry, and more battery friendly alternative.
Servo last time I checked used the same if not more memory (100MB) for basic pages. There doesn't appear to be major differences for that application yet.
Re: Servo’s new home
#116I am confused. I thought it is the raison d'être of Mozilla to develop a browser. So how does it come that the brand new browser engine they developed is being given away? I mean, even if they need to cut costs, isn't Servo part of the team they should keep until the end?
I most definitely agree.
All I can think is that they took a look at Servo and decided it was cool tech but was really nowhere near delivering things they needed for Firefox aside from Stylo which it had already delivered.
Re: Servo’s new home
#117Servo is starting to remind me a little of Minix, where it is an ambitious project attempting to fix underlying architectural problems, but the scale of the project being so large that ecosystem progress outpaces it's ability to adapt. I hope I'm wrong.
That's a well-known problem unfortunately. http://doc.cat-v.org/bell_labs/utah2000/utah2000.html
To be a viable computer system, one must honor a huge list of large, and often changing, standards ... A huge amount of work, but if you don't honor the standards, you're marginalized. ... At another level, instruction architectures, buses, etc. have the same influence. With so much externally imposed structure, there's little slop left for novelty. Even worse, commercial companies that "own" standards, such as Microsoft and Cisco, deliberately make standards hard to comply with, to frustrate competition.
Re: Servo’s new home
#118> or donating to help cover the project’s new CI and hosting costs, Planning to do exactly that tonight. I'm one of those who stopped donating to Mozilla once I realized none of the money donated could ever be used for developing the browser. If anybody else thought like me tonight might be a good time to prove we were principled, not cheap. Edit: one more thing. Hopefully at some time we can now recreate Firefox wit…
I’m not in a position to donate right now, so thanks a lot for donating to this project. Though I do wonder how much influence Servo will have on preventing browser monoculture given that as a stand-alone thing it can’t be or isn’t involved in developing standards. Mozilla will still have to play that role. I hope they step up to the plate and stay focused on this most important thing.
> I’m not in a position to donate right now, so thanks a lot for donating to this project.
I've been there myself for years.
I'm happy to now be in a position not even have to think to donate tonight.
Hopefully you too will get there soon too!
Edit: and thanks for your contributions to netty and graphql-java!
Re: Servo’s new home
#119I am confused. I thought it is the raison d'être of Mozilla to develop a browser. So how does it come that the brand new browser engine they developed is being given away? I mean, even if they need to cut costs, isn't Servo part of the team they should keep until the end?
My understanding is that Servo was more experimental research, with an eye towards possibly being integrated at some point.
Except multiple parts of it had already been integrated into Firefox, providing its most recent performance gains (Webrender, Stylo).
Re: Servo’s new home
#120I am confused. I thought it is the raison d'être of Mozilla to develop a browser. So how does it come that the brand new browser engine they developed is being given away? I mean, even if they need to cut costs, isn't Servo part of the team they should keep until the end?
I most definitely agree. All I can think is that they took a look at Servo and decided it was cool tech but was really nowhere near delivering things they needed for Firefox aside from Stylo which it had already delivered.
And Webrender.