Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

It's definitely slower to actually load pages — I'm guessing that there are still a lot of network optimizations that more mature codebases have accrued that Servo hasn't yet — but holy cow are pages buttery smooth once they do load (and even while they're loading, which is unusual). Comparing Chrome and Servo in terms of UI jank felt pretty shocking, in Servo's favor. Kudos, it looks like Rust and WebRender have paid off.

Looking forward to seeing this evolve.



Yeah; we've mostly ignored the network stack.

So there's some extra copying in the IPC, and no speculative parsing, which can slow things down, among other factors.

Can be fixed, but priorities :)


I will absolutely love to contribute toward the network stack. Can you provide me any pointers?


In case you're looking for a place to jump in:

The thread that handles all the resources (http://, chrome://, file://, etc):

https://github.com/servo/servo/blob/master/components/net/re...

And here's the file that handles HTTP requests:

https://github.com/servo/servo/blob/master/components/net/ht...


Using pointers in rust is discouraged!


Do you have a reference for that claim? :)


boxes kibwen


We have http://starters.servo.org/, though there may not be network stack bugs right now.

I have some more involved projects planned for the network stack that aren't yet ready to be picked up though. I suggest working on some bugs above, getting familiar, and then asking in IRC for something in the network stack.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: