241–250 of 326 posts
Earlier quoted context omitted.
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.
Why should there be any great difference? Firefox is already written in a language where compilers have been optimized since decades. Rust will not bring that magic.
Earlier quoted context omitted.
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.
Why should there be any great difference? Firefox is already written in a language where compilers have been optimized since decades. Rust will not bring that magic.
(Provided that the C++ version is not strictly optimal WRT resource allocation; I think it's a rather safe bet.)
Earlier quoted context omitted.
MPL is a perfectly fine license. It has most of the benefits of permissive licenses (non-virality, worry-free integration with proprietary code) with most of the benefits of copyleft licenses also (changes to the library itself must be public). I fail to see what benefits a more permissive license would bring.
I have read this claim many times and yet to see any empirical evidence to back it up. If this license really hit the “sweet spot" between GPL and MIT/BSD then why haven't other projects outside of Mozilla funded projects adopted it. I think the reality is just the opposite. It neither gives the impression to contributors that their contributions are "protected" nor does it give lisensees the comfort that they will n…
For another, Mozilla has never really tried to "market" the license. It's hard to make something gain traction if you don't really try.
And then nobody really cares that much about licensing so if something is "good enough" and does what they want it to then they're going to stick to it. Especially if it means they get to avoid doing research about licenses.
And people that do really care about licenses tend to fall into camp permissive or camp copyleft with not a whole lot of in-between.
Earlier quoted context omitted.
We spent a significant amount of effort in the last year and a half working on a redesigned modular/parallel layout subsystem. The VR focus was because it was a good way to get servo out to end users early without needing to be fully web compat -- WebXR doesn't require complex layout. We didn't drop our focus on full web compat during this, but full web compat has always been a more long term goal given how complex t…
WebXR is also completely inane. What users are you "shipping" to? A tenth of a tenth of a tenth of a tenth of a percent of internet users? You have a massive effort ahead of you, and you won't get there by chasing distractions. You need to have a singular focus if you're going to accomplish this goal.
If they announced tomorrow they’d decided to focus all their efforts on using Rust to calculate digits of pi, that’s their perogative.
As a prolific creator with a strong sense of vision for your projects, I’d have expected this to be obvious.
We'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!
Hmmm Well, I'm not in the business, but if the team was disbanded, then where's the knowledge gone and who will be the next paid team ? I ask because I guess Servo is not the kind of project you just commit some patch over the weekend...
We'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!
Tangent: is your username in combination with that comment a reference to the Mozilla Lifeboat?
Earlier quoted context omitted.
Servo currently incorporates a network stack, a JS engine, the DOM, JS APIs, an HTML parser, a CSS styling engine, graphical rendering, media parsing and playback, etc. It is not a browser, since it doesn't impose requirements about how to load specific pages, interact with tabs, expose history or bookmarks, etc.
I thought Servo linked with SpiderMonkey rather than including their own JS engine
We'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!
Hmmm Well, I'm not in the business, but if the team was disbanded, then where's the knowledge gone and who will be the next paid team ? I ask because I guess Servo is not the kind of project you just commit some patch over the weekend...
Do 10 of those, and you'll probably have enough understanding to fix one off errors in the documentation.
Do 10 more of those, and you might start answering questions from other people re: how to help the servo project.
Answer 10 of those questions, and you might go, oh hell, I'm already answering questions, why don't I write a blog post introducing people to the servo project so you aren't repeating the same thing over and over again.
write 10 of those kinds of articles, and you'll be ready to be mentored by the great servo and rust community and start making larger code changes, algorithm changes, implementing a feature that you really wanted,
and so on.
You gotta start small!