Earlier quoted context omitted.
Right-click -> Open, Confirm. Not really involved.
It's not involved, but it's also not obvious to many users.
Fairly sure that's by design.
Servo Nightly Builds Available
241–246 of 246 posts
Re: Servo Nightly Builds Available
#242Earlier quoted context omitted.
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…
I do things like this all the time in Haskell when quickly prototyping new code and then swiftly kick myself because of it. Safe languages are nice, but there's really no way to prevent a developer from saying "Yeah fuck it, this case will never happen anyway" and then calling a fromJust on a Maybe monad which turns out was a Nothing and throws a runtime exception.
Well, there is a way: Don't allow partial functions like fromJust or head. But a) it's going to make prototyping so tedious that no one will bother using this hypothetical language, and b) there are problems that you just cannot solve without partial functions (e.g. foldl1).
Re: Servo Nightly Builds Available
#243Earlier quoted context omitted.
Does anyone know if Servo has any unsafe Rust code?
Yes, quite a bit of it: https://github.com/servo/servo/search?l=rust&q=unsafe
Any reasonably large program will have at least some amounts of unsafe code. And that's not a big deal. The point of Rust is to very clearly isolate the unsafe parts, so that you only need to audit 1% or less for memory safety.
Re: Servo Nightly Builds Available
#244Looking forward to using Servo one day, keep up the good work. First thing I noticed almost immediately after launching is that everything breaks when dragging the window across monitors (that have different densities) - OS X. I dragged from my Macbook's display to an external monitor with a lower DPI and everything went huge and most of the UI got cut off. Dragging back to the Macbook display does not resolve the is…
you misunderstand if you think servo is scheduled for production and put peer pressure on the devs, but sure, firefox is great already, can only get better. Speaking of which, how are the memory requirements of servo, in relative terms, yet?
Re: Servo Nightly Builds Available
#245Looking forward to using Servo one day, keep up the good work. First thing I noticed almost immediately after launching is that everything breaks when dragging the window across monitors (that have different densities) - OS X. I dragged from my Macbook's display to an external monitor with a lower DPI and everything went huge and most of the UI got cut off. Dragging back to the Macbook display does not resolve the is…
you misunderstand if you think servo is scheduled for production and put peer pressure on the devs, but sure, firefox is great already, can only get better. Speaking of which, how are the memory requirements of servo, in relative terms, yet?
I don't know what you think you inferred, but please reread my comment carefully. I meant exactly what I wrote and nothing beyond that.
Re: Servo Nightly Builds Available
#246not 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.
This worked for me on Ubuntu 15.10 x64