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

Rust in 2018: easier to use

jvns.ca

Post reply on HN
Print view View original

31–40 of 305 posts

Re: Rust in 2018: easier to use

#31

Post by z0ltan »

StreamBright wrote: post #11
nafizh wrote: post #3

Anyone has suggestions on learning rust for a python programmer who is also not strong on systems concepts?

Depends what is your goal. Learning a language with decent type system? Learning a language with lower level access to operating system features? I would suggest to learn OCaml because it got really popular in 2017 thanks to Facebook & Bloomberg, it has an amazing type system and you can use it to build CLI tools and web pages (Reason/Bucklescript) with an insanely good tooling (utop, jbuilder, merlin) and the commun…

I have always been interested in OCaml, but I have a genuine question though - last when I looked at seriously at it, the standard library seemed to be a bit of a mess lacking a lot of features. A lot of modern resources seemed to focus on using Jane Street's Core(?) which I would not like to use - I'd rather depend on the standard language for standard features. Is this still a thing, or am I mistaken, or both? Please help! I really would like to use OCaml for a variety of hobby projects, including toy compilers. Which books/resources would you recommend?

Re: Rust in 2018: easier to use

#32

Post by z0ltan »

aaron-lebo wrote: post #4
nafizh wrote: post #3

Anyone has suggestions on learning rust for a python programmer who is also not strong on systems concepts?

Read the rust book and actually build something with it. There's a lot of stuff in Rust that you just never have to consider in Python so there's no easy way other than diving in. Actually, Programming Rust might be better, but it's not free. https://doc.rust-lang.org/book/second-edition/ http://shop.oreilly.com/product/0636920040385.do

Upvoted for Jim Blandy's book. That man can teach!

Re: Rust in 2018: easier to use

#34

Post by Manishearth »

yen223 wrote: post #12

This is going to sound weird, but I would like to see a garbage-collected Rust. Take away the borrow checker, and you still have a modern language with UTF-8 support out-of-the-box, algebraic data types, pattern matching, a focus on performance, and great tooling (cargo + rustup = OCaml almost fits the bill (Rust is inspired by OCaml after all), but the tooling around it is lacking to put it mildly.

This sounds like Swift :)

(ARC, not tracing GC, but still.)

Re: Rust in 2018: easier to use

#35

Post by michaelchisari »

banachtarski wrote: post #29
eecc wrote: post #24

Julia writes she wouldn’t yet use Rust to write webservices. Right there, this could be the mission for 2018. http://www.arewewebyet.org Nobody with a sane mind would write C or CPP micro-services, but post-Spectre and Meltdown any reclaim in performance is tangibility valuable. Rust could be the one to swoop in and claim the position

> Nobody with a sane mind would write C or CPP micro-services why? I do this all the time. Maybe I should check into a nearby asylum.

It must depend on what you're building with it. I haven't seen any reason why it couldn't be used for serving up data for an api.

But as far as using it as a full featured web framework, a la Rails, Django or even Laravel, I can see why people say it's got a long way to go.

That said, I haven't built anything production or large scale in Rust, so I can't claim to be an expert.

Re: Rust in 2018: easier to use

#36

Post by curiousGambler »

grayrest wrote: post #9

I expect a "it's easier to use" evangelism push around the upcoming epoch release. There are a bunch of mostly completed but still feature flagged changes that should remove a lot of the borrow checker toe stubbing. Getting rustfmt (formatter) and clippy (linter) on stable Rust would ideally be part of the push. Aside from the almost completed features in the pipeline, I only see procedural macros (macros 2.0) and wh…

Why anyone would name anything "clippy" again is beyond me.

Re: Rust in 2018: easier to use

#37

Post by Manishearth »

grnadav1 wrote: post #18

A guy w/ 10 weeks Rust experiance and already gave a talk at RustConf?!

The closing keynote at RustConf is generally someone who is new to Rust or has never used Rust but can bring in an interesting perspective. Last year we had Joe Duffy, who I don't think has done much Rust aside from perhaps basic experimentation, but has a lot of relevant experience from running the Midori (Microsoft's safe systems language) project.

(also, the author isn't a "guy")

Re: Rust in 2018: easier to use

#38

Post by z0ltan »

hateduser2 wrote: post #33
karo_ops wrote: post #28

Each time I try to read an article by Julia, I get alienated by the chidlish style of writing (count the exclamation marks and caps). Which is a shame, because the article is otherwise fine.

You can probably just ignore that right?

Why the aggro? He's just expressing his point of view.

Re: Rust in 2018: easier to use

#39

Post by curiousGambler »

eecc wrote: post #24

Julia writes she wouldn’t yet use Rust to write webservices. Right there, this could be the mission for 2018. http://www.arewewebyet.org Nobody with a sane mind would write C or CPP micro-services, but post-Spectre and Meltdown any reclaim in performance is tangibility valuable. Rust could be the one to swoop in and claim the position

I get the impression Go runs the microservice space. It's built for it and is incredibly fast despite the GC. I don't see Rust claiming that position anytime soon.

Re: Rust in 2018: easier to use

#40

Post by karo_ops »

hateduser2 wrote: post #33
karo_ops wrote: post #28

Each time I try to read an article by Julia, I get alienated by the chidlish style of writing (count the exclamation marks and caps). Which is a shame, because the article is otherwise fine.

You can probably just ignore that right?

Not really. Writing style is an inherent part of journalism.

`s/\!\+/./` would cut it, though.

Post reply on HN