Dev.SN ♥ developers
Sections
Dev.SN
An anonymous coward writes:
"Mozilla is using work on it's next generation layout engine, Servo, to fine tune a new language used for writing that layout engine. The new language, called Rust, started as a personal project of Greydon Hoare and has since grown to be sponsored by Mozilla and Samsung. From the article:
The Rust language will power Mozilla's new browser, Servo, and its big selling point is efficiency. Because C++ crashes when it runs into memory allocation issues, it weakens any browser that uses the language. Mozilla designed Rust to be superior to C++ this way, more easily isolating tasks and promote a process known as "work stealing," which is when tasks from an overloaded processor are shifted over to another one.
Rust is a general purpose, multi-paradigm, compiled programming language developed by Mozilla Research. It is designed to be a "safe, concurrent, practical language", supporting pure-functional, concurrent-actor, imperative-procedural, and object-oriented styles."
(Score: 1, Informative) by Ethanol-fueled on Saturday March 15 2014, @06:30PM
Speaking of piles, the idea was pretty exciting until I saw how goddamn ugly the language is. Utterly hideous. I haven't seen anything that ugly since SCALA. Even PHP's prettier than RUST.
(Score: 2, Funny) by ticho on Saturday March 15 2014, @06:56PM
But this one comes with a plateful of buzzword soup. Therefore, it can't not be good, ask any PHB!
(Score: 4, Informative) by forsythe on Sunday March 16 2014, @01:23AM
Any language I've seen looked ugly, the first time I saw it. Quite a few still do.
That said, lots of people have found Rust ugly, which probably stems from the way syntax conventions are inspired by very different sources (I've heard Rust described as "What C would look like if it were designed by somebody who had only ever known Haskell"). Ugliness isn't a sin for a language, but it may mean that newcomers to the language will have trouble finding parallels to other languages, and that it will therefore be rather difficult to pick up.
Given that new languages are almost impossible to get adoption for anyway, that's a valid and very harsh criticism of Rust.
(I've been picking it up a little myself over the past few months. As a language with no mandatory GC, it promises to be actually useful for systems programming. Given more time, I think I wouldn't have any more problems with format! and ~ than with C's *.)
(Score: 1) by Hairyfeet on Sunday March 16 2014, @03:41AM
Hey if it gets rid of the "bandaids on bullet wounds" that is JavaScript? Then I don't care if its the ugliest damned thing on the planet YES PLEASE!!!
I mean do you have ANY idea how much the net is slowed down by JavaScript malware? I know at the shop that is pretty much ALL I see anymore is JS malware infections. Hell since Adobe made "update automatically" the default setting for Flash I've been seeing Flash infections go down, not JS though and if you think about it the reason is obvious....it was just never made with security in mind and instead of starting over and doing it right bandaids have just been bolted onto a broken mess.
So if it gets rid of the "Hey we'll just run third party code from anywhere, whats the harm?" of JS and gives us a web language built from the ground up with best practices and least permissions in mind? All for it. Sadly considering that while Webkit had support for Low Rights mode 6 months after Vista came out while Moz has had SEVEN YEARS and still hasn't implemented it in FF? Really doesn't give me much hope of them making anything but a mess, but maybe Google or the Webkit guys can give us something to replace JS..
(Score: 2, Informative) by sjames on Sunday March 16 2014, @04:08AM
Sorry, it won't do that. Rust will be used to write the browser which will, in turn, support Javascript.
I can sure sympathize with your position though. I can and do code in Javascript when it needs to run in the browser, but much of the functionality feels bolted on and then mysteriously restricted to paper over a gaping security hole that resulted from security not really being a priority when the runtime was designed.
It would be nice if Javascript would just implement declared domains of trust and be done with it.
It could use a good syntax cleanup as well.