81–90 of 117 posts
I just tried it out. It froze when looking at a reddit comments page, it froze when I tried to use the URL bar. Pretty exciting nonetheless.
The URL bar does seem buggy and incomplete. I don't think it even supports copy/paste yet. It also won't let me type " https://..."
I'm really hopeful for this. The world needs a new browser engine, there is dwindling competition in this space and time and time again I find myself dissatisfied with browser offerings. 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 chanc…
> The world needs a new browser engine > As a non-dev I expect you are just responding to the inherent lack of performance that the javascript + html + css bundle shamelessly provides, which Servo will do nothing to sort out. Webassembly on the other hand is the first step to bringing superior performance to all browsers.
Earlier quoted context omitted.
> The world needs a new browser engine > As a non-dev I expect you are just responding to the inherent lack of performance that the javascript + html + css bundle shamelessly provides, which Servo will do nothing to sort out. Webassembly on the other hand is the first step to bringing superior performance to all browsers.
Servo doesn't really do anything for JavaScript (which is pretty much as fast as it's going to get, thanks to all the hard work of the V8, Spidermonkey, and SquirrelFish teams). But speeding CSS up is kind of the whole point of Servo.
Earlier quoted context omitted.
> The world needs a new browser engine > As a non-dev I expect you are just responding to the inherent lack of performance that the javascript + html + css bundle shamelessly provides, which Servo will do nothing to sort out. Webassembly on the other hand is the first step to bringing superior performance to all browsers.
Improving HTML + CSS performance is absolutely one of the goals of Servo. Here's a video from pcwalton demonstrating reflow (HTML), repainting, and CSS animations on the GPU in Servo: https://air.mozilla.org/bay-area-rust-meetup-february-2016/#... (much of this code is being uplifted to Firefox as WebRender). It's true that Servo won't have any effect on Javascript performance, but WASM won't have any effect on HTML…
I'm really hopeful for this. The world needs a new browser engine, there is dwindling competition in this space and time and time again I find myself dissatisfied with browser offerings. 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 chanc…
> The world needs a new browser engine > As a non-dev I expect you are just responding to the inherent lack of performance that the javascript + html + css bundle shamelessly provides, which Servo will do nothing to sort out. Webassembly on the other hand is the first step to bringing superior performance to all browsers.
Earlier quoted context omitted.
Servo doesn't really do anything for JavaScript (which is pretty much as fast as it's going to get, thanks to all the hard work of the V8, Spidermonkey, and SquirrelFish teams). But speeding CSS up is kind of the whole point of Servo.
And not just "CSS" but the whole DOM itself, which is more often than not what most people "perceive" as the slowness with web apps (and the entire reason why virtual-DOMs have caught on)
The concurrency story could also expand on the limited capabilities of web workers support for shared memory.
Earlier quoted context omitted.
Improving HTML + CSS performance is absolutely one of the goals of Servo. Here's a video from pcwalton demonstrating reflow (HTML), repainting, and CSS animations on the GPU in Servo: https://air.mozilla.org/bay-area-rust-meetup-february-2016/#... (much of this code is being uplifted to Firefox as WebRender). It's true that Servo won't have any effect on Javascript performance, but WASM won't have any effect on HTML…
I understand that, but the idea that HTML + CSS can only be sped up by some hugely parallel structure requiring a whole new programming language and browser engine is really quite shocking. I think once webassembly is established and in use, we will start to see steps in the direction of replacing HTML + CSS altogether, with something that has performance in mind.
I'm really hopeful for this. The world needs a new browser engine, there is dwindling competition in this space and time and time again I find myself dissatisfied with browser offerings. 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 chanc…
> The world needs a new browser engine > As a non-dev I expect you are just responding to the inherent lack of performance that the javascript + html + css bundle shamelessly provides, which Servo will do nothing to sort out. Webassembly on the other hand is the first step to bringing superior performance to all browsers.
Earlier quoted context omitted.
>> 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?
The user doesn't care whether the text rendering of one app is consistent with the same app on a different platform, the user cares whether the rendering is consistent with the other apps he uses on the same platform.
Just so you Servo folks know, we appreciate the plan of shipping components incrementally in Firefox, and realize the necessity, and how big a project building a whole browser is… …and yet… …I think you know we're all waiting for Servo itself to be usable as our main browser :-) Good luck!
Servo doesn't even support SVG yet, and I can remember how long it took Firefox to get SVG animation once plain SVG was in there. One can hope things will go faster this time around ;-)
I'm not worried about whether Servo supports SVG.