4 ms·

I for one am pretty decided to move to Firefox once Mozilla integrates Servo into it (granted the performance benefits really are significant). But I'm also wa

I for one am pretty decided to move to Firefox once Mozilla integrates Servo into it (granted the performance benefits really are significant). But I'm also waiting for Mozilla to implement its multi-process sandboxing system. Microsoft seems to be doing some interesting things on that front as well - I hope Mozilla is watching. I like the idea of having each tab in an secured app container, which sounds even better than Chrome's tab-in-a-process system. https://blogs.windows.com/msedgedev/2015/05/11/microsoft-edge-building-a-safer-browser/ https://blogs.windows.com/msedgedev/2015/05/11/microsoft-edg... Of course this will only work on Windows 10, but I don't think that's any reason to wait on implementing such a system (unless it has some major issues I'm not seeing, of course).

callahad 11y ago
> I for one am pretty decided to move to Firefox once Mozilla integrates Servo into it Hooray! I'm excited to have you back. :) If your switch is gated on Servo, you might be in for a long wait: we're moving small, modular components into Firefox as we're able, but completely changing implementation languages for parts of a browser used by hundreds of millions of people is a slow, deliberate process which involves pretty significant changes not only to our codebase, but also to our build infrastructure. Right now the immediate goal is to share either an image decoder or the URL parser between Servo and Firefox. Quite likely by the end of the year. Follow these bugs to find out more when things land: https://bugzil.la/oxidation https://bugzil.la/oxidation, https://bugzil.la/1151899 https://bugzil.la/1151899, https://bugzil.la/1161350 https://bugzil.la/1161350 > I'm also waiting for Mozilla to implement its multi-process sandboxing system I believe we're uplifting multi-process into the Dev Edition 40 release in a week or so. If not, it'll be in 41. Goal is to have it on by default in the release channel by the end of the year: https://wiki.mozilla.org/Electrolysis#Schedule https://wiki.mozilla.org/Electrolysis#Schedule
- magicalist 11y ago
  > Right now the immediate goal is to share either an image decoder or the URL parser between Servo and Firefox Interesting, it seems like there would be an order of magnitude (or more) difference in effort to write these two things. The third link you gave links to mp4parse-rust, is that what you mean by image decoder?
