Live data from Hacker News

Rust's 2017 Roadmap

blog.rust-lang.org

271–274 of 274 posts

Re: Rust's 2017 Roadmap

#271
post #252

Earlier quoted context omitted.

I don't quite follow the question and/or implication.

Nostrademons said "for programmers that can use GC, there are already very good solutions out there", which I understood to mean "the advantages of most ML-family languages over other languages that require GC are smaller than the advantages of Rust over other languages that do not require GC". Which I was questioning.

I wasn't thinking specifically of ML-family languages, though they could be included.

Rather, if you are in a problem domain like web-development or server-side microservices where a GC is fine, there are lots of decent options for programming languages. Python, Ruby, or PHP. Go. Any of the JVM languages - Java, Scala, Clojure, Kotlin. Swift or Objective-C. dot-NET. Many of these have had continuous attention over the last twenty years, they've got major corporate backers, and so a lot of the recent research in PL theory gets ported over to them.

If you are in a problem domain where you can't use GC - like computer graphics, games, databases, information retrieval, operating systems, or embedded - you have basically one option. C++. C++ has gotten a much-welcome facelift recently with C++11/14/17, but the core of the language is still 40 years old, and the language as a whole makes serious compromises (like memory safety) for backwards-compatibility. The excitement about Rust largely stems from its competition being C++; if you pit Rust against say Python or ES6 in the domains in which the latter are used, it's very much "Why would I use this?"

Re: Rust's 2017 Roadmap

#272
I'm really on board with this roadmap. I'm actually quite impress to see a language publish such a clear direction, they have really good focus, and if they keep this focus year over year, Rust will become a really great language.

Re: Rust's 2017 Roadmap

#273

Earlier quoted context omitted.

Could you provide an example where the borrowing would cause issues for immutable data? I'm still learning Rust, but I thought the fact that you could have as many immutable borrows as possible would limit what errors the borrow checker could throw at you.

This is embarrassing, but I'm now second-guessing whether what I wrote was accurate. Sorry. In penance, here are some links: https://www.reddit.com/r/rust/comments/5ny09j/tips_to_not_fi... https://m-decoster.github.io//2017/01/16/fighting-borrowchk/

Fantastic! Thanks a lot in any case.

I do find the image of "fighting the borrow checker" is quite harmful to how people view Rust. As those links state, an important aspect of teaching Rust is educating people about why the borrow checker complains, so that they might adjust their mental model.

Re: Rust's 2017 Roadmap

#274
post #170

Earlier quoted context omitted.

> Can you tell me what it means to search for 'line' or 'lines' in rustdoc? Rustdoc has a search bar at the top. with 'line' it's the third result, 'lines' is the first https://doc.rust-lang.org/stable/std/?search=lines and the short description makes it clear that the first two results are irrelevant in this case. > It would be great to have an offline way to search Rust documentation and examples, It all works offl…

> Rustdoc has a search bar at the top. Let me assure you that I mean only the best for this language and I appreciate your persistent willingness to help, but I want to help debug your use of internal terminology that doesn't help beginners. "rustdoc" is not how you should be telling beginners to look for documentation. As far as I can tell, "rustdoc" is the tool for generating documentation, not searching it. I assu…

o/ waves

Please make sure to leave a comment and/or downvote any answers that are wrong to help people coming after you. I also apologize for whichever specific way I harmed you.

Post reply on HN