Live data from Hacker News

One year of Rust

blog.rust-lang.org

21–30 of 110 posts

Re: One year of Rust

#21
post #8
post #4

Earlier 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.

A big pain is still JIT compilation. Last time I used rust, even small changes to code required a full re-compilation.

Re: One year of Rust

#22
post #21
post #8

Earlier quoted context omitted.

I'd say the tooling is pretty great only with the exception of an IDE. Debugging, building, testing, packaging all seems pretty well handled.

A big pain is still JIT compilation. Last time I used rust, even small changes to code required a full re-compilation.

To be clear: Rust doesn't have a JIT. But we've been doing a lot of work on incremental recompilation, which will fix this problem. (Or rather, we've been working on the precursor requirement, MIR.)

To be extra clear, a crate is the unit of compilation in Rust, so changing your code means that the whole crate it's in needs recompiled; your dependencies won't be. Or, if your project is split up into multiple crates, the other ones won't. Incremental recompilation will reduce this level of granularity such that the whole crate won't need to be recompiled.

Re: One year of Rust

#23
post #20

Earlier quoted context omitted.

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.

That's gotten much better since 1.0. Prior to 1.0, you needed to revise your Rust program about once a week so it would compile. Now the language has settled, but the libraries are still churning. One of the big advantages of Go is that it comes with a coherent set of libraries from a single source (Google) that do most of the things you'd want to do on a server. Rust is more like Python; many people write libraries,…

The advantages of having a distributed ecosystem vs. having a monolithic standard library is an extremely polarized topic, and I don't want to start that debate.

But I do want to emphasize that Rust libraries follow semver, and the lock features of Cargo mean that your builds are always reproducible and you upgrade only when you want to. Your code will never stop compiling one day just because some library "churned".

Re: One year of Rust

#24
post #10
post #4

Earlier 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.

Couldn't agree more! There's some work ongoing on a third party Rust plugin for InteliJ but it still has a long way to come.

Re: One year of Rust

#25
post #21
post #8

Earlier quoted context omitted.

I'd say the tooling is pretty great only with the exception of an IDE. Debugging, building, testing, packaging all seems pretty well handled.

A big pain is still JIT compilation. Last time I used rust, even small changes to code required a full re-compilation.

Are you sure you mean JIT rather than incremental compilation? The former is a pretty different concept that AFAIK Rust has no implementation of.

I think we are likely to see better incremental support with the recent development of MIR, but I'm not sure what the current plans are. Should help tooling around the language generally!

Re: One year of Rust

#26
post #4
post #2

One 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.

Not as great as a full IDE, but Atom.io + tokamak(https://vertexclique.github.io/tokamak) + atom-ctags(https://atom.io/packages/atom-ctags) get you a decent editor/light IDE setup.

I agree however that it would be nice to have ie lifetimes visualized and stuff like that, hopefully sometime soon...

Re: One year of Rust

#27
post #4
post #2

One 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.

> Except the tooling, could be better. A language like Rust will benefit from a rich IDE a lot.

I just found this link[1] for a pretty complete Emacs IDE-like setup the other day. I'm not a Rust programmer, but it seemed promising enough that it made me want to give it a spin.

[1] http://julienblanchard.com/2016/fancy-rust-development-with-...

Re: One year of Rust

#30
post #4
post #2

One 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.

I'm not into IDEs, so that doesn't bother me. But by tooling I'd understand cargo. It is improving.
Post reply on HN