Live data from Hacker News

Servo Nightly Builds Available

blog.servo.org

101–110 of 246 posts

Re: Servo Nightly Builds Available

#103
post #29

Earlier quoted context omitted.

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.

ah....the description is ambiguous then. Embed a browser in another application isn't very clear either. Is Servo like framework where devs can build apps on top (something on electron line).

Or is it really about embedding browser inside your application. That one can do today with QT framework where you can embed a browser inside your application. But QT itself moved from Qt WebKit to Qt WebEngine. So, 'embed a browser' in your application sounds old to me.

Re: Servo Nightly Builds Available

#104

Earlier quoted context omitted.

> By now, HTML and the standards surrounding it have become so big that starting from a blank slate nowadays is next to impossible. It's a two sided coin: HTML now defines a lot of the basic web platform parts in enough detail that you can just implement the spec and have a web browser that works , whereas in the 90s (and most of the 00s) browsers spent huge amounts of resources on reverse-engineering each other. Pre…

Well, we still do lots of reverse-engineering, because the specs are often wrong :)

A lot is relative. :)

Honestly, from what I see, the amount you do is relatively minuscule compared with what Opera was doing ten years ago, while Opera had far more marketshare which is normally the best way to avoid web compat issues in the first place.

Re: Servo Nightly Builds Available

#105
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?

aa

Re: Servo Nightly Builds Available

#106
post #91

Earlier quoted context omitted.

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

To clarify, a panic in rust is the result of an unhandled exception. Usually this is due to laziness rather than a real bug. For example Servo might encounter an IMG tag, start to load the body. The result might be stored in an option because something could have gone wrong during loading (peer disconnected etc.) but the developer didn't feel like implementing robust image handling that day and instead called .expect…

And importantly, a panic is not a result of a memory safety bug, and those are the crashes (with their potential security risks) that Rust is aiming to get rid of.

Re: Servo Nightly Builds Available

#107
post #68
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?

The Windows version is not availiable because mozjs the JavaScript engine, Or say, SpiderMonkey, fails to compile on windows currently, and servo developers can not know when it will be fixed. Once it can be build on windows, windows version may come out soon.

Re: Servo Nightly Builds Available

#108
post #77

Earlier quoted context omitted.

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…

>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 That sounds too precise to be just an example :) We've all been there!

Haha, yes, this kind of thing has bitten me a few times. I remember getting SVN really confused where the server thought files were different but my machine thought they were the same (or similar). I think I had to make a whole new repo.

It's now on my mental list for "but it works on my machine", checking filenames and their cases.

Re: Servo Nightly Builds Available

#109
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…

ass

Re: Servo Nightly Builds Available

#110
post #86

Earlier quoted context omitted.

browser.html is just the browser chrome (er, not to be confused with the browser Chrome), it's an independent Mozilla project to create a frontend entirely in web technologies, which, since these are all standardized, should theoretically work with any browser engine, not just Servo. As for Firefox, later on this year we should see the integration of Servo's style engine ("Stylo") into Gecko, and going forward we sho…

> 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?
Post reply on HN