Earlier quoted context omitted.
Rust has been in development for almost a decade at this point; but the language changed significantly many times before 1.0. It's been one year since the 1.0 release, which is the language we know today as "Rust". All those older languages are dead and gone now. I'm actually doing a talk about the ACM's Applicative conference in NYC this year talking about the history of Rust.
This is one thing that's a little annoying to me. I know if I develop a Rust app today I can't leave it alone or it will decay horribly.
One year of Rust
31–40 of 110 posts
Re: One year of Rust
#32Earlier quoted context omitted.
Except the tooling, could be better. A language like Rust will benefit from a rich IDE a lot. But still the language is great.
I really wish that Jetbrains had a Rust IDE. I love their Go, and Erlang plugins for IntelliJ, Java with IntelliJ, and Clion with C. Without them, I don't think I could be anywhere as effective as I am. I tried to pickup Rust, but I was super frustrated by the code/compile/run cycle with the current plugin. But, hopefully more users will make that better.
Re: One year of Rust
#33Hey HN, do you knoe Any notable projects or startups using Rust? Web, desktop apps, scientific or algorithmic computing etc?
https://github.com/servo/servo
It is a massive undertaking and it's already sort of working in many regards.
Re: One year of Rust
#34One year since stable? It feels like five years for the level of maturity they have achieved.
Except the tooling, could be better. A language like Rust will benefit from a rich IDE a lot. But still the language is great.
Re: One year of Rust
#35One year since stable? It feels like five years for the level of maturity they have achieved.
Except the tooling, could be better. A language like Rust will benefit from a rich IDE a lot. But still the language is great.
Re: One year of Rust
#36Hey HN, do you knoe Any notable projects or startups using Rust? Web, desktop apps, scientific or algorithmic computing etc?
Re: One year of Rust
#37One year since stable? It feels like five years for the level of maturity they have achieved.
Except the tooling, could be better. A language like Rust will benefit from a rich IDE a lot. But still the language is great.
It is a really big barrier to adoption because it's very hard to find out what functionality is or is not offered. Here's an example: I want to iterate over a set. Easy, right?
No.
http://static.rust-lang.org/doc/master/std/collections/hash_...
Look at the signature for Cycle. It's really hard to know what this does even though it's trivial:
fn cycle(self) -> Cycle where Self: Clone
When you click through to the real documentation, it describes a useful use case for this. But that's not how programmers think. They think "I need to do X right now so I'll find something that looks right" not "I'm going to click through the documentation... oh X looks interesting I'll remember that later". There's no way to infer what Cycle really does without having actually clicked through or used it.
Re: One year of Rust
#38Earlier quoted context omitted.
Except the tooling, could be better. A language like Rust will benefit from a rich IDE a lot. But still the language is great.
I'd say rustdoc is pretty rough. It's very hard to navigate the rust stdlib vs, say, Go, and when you do find what you want, it's often specified in some very cryptic manner that seems to require a PL PhD. It is a really big barrier to adoption because it's very hard to find out what functionality is or is not offered. Here's an example: I want to iterate over a set. Easy, right? No. http://static.rust-lang.org/doc/m…
Re: One year of Rust
#39Earlier quoted context omitted.
Except the tooling, could be better. A language like Rust will benefit from a rich IDE a lot. But still the language is great.
I really wish that Jetbrains had a Rust IDE. I love their Go, and Erlang plugins for IntelliJ, Java with IntelliJ, and Clion with C. Without them, I don't think I could be anywhere as effective as I am. I tried to pickup Rust, but I was super frustrated by the code/compile/run cycle with the current plugin. But, hopefully more users will make that better.
Re: One year of Rust
#40Earlier quoted context omitted.
Except the tooling, could be better. A language like Rust will benefit from a rich IDE a lot. But still the language is great.
I'd say the tooling is pretty great only with the exception of an IDE. Debugging, building, testing, packaging all seems pretty well handled.
Eh, debugging is a mess, at least on OS X. Rust advertises LLDB support, but it seems semi-broken. Listing source is non-functional and just setting a break-point requires a lot of hand-holding.