Live data from Hacker News

Rust 1.26 released

blog.rust-lang.org

131–140 of 178 posts

Re: Rust 1.26 released

#131
post #48

Earlier quoted context omitted.

A couple of commong APIs I can think off the top of my head: - HTTP client - CSV parser/generator I know Hyper and rust-csv are popular. But having an stdlib that's much more feature complete would be great.

Yeah, I can totally appreciate the perspective, but without a significant set of policy changes, I don't see either of these happening. We'll see!

An interesting compromise might be a crate maintained by the core team (std-ext?) that simply re-exports crates under generic names that the community has blessed as being, for better or worse, the default in the Rust ecosystem.

So someone who wants batteries included could add only std-ext as a dependency and get hyper as std_ext::http, regex as std_ext::regex, rust-csv as std_ext::csv and such to avoid needing awareness of the entire ecosystem when first starting out. Seasoned Rust developers would probably continue pulling in dependencies directly, but it might improve the experience for new Rust developers to have everything a 'use' statement away without needing to go look for it.

Re: Rust 1.26 released

#132

As a person who started writing rust this last week, I think I might have picked the best possible time to get in on it. The community is amazing, and I actually understand all these features that were released I've run into about half of the issues they fix already. Rust is coming along very very nicely.

what else would you say it is missing?

Re: Rust 1.26 released

#133
post #126
post #80

Earlier quoted context omitted.

This is true, but even today in 2018, Golang still suffers from the dependency-management hell, the notorious GOPATH, and many other issues it should not have being almost a decade old! Even Rust, which some call "lower-level language", which it is not, has Cargo after it learned from Ruby and Node how important is to have easy package management, and being able to install a new project without knowing almost anythin…

totally fair, but Go did stablize the language itself. i can with zero effort and 100% confidence run any old Go code i have lying around. that's pretty awesome.

> i can with zero effort and 100% confidence run any old Go code i have lying around. that's pretty awesome.

I think you can do that in Rust too (post 1.0). What's more impressive is that canonical go code from five years ago is still canonical.

Re: Rust 1.26 released

#134

Earlier quoted context omitted.

Yeah, I can totally appreciate the perspective, but without a significant set of policy changes, I don't see either of these happening. We'll see!

An interesting compromise might be a crate maintained by the core team (std-ext?) that simply re-exports crates under generic names that the community has blessed as being, for better or worse, the default in the Rust ecosystem. So someone who wants batteries included could add only std-ext as a dependency and get hyper as std_ext::http, regex as std_ext::regex, rust-csv as std_ext::csv and such to avoid needing awar…

Several of these kinds of initiatives, in various forms, have been tried. They never really caught on. (The biggest was stdx)

Re: Rust 1.26 released

#135

So, so, so much stuff in this release! The next few are shaping up to be similar. Very exciting times! As always, happy to answer questions, provide context, etc.

I feet Rust was getting pretty boring... and that's amazing! As a hobbyist I'm pretty happy to see the language maturing. I remember release 1.0 and thinking it was maybe too rushed. How wrong I was!

Is there anywhere I can get a quick recap of major features Rust is planning to eventually maybe implement, and their state? I mean major features like NLL, impl trait, etc.

IIRC: NLL are nightly already, const generics in planning stage, and what happened to CTFE? For us not in the know, a sneak peek on what's coming/being discussed is very exciting, but browsing the issue/RFC tracker is sometimes a PITA and it's hard to keep up to date, especially after getting used to the workarounds.

Re: Rust 1.26 released

#136

As a person who started writing rust this last week, I think I might have picked the best possible time to get in on it. The community is amazing, and I actually understand all these features that were released I've run into about half of the issues they fix already. Rust is coming along very very nicely.

what else would you say it is missing?

Not essential but keyword arguments / named parameters / default arguments. I love those in Python and OCaml/ReasonML.

Re: Rust 1.26 released

#137
post #56

Earlier quoted context omitted.

Maybe after the community chooses a few “winners” the Rust devs could promote them as being “suggested” packages? Also, some suggested metapackages/bundles wouldn’t hurt for newbies, like a set of crates for developing command line tools, for example. Something like this: https://marketplace.visualstudio.com/

It depends, the team suggested this kind of thing two years ago, and the community pretty resoundingly rejected the idea.

And the community does (organically) pick defacto winners. Like chrono, serde and rust csv (well, I'm not sure about rust csv).

It might be nice to have autogenerated docs about the most used soltuions, but I guess the rust cook book sort of fills that niche.

Re: Rust 1.26 released

#138
post #55

Earlier quoted context omitted.

Well, every two languages are different, but at least for systems programming, Golang unfortunately started to replace Python, but given how vitally important security is in that domain, Rust makes a lot more sense than Golang, won't you agree?

I don't think "systems programming" is a coherent concept anymore, so I'd reject the premise of the question. Go has already moved away from that word, Rust will be as well. That you see them as being so different languages reinforces my premise above; they're good at different things, so comparing them doesn't always make a ton of sense.

I have to agree with you.

Re: Rust 1.26 released

#139
post #127

Earlier quoted context omitted.

Once you start putting "systems programming" and "Python" in the same sentence you can be pretty sure that the term "systems programming" has lost all meaning. Or at least using it without elaborating is only going to end up in confusion.

Python is for systems programming like your fist is for hammering nails -- it will be slow, and there will be blood.

Very nicely put!

Re: Rust 1.26 released

#140
post #135

So, so, so much stuff in this release! The next few are shaping up to be similar. Very exciting times! As always, happy to answer questions, provide context, etc.

I feet Rust was getting pretty boring... and that's amazing! As a hobbyist I'm pretty happy to see the language maturing. I remember release 1.0 and thinking it was maybe too rushed. How wrong I was! Is there anywhere I can get a quick recap of major features Rust is planning to eventually maybe implement, and their state? I mean major features like NLL, impl trait, etc. IIRC: NLL are nightly already, const generics…

Yes and no! We’re gearing up for a big release, and so a lot of stuff is landing. I don’t have that text ready at the moment but rest assured that in the next couple of months you’ll see something. “2018 Edition” :)
Post reply on HN