10 ms·
Servo Continues Pushing Forward
- gedrap 12y agoIf someone is interested in contributing and not sure where to start, here's a list of issues tagged as easy: https://github.com/servo/servo/labels/E-easy https://github.com/servo/servo/labels/E-easy Not sure if it is still true but a few months back (6 maybe?), there was a post on HN about contributing to Servo where OP said that he found it easy to contribute despite the fact that he didn't have prior experience in rust. As this post mentions, the code base is relatively small and a lot of simple features were still missing, at least back then. Bugs Ahoy is a handy tool for finding easy issues in Mozilla projects but seems to be down at the moment http://www.joshmatthews.net/bugsahoy/?servo=1 http://www.joshmatthews.net/bugsahoy/?servo=1
- natural219 12y agoThank you for this! I'm just not getting acquainted with Servo and starting to get interested. This is a great place to start.
- lastontheboat 12y agoWhoops! I merged a PR earlier today that broke searching Github issues; thanks for pointing that out!
- pikzen 12y agoOP is referring to http://bluishcoder.co.nz/2015/03/24/contributing-to-servo.html http://bluishcoder.co.nz/2015/03/24/contributing-to-servo.ht...
- gedrap 12y agoNope, in the blog post I was referring to the author went to some event (in France, I believe) where some of core contributors helped him, if my memory serves well. Still this is a good post, thanks for linking it!
- kibwen 12y ago> OP said that he found it easy to contribute despite the > fact that he didn't have prior experience in rust Just yesterday I was talking to the person who contributed WebGL support to Servo (a relatively recent and substantial patch), and they reiterated this sentiment. It was their first time ever using Rust, and although they'd reluctantly done some C++ in the past their primary programming language is Javascript. They were pleasantly surprised at how easy it was to contribute such a large patch, and had bountiful praise for how well-organized the codebase is. The patch actually bounced a few times, and they were also very pleased at how the core contributors continued to work with them over the course of days to track down the breakage and keeps things moving. This person's primary interest is in virtual reality, specifically WebVR (http://webvr.info/ http://webvr.info/), and given Servo's incredible benchmarks so far they're very optimistic about its ability to advance the state of the art of virtual reality on the web. Their biggest complaint was build times. Yeah... we're working on that. :)
- rifung 12y agoI guess I'll have to try contributing an easy patch over the weekend. Hopefully it's as easy as you make it sound!
- hyperpape 12y agoWhat is the current goal with Servo? The last time I felt well informed, I think it was described as just a research project, with zero intention to ever supplant Firefox. Is that still the case? There seems to be an awful lot of promise and effort if there's no plans to make it a production ready browser.
- larsberg 12y agoOur official roadmap/goals for Servo are here: https://github.com/servo/servo/wiki/Roadmap https://github.com/servo/servo/wiki/Roadmap So, it's definitely no longer "just a research project," but the challenges of finding initial product targets and building out the rest of the Web Platform are definitely large ones!
- elektronjunge 12y agoAt worst firefox will use some of the libraries that come out of servo. Firefox is supposed to use the url parser from servo by 2016.
- kibwen 12y agoHere's the patch that's tracking adding Servo's Rust-based URL parser to Firefox: https://bugzilla.mozilla.org/show_bug.cgi?id=1151899 https://bugzilla.mozilla.org/show_bug.cgi?id=1151899
- deleted 12y ago[deleted]
- loudmax 12y agoIf Servo becomes the default layout engine for Firefox, I really hope that having one more engine in the mix forces everyone towards standards compliance, or at least uniformity. Obviously, they're still working out basic functionality, so they've got a way to go before that becomes a concern. But if the project is successful, it's going to be one more browser type for web designers to worry about. Either that or Servo's multi-threaded speed and safety are so awesome that all the major browser developers decide to ditch their own engines and everybody settles on Servo.
- larsberg 12y agoOne fun thing about reimplementing the Web Platform is that you run across all of the spec holes (particularly in much older features, like tables, borders, etc.). Where possible, we're trying to at least determine what current browsers do with the intent of codifying those behaviors in the specifications and W3C cross-browser test suite. That said, if Trident/Edge, Webkit/Blink, and Gecko don't all agree on the implementation of an older feature, we know that it will be a challenge to find middle ground and get things changed and the spec updated to anything more than softer statements using, "MAY."
- higherpurpose 12y agoI have a feeling Servo will finally make me give up Chrome. From what I've seen so far the performance is very impressive [1]. I just wonder if Elecrolysis will ever arrive. It seems like I've been waiting for it forever. Chrome's sandboxing is great for security and performance purposes and I can't give that up (I never seem to have a problem switching to another tab even when I have 40 of them open in Chrome, while in Firefox the whole browser "hangs" sometimes when I load a heavy tab). [1] - https://www.phoronix.com/scan.php?page=news_item&px=MTgzNDA https://www.phoronix.com/scan.php?page=news_item&px=MTgzNDA
- simcop2387 12y agoElectrolysis isn't a Servo thing but a Firefox thing. Something that many of us have been waiting for also. From what I've seen with the way Servo works, it should be working in basically the same way from the beginning but I'm not as confident on that as I'd like to be. Since it renders and works on each iframe in another thread and each tab is implemented as an iframe with mozbrowser extensions I would think it should fix that problem.
- Manishearth 12y agoI think he was talking about Firefox. FWIW in Servo when talking of multiprocess stuff we colloquially call it "Electrolysis". I think Patrick has some work in progress on this. It's not as much work as the Firefox e10s (we already use threads and channels for everything), but I think there is some (relatively) minor work to be done.
- zobzu 12y agohow do you handle component sandboxing in Servo compared to firefox e10s? (firefox being child process sandbox, ipc to parent, and things being a little "unperfect" in the separation)
- pcwalton 12y agoThe plan is to use gaol [1] for sandboxing. For IPC, we want to send Rust objects serialized via serde [2] over native OS IPC pipes (AF_UNIX sockets on Unix). [1]: https://github.com/pcwalton/gaol https://github.com/pcwalton/gaol [2]: https://github.com/serde-rs/serde https://github.com/serde-rs/serde
- maxsavin 12y agoI really like how this sounds. I just really hope CSS is implemented with great care and detail. Right now - Firefox and IE has a lot of quirks, and I only find WebKit and Chrome to have it working well. I've been doing CSS intensely for over 5 years, happy to give my feedback along the way.
- nickysielicki 12y agoLast week I tried my hand at putting vim functionality into servo, a la pentadactyl. It's not even close to being ready. Even rendering a simple page like hackernews is broken. That's not to say I am not excited for this. I think servo will be huge and I think it will see widespread adoption. It's just that with all the news we hear about it, you might be lead to think that today it's competing with webkit. It's not. Soon, though.
- rylee 12y agoThank you! I'm glad someone cares about vim functionality enough to work on it.
- vanderZwan 12y agoEvery time I hear about Servo, it mostly can be boiled down to: A: We did a ton of work B: We're not even remotely close to something really useful yet I think that says more about how websites work, to be honest.
- jerf 12y agoThe stack of web technologies is staggeringly enormous. It may not feel like it just scanning over a simple HTML page, but it is, and there's a lot of invisible-yet-critical stuff like proper same-origin policy enforcement. The miracle is not that it takes Servo a while to be created, it's that this stack works at all, and that they're even trying!
- higherpurpose 12y agoCouldn't they just do something similar to Microsoft's Edge/IE11 approach? Servo for HTML5+/CSS3+/Javascript ES6+ and then keep Gecko as well inside Firefox for "legacy websites"?
- adapt_throw 12y agoIf the point is to make a more secure browser, allowing a webpage to opt-in to use the old, less secure engine instead is probably a non-starter. (In any case, I think the complexity is fundamental to many of the specs involved.)
- greggman 12y agoI'm really curious how Servo (and Electrolysis which I know is un-related) are planning to handle the GPU. Most GL drivers if not all of them are not multi-thread happy. Are they implementing an internal command buffer like Chrome or is there some other solution that allows multiple threads and/or multiple processes to all output content to the same window?
- programmer_dude 12y agoI think we will need to wait for Vulkan before we get a true multithreading GL.
- Narishma 12y agoVulkan will not be GL anything.
- programmer_dude 12y agoWhat do you mean?
- kibibu 12y agoIt's 100% an entirely different API. It's not "OpenGL" or "GL" or "GLnext", it's "Vulkan".
- theandrewbailey 12y agoVulkan's codename before reveal was "GLnext". http://www.develop-online.net/news/glnext-revealed-as-vulkan-graphics-api/0203867 http://www.develop-online.net/news/glnext-revealed-as-vulkan...
- dbcooper 12y agoMy uninformed guess is that they will rely on the new multithread friendly systems such as DX12 and the next generation of Open GL.
- VieElm 12y agoAre they planning on implementing a JavaScript engine in Servo as well?
- loudmax 12y agoThe js engine is separate from the rendering engine as far as I know. There might be some exciting new js engines written in Rust, but I don't think they would be part of Servo per se.
- Manishearth 12y agoNo concrete plans for now. JS is complicated, and we don't have enough people to do that. Relying on a JS engine that's currently being used (which we know will get security updates) is much better than rolling our own, for now.
- pcwalton 12y agoIt uses SpiderMonkey.
- rilut 12y agoIf possible, will it be very complicated to use V8? Or is it just impossible?
- pcwalton 12y agoIt's not impossible, but I don't know why you'd want to use V8.
- deleted 12y ago[deleted]
- jomohke 12y agoSpidermonkey compares very well with V8: http://arewefastyet.com/ http://arewefastyet.com/ (beats it in Sunspider, is roughly equal in others) And it maintains the lead in ECMAScript6 support: https://kangax.github.io/compat-table/es6/ https://kangax.github.io/compat-table/es6/
- agumonkey 12y agoI'd love the servo team to show more demos. https://www.youtube.com/watch?v=pZGhnqtXVdc https://www.youtube.com/watch?v=pZGhnqtXVdc
- zobzu 12y agoI compiled and tried servo+servo-shell just now: - it compiles very fast, that's cool - it doesn't render my static pages properly, albeit its not too bad - its slow as hell (i did use --release for build and run) :)
- Jweb_Guru 12y agoIt's definitely not slow at rendering. Network performance isn't great, but try resizing the window.
- elktea 12y agoI've tried it a few times and it's been super slow for me as well. Maybe it's just slow on Linux.
- Manishearth 12y agoYeah, there are some linux issues (forgot what). Also, default build is a debug build. Very slow. Also, we fetch resources serially. It can be done in parallel, but we haven't gotten to that part yet.
- pcwalton 12y agoWhat in particular were you doing?
- mkishi 12y agoIt's slower than Chrome on my 2011 Macbook Air. Which is disappointing, considering it doesn't yet implement the same features.
- buster 12y agoCould servo-shell be used to implement a keyboard driven browser (a la dwb)? Looking at https://developer.mozilla.org/en-US/docs/Web/API/Using_the_Browser_API https://developer.mozilla.org/en-US/docs/Web/API/Using_the_B... it looks like the API does only offer few interaction points with the underlying iframe or shouldn't that be a problem? Can the browser html intercept all key presses and change the iframe content to display follow links, for example? :) That might be a great way to finally have a better keyboard driven solution (since, i think that the browser addons like pentadactyl suck very much).