News for hackers. Stuff that matters.
Re:The JVM situation by pshc on Tuesday June 18, 2013 @08:24PM (#5902919)
Rust is the anti-JVM.

- Proper task isolation with pointer ownership.

- No global GC. Task-local GC when needed, and explicit ownership otherwise.

- Mozilla.

- No NullPointerExceptions. Unsafe code is convenient when you need it.

Re:The JVM situation by jacques_chester on Tuesday June 18, 2013 @08:52PM (#5903024)
I personally am really excited by Rust, but it's also still a fairly fast-moving target. Lots of work is still being done on the semantics of the language.

It's an industrial research project, basically. When the semantics stabilise I reckon it'll be a technical winner in its chosen domain.

Re:The JVM situation by jmgrosen on Tuesday June 18, 2013 @09:05PM (#5903086)
Yes, certainly -- it's annoying to be working on some code, then update to a day-newer compiler and suddenly have a screen full of errors (as is currently the case).

But in the long run, it'll be worth it, and I have no doubt that Rust will become an amazing language worth using.

Re:The JVM situation by azth on Wednesday June 19, 2013 @12:16AM (#5903716)
And now you can browse Wikipedia in Servo (which is written in Rust): https://twitter.com/metajack/status/346822553089761281/photo...
Re:The JVM situation by jacques_chester on Wednesday June 19, 2013 @01:43AM (#5903894)
Servo is a good idea because it helps show the pain points of Rust on a real world project. But it doesn't show that Rust is ready for general use yet because that's really what it is -- another facet of the Rust project.
Re:The JVM situation by azth on Wednesday June 19, 2013 @04:24PM (#5907945)
True. It is nice; however, to see a big project being developed side-by-side with the language.
Re:The JVM situation by jacques_chester on Wednesday June 19, 2013 @09:45PM (#5909676)
Absolutely. The obvious historical parallel is the co-evolution of Unix and C.