| I had a conversation here with people about Servo and it was immediately clear that it was a collection of people who wanted to play around with Rust and not actually solve a problem that people have while saying that they did. They were way more concerned with bullshit like governance than meat and potatoes like writing a getting started article. > Servo’s mission is to provide an independent, modular, embeddable web engine, which allows developers to deliver content and applications using web standards. This is servo's mission, on their website, and the last time I checked, they provide absolutely no documentation on how to actually do it. If you need embedded, just use CEF like everyone else. If you need a browser base, just use Chromium. Everyone else is dicking around. I would have written a WebKit port[1] for my own purposes, because CEF has significant technical limitations, but WebKit has no documentation on how to do it either. They have documentation on what a WebKit port is, and what ones exist, but not actual documentation on how to create your own callbacks for view abstraction and blitting etc. It's a much more significant effort compared to just using CEF. [1]: https://trac.webkit.org/wiki/SuccessfulPortHowTo |
I've been compiling it locally and playing with it. I run it like:
$ servo https://news.ycombinator.com
To do that, I've got an alias set up to point to my dev build.
alias servo='f() { /home/tychi/SourceCode/servo/mach run --release $1 };f'