- jumpwah 11y ago
  Are there any plans to build a completely new browser from Servo? Is there even any worth in that? (A firefox-esque "normal" one, not like that experimental html browser thing.)
  - Manishearth 11y ago
    (Servo contributor here) No concrete plans. We hope to get a new mobile browser out. For Desktop we're hopeful about browser.html. As a research project we aren't really worrying about any of this yet. browser.html is intended to be a "normal" browser, though in it's current state it isn't quite there yet :P (It's not pure web HTML, there is a small set of "mozbrowser" APIs which it uses to get sandboxing and the other necessary things) Firefox's UI is anyway written in XUL (an html-esque xml thingy), so browser.html isn't too far from what Firefox does.
    - jumpwah 11y ago
      Thanks for the response. With browser.html, I think I meant functionally, like isn't it supposed to be marketed as a simple, out-of-box, no configuration browser for those who just want no hassle simple web browsing? (Because otherwise I might be confusing it with something else, although I was sure I saw that Mozilla research was doing something like this.) Because if it is, I obviously don't want that... I "just" want a free software html/css/js spec compliant browser (obviously without the drm, or an option without that part, because that's not free software), but the catch is that I sort of need it to be quite customisable... By which I mean something akin to the current firefox, which allows addons, a great powerful addon api, unlike chrome, allows modifying the ui (via userChrome.css), modifying display of web pages themselves (via userContent.css), developer console, setting configuration options via a config file, view page source etc. This seems off-topic and almost like a personal feature request for Servo or whatever, but my point is that I know my "setup" isn't exactly 'mainstream', hence why I basically require powerful customisation options. For example, I'm on firefox (37), but it looks like this: http://i.imgur.com/L9P8XhC.png http://i.imgur.com/L9P8XhC.png. And it's not exactly a whole heap of fragile customisations which are destined to break, it's "just" one userchrome file and one addon, so it's actually fairly reliable too. I care about the ui in that I want the power to change it to what I like. If I can do that, I don't care what the default ui is. But I don't think browser.html's purpose is to be powerful like current firefox is it? I guess normal isn't the right word. If anything, you're right, browser.html is normal, but not in the way I've grown accustomed to with the feature-filled firefox. If you're familiar with zsh and the fish shell, I mentally labelled browser.html as the special "fish shell" of browsers the first time I saw it, hence why I was quick to dismiss it as a future option. I should probably go and embed servo in emacs or something.. :)

callahad 11y ago

> I for one am pretty decided to move to Firefox once Mozilla integrates Servo into it Hooray! I'm excited to have you back. :) If your switch is gated on Servo, you might be in for a long wait: we're moving small, modular components into Firefox as we're able, but completely changing implementation languages for parts of a browser used by hundreds of millions of people is a slow, deliberate process which involves pretty significant changes not only to our codebase, but also to our build infrastructure. Right now the immediate goal is to share either an image decoder or the URL parser between Servo and Firefox. Quite likely by the end of the year. Follow these bugs to find out more when things land: https://bugzil.la/oxidation https://bugzil.la/oxidation, https://bugzil.la/1151899 https://bugzil.la/1151899, https://bugzil.la/1161350 https://bugzil.la/1161350 > I'm also waiting for Mozilla to implement its multi-process sandboxing system I believe we're uplifting multi-process into the Dev Edition 40 release in a week or so. If not, it'll be in 41. Goal is to have it on by default in the release channel by the end of the year: https://wiki.mozilla.org/Electrolysis#Schedule https://wiki.mozilla.org/Electrolysis#Schedule

magicalist 11y ago
> Right now the immediate goal is to share either an image decoder or the URL parser between Servo and Firefox Interesting, it seems like there would be an order of magnitude (or more) difference in effort to write these two things. The third link you gave links to mp4parse-rust, is that what you mean by image decoder?
jumpwah 11y ago
Are there any plans to build a completely new browser from Servo? Is there even any worth in that? (A firefox-esque "normal" one, not like that experimental html browser thing.)
- Manishearth 11y ago
  (Servo contributor here) No concrete plans. We hope to get a new mobile browser out. For Desktop we're hopeful about browser.html. As a research project we aren't really worrying about any of this yet. browser.html is intended to be a "normal" browser, though in it's current state it isn't quite there yet :P (It's not pure web HTML, there is a small set of "mozbrowser" APIs which it uses to get sandboxing and the other necessary things) Firefox's UI is anyway written in XUL (an html-esque xml thingy), so browser.html isn't too far from what Firefox does.
  - jumpwah 11y ago
    Thanks for the response. With browser.html, I think I meant functionally, like isn't it supposed to be marketed as a simple, out-of-box, no configuration browser for those who just want no hassle simple web browsing? (Because otherwise I might be confusing it with something else, although I was sure I saw that Mozilla research was doing something like this.) Because if it is, I obviously don't want that... I "just" want a free software html/css/js spec compliant browser (obviously without the drm, or an option without that part, because that's not free software), but the catch is that I sort of need it to be quite customisable... By which I mean something akin to the current firefox, which allows addons, a great powerful addon api, unlike chrome, allows modifying the ui (via userChrome.css), modifying display of web pages themselves (via userContent.css), developer console, setting configuration options via a config file, view page source etc. This seems off-topic and almost like a personal feature request for Servo or whatever, but my point is that I know my "setup" isn't exactly 'mainstream', hence why I basically require powerful customisation options. For example, I'm on firefox (37), but it looks like this: http://i.imgur.com/L9P8XhC.png http://i.imgur.com/L9P8XhC.png. And it's not exactly a whole heap of fragile customisations which are destined to break, it's "just" one userchrome file and one addon, so it's actually fairly reliable too. I care about the ui in that I want the power to change it to what I like. If I can do that, I don't care what the default ui is. But I don't think browser.html's purpose is to be powerful like current firefox is it? I guess normal isn't the right word. If anything, you're right, browser.html is normal, but not in the way I've grown accustomed to with the feature-filled firefox. If you're familiar with zsh and the fish shell, I mentally labelled browser.html as the special "fish shell" of browsers the first time I saw it, hence why I was quick to dismiss it as a future option. I should probably go and embed servo in emacs or something.. :)