3 ms·
But is it any faster at doing so than any of the competition? Specifically, are there any real benefits to the "parallel" aspect of this?
by taeric 13y ago
But is it any faster at doing so than any of the competition?
Specifically, are there any real benefits to the "parallel" aspect of this?
- pcwalton 13y agoI haven't measured Acid2 layout performance, because it's not particularly interesting; Acid2's CSS is nowhere near the CSS that someone would actually write in the real world. On real pages, from our small amount of testing, we've seen promising results.
- taeric 13y agoI'll have to give it another try. Last build I ran couldn't load that much. Of course, firefox is already bloody fast on any site I can think of. Not sure what sorts of improvements I should be looking for.
- pcwalton 13y agoOh, Servo certainly isn't a production-ready browser engine yet, if that's what you're looking for; the incomplete DOM code and network code prevent many sites from working.
- taeric 13y agoMore than just being production ready. I'm wondering what lessons have been learned that will actually help current browsers. Seems that servo is in a massive game of catch up, with no guarantees that things will be faster/better/whatever.
- anonbanker 13y agoI remember the same things being said about Mozilla/Gecko back in '99. That seemed to turn out pretty well for everyone.
- camus2 13y ago"I remember the same things being said about Mozilla/Gecko back in '99." Except nobody ever said that back in 99.
- anonbanker 13y agoInteresting. how does one go about proving a negative? To support my side, do a Google search for "Joel spolsky Mozilla". Hope that helps. Granted, it was written four months into 2000, but was reflecting murmurings one would read on Slashdot months earlier (back when /. was the HN of its time).
- taeric 13y agoI'm not sure what this proves, though. It didn't exactly work out well for Netscape. To be fair, the lesson learned there was to not bet your company on a rewrite. Which they are not doing.
- anonbanker 13y agoI'd say that the first thing it proves is you don't remember the tech scene in '98. All the comments you brought up in your GP post were reflected loudly by most pundits during that time. Cringley, spolsky, and many others said AOL was doing a fool's errand by allowing the then-unproven open source bazaar model to rewrite the browser. And that they'd be playing catch-up. And that IE would win because nobody would care about the rewrite. Fast forward to 2014, and blink/Firefox fight for first place, while IE continues to lose market share. Mozilla not only caught up, but is now setting the pace. The second thing it shows is that history repeats itself. The pundits, much like you will prove to be, were wrong. Thanks to the brilliance of jwz, the Mozilla project and the gecko rewrite has outlived both Netscape and AOL. Firefox is a flagship example of how open development can create a superior product that can outlast the companies that make it. The next thing this proves is that open development is continuing to show that rewriting an engine doesn't require "betting the company" anymore. Mozilla and Samsung are both heavily-invested in Servo, and are expecting this rewrite to be at the core of your future operating system. But if servo doesn't pan out, Mozilla won't be filing for chapter 11 protection
- pcwalton 13y agoIf you're looking for guarantees, you may not understand how research works :) When it comes to areas in which Servo is ahead of current browsers, I can name many: off-main-thread layout, parallel layout, off-main-thread iframes (not out of process to avoid scaling issues), a fully garbage-collected DOM without cycle collection/reference counting or stop-all-threads GC, and, most of all, being written in a memory-safe language. These are all areas in which other browser engines would need to catch up to Servo--though it's unclear how to do that without a complete rewrite, especially for that last one.
- taeric 13y agoI'm thinking there will at least be lessons learned. That lesson may be that going parallel offers no benefit. Which sucks, in that we are hoping otherwise, but it is a possibility. Right? That is, I am more asking as to what lessons have been learned. Not demanding that we know what progress was made. Since, as you point out, we may not have made any. Which is to say, I should throw up a huge "I'm not trying to dissuade any of this effort." If I have been too negative in my comments here, I humbly apologize!
- pcwalton 13y agoSure, no problem. Here is one: http://pcwalton.github.io/blog/2014/02/25/revamped-parallel-layout-in-servo/ http://pcwalton.github.io/blog/2014/02/25/revamped-parallel-... I'm hoping to make more blog posts.
- taeric 13y agoAwesome, thanks! This is pretty much exactly in line with what I was looking for. Looking forward to reading more of these.
- chriswarbo 13y ago> Of course, firefox is already bloody fast on any site I can think of. That's because all the sites we can think of are designed to be fast in Firefox (and other current browsers). Once super-fast browsers become standard, we can start designing sites that would be unusable on today's Firefox :)
- taeric 13y agoI can only hope I am not imagining the sarcasm that goes with that idea.
- nnethercote 13y agoSemi-relatedly, because Rust is a memory-safe language, there are whole classes of bugs (buffer overflow, use-after-free, etc.) that are impossible, which is great for Servo's security.
- taeric 13y agoThat actually makes a ton of sense. I think this should be trumped up more than the parallel abilities.