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

71–80 of 246 posts

Re: Servo Nightly Builds Available

#71

Post by mintplant »

cmrx64 wrote: post #29
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.

Embedded in the sense that you embed a browser in another application, I think? Maybe IVE (in-vehicle entertainment).

> Embedded in the sense that you embed a browser in another application

Yes, this is it.

Re: Servo Nightly Builds Available

#72

Post by _jezell_ »

Lukas_Skywalker wrote: post #70
Manishearth wrote: post #58

Earlier quoted context omitted.

Fixed: https://github.com/servo/servo/pull/12003 There's a more serious error in the url parsing that caused this, due to some wierd stuff google is doing with punycode. I haven't looked into that yet. But youtube no longer crashes -- so you can now enjoy window-shopping on youtube!

Daaaamn that was fast. Keep up the good work!

Fix for parser https://github.com/servo/rust-url/pull/208

Re: Servo Nightly Builds Available

#73

Post by Manishearth »

legulere wrote: post #49

It's already more nice than what I expected. Some really minor bugs that occurred while using it a bit (OS X 10.11): - Scrolling when already at the end of the page sometimes makes a relatively big instant step (noticed this for instance on the hackernews startpage) - The tabs aren't cropped in tab view: http://imgur.com/Q1Bxibo - Tabs don't keep at which point you have scrolled when switching tabs - After opening th…

Could you file issues for all of these (preferably with secreenshots)?

Thanks!

Re: Servo Nightly Builds Available

#74

Post by pekk »

pcwalton wrote: post #2

Happy to answer questions (when I wake up; getting this ready has been a lot of work, needless to say) :) It goes without saying, but as this is the very first nightly (not by any means a full-fledged release), expect severe bugs, crashes, and missing functionality. Many of your favorite sites will be broken. Don't expect to use this as your everyday browser. We'd love feedback on what issues folks hit the most, so w…

> expect severe bugs, crashes, and missing functionality.

I really don't mean this in a snarky way: wasn't this kind of thing supposed to be obviated by the switch to Rust? It often seems that every other post about Rust on HN says that if it compiles, it works.

Re: Servo Nightly Builds Available

#75

Post by [deleted] »

po1nter wrote: post #68
pcwalton wrote: post #2

Happy to answer questions (when I wake up; getting this ready has been a lot of work, needless to say) :) It goes without saying, but as this is the very first nightly (not by any means a full-fledged release), expect severe bugs, crashes, and missing functionality. Many of your favorite sites will be broken. Don't expect to use this as your everyday browser. We'd love feedback on what issues folks hit the most, so w…

Do you have an ETA for when the Windows version might be available for us to try?

[deleted]

Re: Servo Nightly Builds Available

#76

Post by reissbaker »

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 paid off.

Looking forward to seeing this evolve.

Re: Servo Nightly Builds Available

#77

Post by IanCal »

pekk wrote: post #74
pcwalton wrote: post #2

Happy to answer questions (when I wake up; getting this ready has been a lot of work, needless to say) :) It goes without saying, but as this is the very first nightly (not by any means a full-fledged release), expect severe bugs, crashes, and missing functionality. Many of your favorite sites will be broken. Don't expect to use this as your everyday browser. We'd love feedback on what issues folks hit the most, so w…

> expect severe bugs, crashes, and missing functionality. I really don't mean this in a snarky way: wasn't this kind of thing supposed to be obviated by the switch to Rust? It often seems that every other post about Rust on HN says that if it compiles, it works.

No language can fix missing functionality, that seems pretty clear.

Your compiler doesn't know what you're trying to do, so you can't prevent all bugs.

That leaves crashes, and ... well it may also depend on what you mean by a crash. The UI becomes unresponsive? Might have absolutely nothing to do with memory issues or even code written in rust. Maybe your rust code is fine but you're trying to open and write to the same file from two places which you don't realise because the users file system is case insensitive but you've only tested on a case sensitive one, etc.

It's also multi-threaded and while languages can significantly help improve the safety of multi-threaded code, I don't think anything can stop you from creating a deadlock or putting your system into an inconsistent state.

And finally, they may not even particularly expect those things, but putting out early nightly builds to a wider audience and expecting nothing to go wrong would be cavalier. A typical warning on many early releases is "don't blame me if this destroys all your files".

Re: Servo Nightly Builds Available

#78

Post by epidemian »

pcwalton wrote: post #2

Happy to answer questions (when I wake up; getting this ready has been a lot of work, needless to say) :) It goes without saying, but as this is the very first nightly (not by any means a full-fledged release), expect severe bugs, crashes, and missing functionality. Many of your favorite sites will be broken. Don't expect to use this as your everyday browser. We'd love feedback on what issues folks hit the most, so w…

Kudos on this milestone!

A very general question: what's the high-level plan for Servo regarding Firefox? I see a lot of requests/issues dealing with stuff that doesn't seem related to a layout engine. Is the plan to have browser.html as a temporary incubator for Servo and eventually migrate it to replace FF's layout engine, or is it to "grow" an entire new browser around this new engine?

Re: Servo Nightly Builds Available

#79

Post by Manishearth »

IanCal wrote: post #77
pekk wrote: post #74

Earlier quoted context omitted.

> expect severe bugs, crashes, and missing functionality. I really don't mean this in a snarky way: wasn't this kind of thing supposed to be obviated by the switch to Rust? It often seems that every other post about Rust on HN says that if it compiles, it works.

No language can fix missing functionality, that seems pretty clear. Your compiler doesn't know what you're trying to do, so you can't prevent all bugs. That leaves crashes, and ... well it may also depend on what you mean by a crash. The UI becomes unresponsive? Might have absolutely nothing to do with memory issues or even code written in rust. Maybe your rust code is fine but you're trying to open and write to the…

By crashes we mean panics. We still panic in various places in the code when something goes wrong.

Re: Servo Nightly Builds Available

#80

Post by Manishearth »

reissbaker wrote: post #76

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 :)

Post reply on HN