Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Rust's 2017 Roadmap

blog.rust-lang.org

Post reply on HN
Print view View original

31–40 of 274 posts

Re: Rust's 2017 Roadmap

#31

Post by steveklabnik »

ainar-g wrote: post #26

Does the "lower learning curve" goal include the lowering of learning curve for people who already know how to program? Because right now, the Book sometimes seems like it's aimed for people who either didn't program a lot, or didn't program in a language with types. What I actually would like is a few "Books" like "Rust for C++ people", "Rust for Go people", etc. Those would describe in many examples how things that…

You will probably like the O' Reilly book. It's a bit closer to "Rust for C++ people", IMHO.

I fully agree that more of this kind of thing would be great.

Re: Rust's 2017 Roadmap

#32

Post by kzrdude »

steveklabnik wrote: post #5
DeepYogurt wrote: post #3

Don't change the language to make it easier (unless that can be a free lunch), but get someone doing a "Today in rust" or "Doing X in rust" blog/vlog. Also please get some sort of RNG into the main language (not as a crate).

What advantage would putting an RNG into the language do? Are there any languages where an RNG is a language construct?

Relieve crates of version coupling stress. I effectively can't release an 1.0 crate if I have rand as a public dependency; if it has a new major version, I need to have that too to keep in sync and do versioning right.

Rand is a vocabulary crate (traits Rng and Rand are used for inter-crate exchange), so it's very sensitive to version coupling.

Re: Rust's 2017 Roadmap

#33

Post by leshow »

adamnemecek wrote: post #13

> Plans include a new book, You should consider publishing an official, printed book. I would totally pay $30-40 for something like this. And once it's already written, the actual publishing shouldn't be too time consuming (but idk lol). I think that there's a lot of people who'd buy it just to support the project. On one hand, I do have environmental concerns, but on the other hand, I feel like my retention rate wit…

Oreilly has an early release available: http://shop.oreilly.com/product/0636920040385.do

I have purchased it and it's pretty good. Although it really seems to be geared more towards experienced systems programmers. The online book is much better for beginners, IMO.

Re: Rust's 2017 Roadmap

#34

Post by davidtgoldblatt »

Manishearth wrote: post #7
steveklabnik wrote: post #5

Earlier quoted context omitted.

What advantage would putting an RNG into the language do? Are there any languages where an RNG is a language construct?

I think they mean stdlib. RNG is not in the language for any language I can think of.

It's part of the core language semantics (arguably the core language semantics) for Java2K (http://p-nand-q.com/programming/languages/java2k/).

Re: Rust's 2017 Roadmap

#35

Post by Manishearth »

XorNot wrote: post #14
Manishearth wrote: post #6

Earlier quoted context omitted.

Any particular reason rng must be in the stdlib? It's an "official" crate, maintained by the Rust developers. In general Rust tries to keep things out of its stdlib instead opting for crates. It lets these evolve independently of the stdlib (not tied to rustc releases), and also lets them have their own versioning (none of that urllib2 urllib3 nonsense)

I would say random numbers are a fairly core programming construct for a standard library. They're important, difficult to get right, and have huge implications if you get them wrong.

This doesn't answer my question, though. Most of the "fairly core programming constructs" are not in the stdlib for Rust (like regexes)

The Rust stdlib is mostly core abstractions and platform-dependent stuff.

Given that, why should they be in the stdlib? The rand crate is officially blessed and the one everyone uses.

Re: Rust's 2017 Roadmap

#36

Post by [deleted] »

adamnemecek wrote: post #13

> Plans include a new book, You should consider publishing an official, printed book. I would totally pay $30-40 for something like this. And once it's already written, the actual publishing shouldn't be too time consuming (but idk lol). I think that there's a lot of people who'd buy it just to support the project. On one hand, I do have environmental concerns, but on the other hand, I feel like my retention rate wit…

[deleted]

Re: Rust's 2017 Roadmap

#37

Post by Manishearth »

sevensor wrote: post #21
Manishearth wrote: post #6

Earlier quoted context omitted.

Any particular reason rng must be in the stdlib? It's an "official" crate, maintained by the Rust developers. In general Rust tries to keep things out of its stdlib instead opting for crates. It lets these evolve independently of the stdlib (not tied to rustc releases), and also lets them have their own versioning (none of that urllib2 urllib3 nonsense)

It's a battery people are pretty well used to seeing included in a language. POSIX even mandates one for C. For repeatable simulation work you might want something more robust, and hopefully everybody knows it's no use for crypto, but it's a handy thing to have around if you need to flip a digital coin.

It's not harder to use in Rust than it is to pull in a C header file, though.

Re: Rust's 2017 Roadmap

#38

Post by gcp »

agmcleod wrote: post #28
moosingin3space wrote: post #12

Earlier quoted context omitted.

I think VS Code is what the community is rallying around to become the flagship cross-platform Rust IDE, with intellij-rust as the second choice.

Ive found Atom to be better in terms of having the lint as you go. RustyCode is pretty good though otherwise :). I'm interested to see where the debugging goes with it as well.

RUSTYCODE IS DEAD.

I wish more people knew this, because it's probably the thing most people try to install as it has the most downloads. It's no longer maintained and doesn't work correctly with current stable. There's a fork that is being updated that's just called "Rust" in the VSCode addons.

Re: Rust's 2017 Roadmap

#39

Post by moosingin3space »

agmcleod wrote: post #28
moosingin3space wrote: post #12

Earlier quoted context omitted.

I think VS Code is what the community is rallying around to become the flagship cross-platform Rust IDE, with intellij-rust as the second choice.

Ive found Atom to be better in terms of having the lint as you go. RustyCode is pretty good though otherwise :). I'm interested to see where the debugging goes with it as well.

With the Rust Language Server under development, functionality like lint-as-you-go should work really nicely in any editor.

Re: Rust's 2017 Roadmap

#40

Post by [deleted] »

agmcleod wrote: post #28
moosingin3space wrote: post #12

Earlier quoted context omitted.

I think VS Code is what the community is rallying around to become the flagship cross-platform Rust IDE, with intellij-rust as the second choice.

Ive found Atom to be better in terms of having the lint as you go. RustyCode is pretty good though otherwise :). I'm interested to see where the debugging goes with it as well.

[deleted]
Post reply on HN