Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Servo Nightly Builds Available

blog.servo.org

Post reply on HN
Print view View original

151–160 of 246 posts

Re: Servo Nightly Builds Available

#151

Post by metajack »

publicfig wrote: post #146
eatonphil wrote: post #119

Just opened up the MacOS build. It is pretty impressive! But the autocomplete is just awful. Typing in " http://localhost:3000" at normal speed produced " http:///localhost:300000" . Especially while it's in such a primitive developer-oriented state it would be much more useful to disable that silly autocomplete. Edit: Additionally, it doesn't yet support native keybindings like Command left-right or Alt left-right.

I doubt that there's going to be much effort into improving the HTML based browser that they're using as a shell to the engine outside of making sure you can go to a specific URL. Things like hotkeys and autocomplete are nice, but not really necessary for developing on Servo. I could be wrong on that though

The browser.html team works on the frontend, so they are very much interested in improving this. You're right that Servo devs themselves often use an even more stripped down test harness that you supply URLs to on the commandline, but that may change now that browser.html has gotten quite nice :)

Re: Servo Nightly Builds Available

#152

Post by metajack »

hitlin37 wrote: post #27

"Servo is a modern, high-performance browser engine being developed for application and embedded use." Is embedded devices one of the goals around Servo? Do Servo have any embedded specific design goals? I'm interested to know which parts in Servo targets to embedded use. I can see that page says Android builds are coming soon. i guess that explains it.

Embedding generally means using it as a part of another application, either as a webview or something like the chromium embedding framework.

However we do have ports for mobile hardware and some embedded hardware, and we think Servo has a lot to offer there. We've done some initial research into battery life stuff that looked really promising, and of course getting parallel speedups is much more noticeable on slower hardware than on desktops.

Re: Servo Nightly Builds Available

#153

Post by cbrewster »

mjs wrote: post #4

The OS X binary isn't signed, and the download URL is HTTP. Is there a version available on a more secure distribution channel anywhere?

The issue with the codesigning is mentioned on download.servo.org, hopefully in the future, we can set up some infrastructure to codesign the app. :)

Re: Servo Nightly Builds Available

#154

Post by metajack »

pimeys wrote: post #50

Is there an article somewhere comparing how Servo and Chromium threaded compositing differ? I guess there is some work on Chromium side to render pages using multiple threads, but I couldn't find more information and how it compares to Servo's mechanism.

We're planning some more in depth blog posts on how Servo works, and this was already one of the topics I wanted to cover.

The gist is that Servo runs most subsystems on separate threads (including sandboxed and cross origin iframes for example), and so each tab or page is not fighting over the same JS engine's time. On top of that, painting/compositing is combined in WebRender and is parallel as well.

Re: Servo Nightly Builds Available

#155

Post by metajack »

a_imho wrote: post #111

not working at all ./runservo (as per instructions) thread 'main' panicked at 'Failed to create window.: OsError("GL context creation failed")', ../src/libcore/result.rs:785 note: Run with `RUST_BACKTRACE=1` for a backtrace. ./servo welcome to servo, than it changes to a white window Debian 8

We've gotten several reports of this, and this is exactly why we wanted to get some wider testing. Hopefully we'll figure this out and get a patch in soon. In the meantime, the suggested workaround will get you going I think at the expense of some rendering performance.

Re: Servo Nightly Builds Available

#156

Post by metajack »

blablabla123 wrote: post #101

How do you actually open the developer console? ;)

If you start servo with the devtools port on, you can use the Firefox tools to get a remote console. This may or may not be working well at the moment. The JS console.log stuff will get output to stdout or stderr when you run as well.

There are discussions underway about how to bring in other tools, and how to get stuff like this into Servo or browser.html itself.

Re: Servo Nightly Builds Available

#157

Post by metajack »

sdeframond wrote: post #46

Is some HiDPI mode already available on Linux?

I don't think we do autodetection yet aside from what Glutin already does (which is very basic). But you can put Servo into a HiDPI mode manually with the --device-pixel-ratio=2.0 argument, and you can supply whatever ratio you like.

We do detect Retina on Mac and have system DPI awareness on Windows, so once we figure out what to do on Linux we can probably add it pretty easily.

Re: Servo Nightly Builds Available

#158

Post by metajack »

chenglou wrote: post #67

Is the scrolling behavior on OS X custom implemented, just like on Firefox? Imo it hits the uncanny valley unfortunately, especially for edge bounce back. Otherwise, excited to try this out more.

I think the browser.html team will be very interested in this feedback. I sat with them as they poured over Cocoa disassembly and source trying to replicate the behavior as best they could. We definitely have some things to improve. Because we are using our own rendering system to draw on the GPU, we can't use Apple's implementation of this stuff which requires buying into Core Graphics/Core Animation completely I believe.

Note that I don't think Firefox has overscroll at all, except maybe on mobile.

Re: Servo Nightly Builds Available

#159

Post by nickpsecurity »

metajack wrote: post #139
pilif wrote: post #81

It's amazing to see actual effort taking place to build a new browser engine from scratch. I would say that since the late 90ies, there hasn't been a single new engine being made. Everything we have now is a development based on KHTML, Gecko, Presto or Trident. By now, HTML and the standards surrounding it have become so big that starting from a blank slate nowadays is next to impossible. The existing engines have it…

> By now, HTML and the standards surrounding it have become so big that starting from a blank slate nowadays is next to impossible. One important mitigating factor is that newer standards often generalize older ones. For example, originally all the list elements had special case handling (and still might in other engines), but now it's possible to do all that with the user agent style sheet with new additions to CSS…

This has been interesting test. Thanks for your suggestion on the -c option for "can't load servo." That worked. Filed a bug on HN login where tab autosubmits form instead of changes textbox. I can neither see the text I'm typing nor scroll down on HN. I'll check to see if open issues on that then file them if there aren't.

Re: Servo Nightly Builds Available

#160

Post by coldtea »

pilif wrote: post #81

It's amazing to see actual effort taking place to build a new browser engine from scratch. I would say that since the late 90ies, there hasn't been a single new engine being made. Everything we have now is a development based on KHTML, Gecko, Presto or Trident. By now, HTML and the standards surrounding it have become so big that starting from a blank slate nowadays is next to impossible. The existing engines have it…

>I would say that since the late 90ies, there hasn't been a single new engine being made. Everything we have now is a development based on KHTML, Gecko, Presto or Trident.

Compared to KHTML, Webkit and Blink were pretty much 5 or more whole new projects on top of it. And even the latest IE is hugely rewritten compared to Trident.

Post reply on HN