331–338 of 338 posts
Earlier quoted context omitted.
What, pray tell, do you think the "L" in "DSL" represents?
Same as "L" in "HTML". Does that make XML a programming language? My point is - DSL and programming language can overlap. However they don't have to.
I believe that's Amazon, Microsoft and Facebook all looking to get involved in core Rust development (I think partially triggered by the Mozilla layoffs). If anybody was still harbouring doubts about Rust's future, now is the time to lay them aside.
I believe that's Amazon, Microsoft and Facebook all looking to get involved in core Rust development (I think partially triggered by the Mozilla layoffs). If anybody was still harbouring doubts about Rust's future, now is the time to lay them aside.
This meme really needs to die. Mozilla never stopped working on Rust, many of the core developers are still Mozilla employees, and the Firefox team hasn't stopped adding Rust-based components.
(Well, Firefox adding more Rust is correct, but the rest is not.)
Earlier quoted context omitted.
The learning curve is very, very steep. Worth it, in my opinion. I think, though, you can become productive in Rust after a week or two. Go is great because you can grok it after a couple of days - you'll have most of the main concepts of the language down pretty well. I feel like I'm able to "bend the spoon" every day when I sit down to write Go, and I've only just barely been writing it for a year. Rust? I haven't…
Thanks! Why is it worth it, in your opinion?
If they really want to help, the most obvious first step would seem to be to formally adopt and throw some full-time resources at the Rusoto AWS library set for Rust. It's pretty usable right now, but would certainly benefit from the level of testing, helper methods, and language-specific additions that the officially supported AWS libs have.
> If they really want to help, the most obvious first step would seem to be to formally adopt and throw some full-time resources at the Rusoto AWS library set for Rust. Is it really? Seems to me like that would easily be seen as self-serving, while putting efforts into the ecosystem as a whole means even people who don't care a whit for AWS benefit.
Earlier quoted context omitted.
Coffeescript also won a lot of mindshare, the point is keeping it for decades.
Coffee Script is a transpiled language and it has become irrelevant when lot of the language features it offered is now natively available in ES6 and up (it has definitely inspired lot of ES6 features like fat arrow functions). Rust on the other hand is not a thin layer on top of something like Coffee script. So it does not need to keep up with 'something' for decades. As long as it continues to do its current job of…