So there's plenty of forward progress going on, it's just a bit more behind the scenes. As always, filing issues is super appreciated :)
On a side note, I noted that https://github.com/larsbergstrom owns lars.com. Wow! I wonder how much that is worth given that every 5th german is named lars ;) (though strom seems to indicate he is norwegian)
It has been pointed out more than once to me that I could instead of purchased many other .com names that were available at that time and be semi-retired :-)
That is completely untrue. Lars isn't exactly a rare name in Germany, but I'd be surprised if it was even one of the 20 most common first names. It's definitely nowhere near 1/5th of the population.
9869 of 40 million, so around 0.025% Yep, one in five :-)
It really is a nordic name.
I've tried every obscure browser out there, and many of them are great at specific things but nearly all of them lack a few key features or present an experience that frequently crashes.
I think the Servo project is the biggest chance that Mozilla has to make an impact in its "Internet for the people mantra."
As a non-dev I will do my part by guinea pigging nightly builds and submitting issues!
> As a non-dev
Why wouldn't you expect that to be faster?
Everything was perfecty smooth, but according to pcwalton the bottleneck was CSS handling.
The concurrency story could also expand on the limited capabilities of web workers support for shared memory.
There is another nice presentation on Rust and Servo: https://www.youtube.com/watch?v=7q9vIMXSTzc
Not sure if that's realistic, Servo app ran on macOS takes about 200MB of RAM usage.
And then hopefully people will start to notice that some of those applications are much faster on Android than they are on iOS, and Apple will allow other webviews than WebKit on there.
EDIT: When I say "won't respond at all," I counted to 30 before the next keypress eventually just to verify I was really seeing what I was seeing.
…I think you know we're all waiting for Servo itself to be usable as our main browser :-) Good luck!
I'm not worried about whether Servo supports SVG.
On Linux it's theoretically possible to force Servo into software-rendering mode, though when I've tried that it has done nothing even after 20 minutes.
However it's not yet available on other platforms:
I wondered, for what kind of problems should I bother to file issues? The page says:
> so please file issues about anything that doesn’t work as expected!
Wouldn't that be quite a lot of obvious stuff? I just opened one web page and see over ten rendering errors.
Even the text edit control of the built-in search-bar doesn't work as expected (text selection doesn't work, both with mouse and keyboard). There seems to be no way to scroll.
Then it crashed.
TBH, it's been hard to prioritize work to fix OpenSSL issues when we all knew it was going away from the dependency list. However, I don't think anybody anticipated the scope of work required to get there :-)
Sorry for the inconvenience!
Note that I fully support using a clean rust-based TLS implementation. Given how young servo is, it will have time to mature before Servo becomes widely-deployed. I just think this is an orthogonal problem.
PS: thanks for taking the time to answer here and keep up the good work !
But what makes software that's used everyday feel great are the small details.
I can't use Chrome (for consumption, though I use it for development) because of the way it renders text and a few other UI annoyances.
A browser is a lot of things, but to me, it's first and foremost a reading platform.
So please, do whatever you can to use the OS's native text rendering.
That seems odd and would mean different quality on different platforms. Yes, if native is better than built-in then I agree. But what if their GL based text rendering is just fine, shouldn't they use it everywhere because it's portable?
But on the Mac, light thin fonts on dark backgrounds look much better with Cocoa text on retina screen than anything else. That's why I can't use anything but Terminal.app, despite all the niceties other terminals provide.
Besides, I don't want to give up on the built in dictionary, spell checking, etc
That's a bit apples to oranges comparison, no? One thing Servo didn't touch is JS Virtual machine, it's still SpiderMonkey. Rewriting that AND the layout engine would be suicidal.
I would be unsurprised if Google were quietly doing something similar, of course, particularly with Mozilla having been quite open about this project for several years.
Also, current browser engines don't utilize multi-core processors, which Servo does, so even if you don't have a GPU at all, it should even there provide significant performance gains.
Mind the difference here between "browser engine" and "browser". Most browsers by now do utilize multi-core processors, but they only do so to run multiple tabs or the GUI in parallel. The actual browser engine still only stays on one processor. And well, with HTML being structured like a tree, it's actually incredibly well suited for parallelization, as you can process individual subtrees in parallel.
(And if you're asking yourself why no modern browser engine does utilize multi-core processors, that's because all of them were architectured in the previous millennium when multi-core CPUs weren't really a thing on desktop PCs. Also, the web was still mostly text, which is why no browser engine properly uses the GPU. So, yes, it's high-time for a browser engine being written from scratch.)
Not true. GPU layer compositing is implemented in all modern engines. That's how the CSS 3d transforms work. That's why the translateZ(0) hack existed to speed up animations (it created a new GPU layer. Now there's an official property for this, will-change.)
WebRender (used in Servo) goes a step further — it's not just compositing, it's actually rendering the colors, gradients, borders, shadows, rounded corners and so on in OpenGL. Look at the shaders: https://github.com/servo/webrender/tree/master/webrender/res
Why only this MSI package?
Every open source project worth mentioning releases also portable ZIP packages of the software. Mozilla's Servo windows builds get released only as MSI - why?
(BTW their win builds were available already for many months, just not linked from the frontpage, see bug tracker for more info)
@Mozilla: so please make the Mingw builds as download package as well. And don't forget to release everything as ZIP packages as well. (not just MSI)
I'm not a Windows developer by any means, but my understanding was that the major different compilers on Windows aren't ABI compatible. Also it's entirely possible Servo links against an external library that is built with VS.
but what they could do is to link statically with the runtime.
We have had Linux nightlies for ages now though.