Live data from Hacker News

Servo Nightly Builds Available

blog.servo.org

111–120 of 246 posts

Re: Servo Nightly Builds Available

#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

Re: Servo Nightly Builds Available

#113

It's definitely slower to actually load pages — I'm guessing that there are still a lot of network optimizations that more mature codebases have accrued that Servo hasn't yet — but holy cow are pages buttery smooth once they do load (and even while they're loading, which is unusual). Comparing Chrome and Servo in terms of UI jank felt pretty shocking, in Servo's favor. Kudos, it looks like Rust and WebRender have pai…

Yeah; we've mostly ignored the network stack. So there's some extra copying in the IPC, and no speculative parsing, which can slow things down, among other factors. Can be fixed, but priorities :)

I will absolutely love to contribute toward the network stack. Can you provide me any pointers?

Re: Servo Nightly Builds Available

#114
post #110

Earlier quoted context omitted.

> theoretically work with any browser engine, not just Servo. Well, it depends on some privileged APIs, of course. But we've tried to keep that API surface minimal.

Ah I wasn't aware of that, what do these priveliged APIs do?

Things like history management. While tabs in browser.html are just iframes, browser.html needs more access to the contained documents to be able to fully do its job. For security reasons, you can't get at an iframe's current location/title/favicon if the loaded document is from another domain. We need this information to show a proper title in the title bar and the tabs list, and to show a back button and things like that.

In addition, the browser needs to act as a sort of broker between sites and the OS. Storing cookies and session data, showing notifications or dialogs, and entering fullscreen mode are just a few examples of this. (Note that most of these things aren't even implemented yet. Browsers are complex applications in their own right, even after accounting for the browser engine.)

Re: Servo Nightly Builds Available

#115
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

Most likely this is due to your system only supporting OpenGL version < 3.0. I had the same problem. Replacing '-w' by '-c' in the 'runservo' script might fix your startup problem.

Re: Servo Nightly Builds Available

#116

Earlier quoted context omitted.

Yeah; we've mostly ignored the network stack. So there's some extra copying in the IPC, and no speculative parsing, which can slow things down, among other factors. Can be fixed, but priorities :)

I will absolutely love to contribute toward the network stack. Can you provide me any pointers?

Using pointers in rust is discouraged!

Re: Servo Nightly Builds Available

#117

Earlier quoted context omitted.

The last few releases of OSX don't allow you to launch unsigned binaries without specifically disabling the check. In the latest Sierra beta I've heard you can't disable the check without an involved workaround. It's just OSX users being lazy ;)

Right-click -> Open, Confirm. Not really involved.

It's not involved, but it's also not obvious to many users.

Re: Servo Nightly Builds Available

#118
post #110

Earlier quoted context omitted.

> theoretically work with any browser engine, not just Servo. Well, it depends on some privileged APIs, of course. But we've tried to keep that API surface minimal.

Ah I wasn't aware of that, what do these priveliged APIs do?

Punch through CORS like it's a sheet of paper, for example.

Re: Servo Nightly Builds Available

#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.

Re: Servo Nightly Builds Available

#120

Earlier quoted context omitted.

Yeah; we've mostly ignored the network stack. So there's some extra copying in the IPC, and no speculative parsing, which can slow things down, among other factors. Can be fixed, but priorities :)

I will absolutely love to contribute toward the network stack. Can you provide me any pointers?

We have http://starters.servo.org/, though there may not be network stack bugs right now.

I have some more involved projects planned for the network stack that aren't yet ready to be picked up though. I suggest working on some bugs above, getting familiar, and then asking in IRC for something in the network stack.

Post reply on HN