Page 1 of 2 12 LastLast
Results 1 to 10 of 14

Thread: Mozilla's Servo Still Going Forth To Parallelize The Web

  1. #1
    Join Date
    Jan 2007
    Posts
    13,396

    Default Mozilla's Servo Still Going Forth To Parallelize The Web

    Phoronix: Mozilla's Servo Still Going Forth To Parallelize The Web

    It's been a while since hearing anything about Mozilla's Servo Engine that's an experimental browser layout engine that could one day replace the Gecko Engine within Firefox, but there's new development activity going forward and a new update to share today...

    http://www.phoronix.com/vr.php?view=MTYwNzI

  2. #2
    Join Date
    Jul 2013
    Posts
    223

    Default

    Thanks for picking up my tip, Micheal

    The video/slides finally reveal technical info behind Servo, which was sorely missing from any and all initial news posts about it.
    I can't wait for nightly builds to become available, every time I try to compile it myself I get some form of error where it compile fine then just doesn't work haha.

  3. #3
    Join Date
    Dec 2012
    Posts
    38

    Default

    If you want more technical information, there is lively discussion on their mailing list (https://groups.google.com/forum/#!fo...illa.dev.servo), as well as in their IRC channel (irc.mozilla.org, #servo). For some layout tasks, it's already faster than WebKit.
    Last edited by cmr~; 02-18-2014 at 09:18 AM.
    Rust maintainer

  4. #4
    Join Date
    Oct 2011
    Posts
    13

    Default

    Also, I believe Mozilla has some openings on Servo and/or Rust for those that would like to work with research (which is more and more a rarity these days).

    Rust seems to be an awesome language, I can't wait for it to stabilize a bit more (and include a regex engine) so I can do some small, longer-lived projects with it.

  5. #5
    Join Date
    Sep 2010
    Posts
    419

    Default

    Don't forget responsiveness and reaction times, multitithreaded design really is the tool to make an application very responsive.

  6. #6
    Join Date
    Sep 2010
    Posts
    419

    Default

    Will bookmarks handling be done in a separate threat allowing people with thousands to even hundreds of thousands of bookmarks to use the browser fluently, per-formant and responsive?

  7. #7
    Join Date
    Jul 2013
    Posts
    223

    Default

    Quote Originally Posted by plonoma View Post
    Will bookmarks handling be done in a separate threat allowing people with thousands to even hundreds of thousands of bookmarks to use the browser fluently, per-formant and responsive?
    ... What? Bookmarks are just a list of links, with some metadata (names, ICOs, etc). Their "handling" comes down to editing that list. Having thousands of bookmarks shouldn't affect anything but the start time of the browser (as it reads the list)

  8. #8
    Join Date
    Oct 2008
    Posts
    2,904

    Default

    Quote Originally Posted by plonoma View Post
    Will bookmarks handling be done in a separate threat allowing people with thousands to even hundreds of thousands of bookmarks to use the browser fluently, per-formant and responsive?
    Servo is an engine, not a browser. It has no concept of bookmarks, any more than Blink, Webkit, or Gecko do.

  9. #9
    Join Date
    Feb 2008
    Location
    Linuxland
    Posts
    4,722

    Default

    Quote Originally Posted by Daktyl198 View Post
    ... What? Bookmarks are just a list of links, with some metadata (names, ICOs, etc). Their "handling" comes down to editing that list. Having thousands of bookmarks shouldn't affect anything but the start time of the browser (as it reads the list)
    It is clear you have not used Firefox recently with a lot of bookmarks. Such magnificent and wise decisions they were to have it all in SQLite, which consequently fsync()s in the UI thread.

  10. #10
    Join Date
    Oct 2008
    Posts
    2,904

    Default

    Quote Originally Posted by curaga View Post
    It is clear you have not used Firefox recently with a lot of bookmarks. Such magnificent and wise decisions they were to have it all in SQLite, which consequently fsync()s in the UI thread.
    Wasn't all the bookmark/history disk access moved off to a background thread a while back?

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •