Rust in 2018: easier to use

I expect a &quot;it&#x27;s easier to use&quot; 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.<p>Aside from the almost completed features in the pipeline, I only see procedural macros (macros 2.0) and whatever happens to make async code easier to write[1] really impacting day-to-day code for most people.<p>[1] I&#x27;d really like to see F# Computation Expressions instead of async&#x2F;await. I know the language experts have said Haskell-like do notation doesn&#x27;t work in Rust but I&#x27;m not sure if the F# tweaks would make it work or not.

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 = &lt;3).<p>OCaml almost fits the bill (Rust is inspired by OCaml after all), but the tooling around it is lacking to put it mildly.

The error messages are indeed _mostly_ marvelous (and there&#x27;s an ongoing effort to make them even more marvelous). Often working with `rustc` feels like pair programming for introverts. But here&#x27;s a question: `rustc` often gives _actionable_ advice - how far can can you get just following that advice? You can make `rustc` happy by following suggestions, but may end up puzzled as to the reasons for the changes it suggests.

Out of curiosity, how is the embedded story (for both bare-metal and RTOS) in Rust nowadays? I took a look early last year, and I remember feeling that the ecosystem still wasn&#x27;t as mature as I liked.<p>There&#x27;s svd2rust [0] and dslite2svd [1], which is basically &quot;bindgen for hardware&quot;. Please do correct me if I&#x27;m wrong, but from what I understood [2], most SVD files leave out a lot of information so a lot of what svd2rust generates is unsafe. Seems like the only way around that is to patch the SVD files. Is this still the case?<p>In addition, what about compiling with no stdlib? And how does that interop with existing Crates (ie. do new &quot;embedded-specific&quot; Crates need to be created?)<p>Super excited to see Rust gain traction! I&#x27;ll definitely take another shot in my free time and see how the ecosystem has matured.<p>[0] <a href="https:&#x2F;&#x2F;github.com&#x2F;japaric&#x2F;svd2rust" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;japaric&#x2F;svd2rust</a><p>[1] <a href="https:&#x2F;&#x2F;github.com&#x2F;m-labs&#x2F;dslite2svd" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;m-labs&#x2F;dslite2svd</a><p>[2] <a href="https:&#x2F;&#x2F;www.reddit.com&#x2F;r&#x2F;rust&#x2F;comments&#x2F;687b3l&#x2F;embedded_in_rust_rust_your_arm_microcontroller&#x2F;dhby29s&#x2F;?context=1" rel="nofollow">https:&#x2F;&#x2F;www.reddit.com&#x2F;r&#x2F;rust&#x2F;comments&#x2F;687b3l&#x2F;embedded_in_ru...</a>

Agreed. I&#x27;ve played with Rust on and off since ~v0.8. I tried to get through the Matasano crypto challenges a few years ago and gave up after hitting a few language hiccups. I recently gave it another go, and it&#x27;s <i>much</i> easier to use now.<p>I must have written around a thousand lines before needing a lifetime annotation, vs. something like 30 lines two years ago.

Julia writes she wouldn’t yet use Rust to write webservices. Right there, this could be the mission for 2018.<p><a href="http:&#x2F;&#x2F;www.arewewebyet.org" rel="nofollow">http:&#x2F;&#x2F;www.arewewebyet.org</a><p>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

Just an idea: I wish there was an official wiki in the lines of Arch Wiki that shows how to do things with Rust with lots and lots of examples.<p>True there is the Rust Programming Language v2 book and several other learning resources online, but they all carry redundant information and pass it on the user to discover what they want to learn. A legendary wiki which acts like a cookbook of all things Rust could be awesome and anyone can pick what they want to learn about and go at it.<p>I would happily contribute and do it, but I&#x27;m just starting to learn Rust. Perhaps it is easier for other experienced Rustaceans to do it right.

Surprised no one mentioned the long compile times yet.<p>For me, while I&#x27;d really like to try Rust, these are a deal-breaker.

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

<i>&gt; like – maybe Rust is not for people who are already C++ experts and who are happy with C++? I don’t know!</i><p>I think Rust is very good for C++ experts. Some key concepts like ownership &#x2F; RAII and etc. are well known in C++, and they should be easy to understand.

I&#x27;m learning Rust by writing graphical &#x2F; glitch art software. Not too much exposure to &#x27;systems&#x27; programming although color spaces are more complex than you&#x27;d think. Performance is important when you shuffle thousands of pixels around, and some of it is easy to parallelize.

Is there something like Helix (Rust) for Python?

Well it is super easy to develop hello world in Rust. Yay! Last time I checked there was no decent HTTP client and the documentation is just non existent for that subpar library. There were lost of promises about the newer version of async io library yet it is still WIP as of today. The performance was 30 times less than the same code in Java and after consulting many Rust developers nobody could tell me why.<p>It is new, it is shiny but lets wait its 10th birthday before it can be taken seriously and pls provide a decent async io &#x2F; http library before we even get started what else can be done in Rust.

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).<p>Which is a shame, because the article is otherwise fine.

A guy w&#x2F; 10 weeks Rust experiance and already gave a talk at RustConf?!

- &quot;I&#x27;m an intermediate programmer&quot;<p>- &quot;I&#x27;m writing a profiler&quot;<p>- &quot;I wrote a mini-OS&quot;<p>- &quot;I had a talk at RustConf&quot;<p>Other than that, it&#x27;s really good to see Rust improving.