I'm not a Mozilla fan at all, but the Rust and Servo team certainly don't fuck around.
I'm Firefox and Thunderbird user, I also don't like Mozilla, but I'm full of respect for their work and... there is literally nothing better...
This Week In Servo 69
41–50 of 70 posts
Re: This Week In Servo 69
#42Servo is using zero-copy parallel parsing of html, css and parallel rendering, right? Is it trying to reduce in-going data duplication?
Any insiders (actually understanding this questions ;) who can comment on this?
Re: This Week In Servo 69
#43[deleted]
Re: This Week In Servo 69
#44Are they doing security testing as they go? I'm really looking forward to seeing how it fares against the typical "use after free" javascript errors that pwn to own always demo's. I'm not particularly a fan of Rust, but I certainly like the ideas that they are trying to incorporate in it. Great stuff. Looking forward to see how it evolves.
I enjoyed this 2014 blog post on how they avoid use-after-frees by design, by letting SpiderMonkey have responsibility for all DOM garbage collection:
https://blog.mozilla.org/research/2014/08/26/javascript-serv...
Re: This Week In Servo 69
#45Servo is using zero-copy parallel parsing of html, css and parallel rendering, right? Is it trying to reduce in-going data duplication? Any insiders (actually understanding this questions ;) who can comment on this?
> zero-copy parallel parsing of html,
zero copy yes, parallel I don't know
We do selector matching in parallel (parsing is probably serial?), layout in parallel, and offload almost all of the rendering work onto the GPU.
Not sure what you mean by "in-going data duplication". We try to be zero-copy when we can, and share as much as possible. Rust helps here; because you are free to try and share things without worrying if they will go out of scope too early, and the compiler will tell you if your guess was wrong.
Re: This Week In Servo 69
#46Earlier quoted context omitted.
So they achieved a 25% performance increase all from better parsing and a better algorithm for this[1] list? That's unexpected indead. I would love to see a blogpost with details on that. [1] https://publicsuffix.org/list/public_suffix_list.dat
They changed the implementation from always iterating over this 6000 length array: https://github.com/fduraffourg/servo/blob/8bb853f64354b2cc1b... to a HashSet which is only filled once based on a text file. The domain list also more easily updated now with a python script.
Why are there actual services in that list? I see all the variations of blogspot.com for example, which is definitely not an eTLD. Are services providing subdomain registration supposed to talk to Mozilla and get themselves added to it? I don't see deviantart in there.
Re: This Week In Servo 69
#47Totally irrelevant: But did anybody else notice '(John) Connor (Kate) Brewster'?
Its Connor MacLeod, not John Connor ;)
Re: This Week In Servo 69
#48Servo would be more compelling for use with commercial software if had MIT or Apache license. The MPL isn't as bad as GPL but still isn't as generous to the developer as MIT or Apache. With the right license, Servo would be a slam dunk for replacing CEF in commercial software that prohibits reversing or tampering.
Re: This Week In Servo 69
#49Servo is using zero-copy parallel parsing of html, css and parallel rendering, right? Is it trying to reduce in-going data duplication? Any insiders (actually understanding this questions ;) who can comment on this?
> zero-copy parallel parsing of html, zero copy yes, parallel I don't know We do selector matching in parallel (parsing is probably serial?), layout in parallel, and offload almost all of the rendering work onto the GPU. Not sure what you mean by "in-going data duplication". We try to be zero-copy when we can, and share as much as possible. Rust helps here; because you are free to try and share things without worryin…
Thanks!
"in-going data duplication" ummm... i guess i meant ;) duplication of the incoming data (network packets->buffers->resources like html-files etc) in the sense of trying to minimize the amount of data duplicated and moved around to be used by various code-parts.
Most probably the most interesting parts are those areas where even Rust can't really "help" to prevent that. thanks
Re: This Week In Servo 69
#50Earlier quoted context omitted.
https://servo.org also has a "Contributing" section, which links to bugs tagged as "easy" for new contributors.
The "easy" bugs get picked up super fast, so it seems you need to keep a close eye on the issue tracker.
You can also ask in IRC and we'll try to think of some for you. We try to keep posting new ones, but we get half a dozen new contributors per week, so it can be hard to keep up with the awesome demand.