This Week in Rust

No nicely-compiled list that I know of. Though now that 1.4 is in beta we won't be adding any features to it (unless there's something unspeakably urgent, that is), so conceivably we could come up with a changelog right this moment. For the moment you may be best served by perusing the installments of This Week In Rust (http://this-week-in-rust.org/) for the past six weeks.

I recommend looking at "This week in" blog and the RFC's also, to form your own opinion of stability http://this-week-in-rust.org/ https://github.com/rust-lang/rfcs#active-rfc-list __________________________ discussion re: stdlib and 1.0 https://www.reddit.com/r/rust/comments/2mo0zb/the_race_towards_10_and_…

• https://this-week-in-rust.org/ • https://www.swedishtechweekly.com/ And then it's not exactly tech, but Matt Levine's "Money Stuff" : • https://www.bloomberg.com/account/newsletters/money-stuff

“This week” train! I’ll go next This week in Rust https://this-week-in-rust.org/

I especially like the following quote in that context: > The biggest failure in Rust‘s communication strategy has been the inability to explain to non-experts that unsafe abstractions are the point, not a sign of failure. Appeared on TWiR: https://this-week-in-rust.org/blog/2021/10/20/this-week-in-rust-413/.

Along the lines of "What's upcoming and learn from it", I've found the https://this-week-in-rust.org/ weekly newsletter valuable for this.

My opinion (programming with Rust since May 2015): Rust is complex but 2020 I discovered that in «This week in Rust» [0] many weeks pass with the section New RFCs No new RFCs were proposed this week This shows that the rapid pace of change already started to slow. [0]: https://this-week-in-rust.org/

So they're definitely in the space (I just read a fantastic rust post on there[0] today, thanks to This week in rust[1]) but you can't beat the staying power/massive bags of money/developer goodwill that is already heaped on Github. Github entering this space would be a death sentence for a site like dev.to, unless they massively fuck it up (or dev.to adapts and provides some extra value-add/integration). [0]: https://dev.to/pnehrer/a-story-of-rusty-containers-queues-and-the-role… [1]: https://this-week-in-rust.org/blog/2020/08/26/this-week-in-rust-353/

Go to rust subreddit, sort by top for the month, read the top few blog posts every so often. Otherwise, read through the blog posts listed in previous editions of https://this-week-in-rust.org/

Development of high quality async support in Rust is happening right now, so remember to wear a hard hat. ;-) I like to watch https://areweasyncyet.rs/ and https://this-week-in-rust.org/ to see where things are.

Depending on your profiency : - you can actually contribute to the compiler itself : https://github.com/rust-lang/rust/issues?q=is%3Aopen+is%3Aissue+label%… - you can contribute to the low-level abstracting graphics library : https://github.com/gfx-rs/gfx/labels/contributor-friendly - and more generally you can also take a look at the weeksletter (and previous iterations of it to see where help was requested) :Week's letter : https://this-week-in-rust.org/

https://www.reddit.com/r/rust/ and https://this-week-in-rust.org/

https://this-week-in-rust.org/ features some job-postings in the "fn work(on: RustProject) -> Money"-section every now and then...

https://www.jendrikillner.com/tags/weekly - Graphics Programming weekly https://halisavakis.com/category/technically-art - Technically Art weekly https://us17.campaign-archive.com/home/?u=ac8ab0580c321574fe178a646&am… - Blender Guru Newsletter https://twitter.com/search?q=Creative%20Code%20News%20(from%3AsableRap… - Creative Code News rarely: https://tympanus.net/codrops/collective - Codrops - web design news, resources https://speckyboy.com/?s=Weekly+News - Speckyboy - designers news https://kerkour.com/tags/newsletter - Kerkour - favorite links https://habr-com.translate.goog/ru/search/?q=%D0%B4%D0%B0%D0%B9%D0%B4%… - habr ru - various technical weekly news bookmarked: https://www.datascienceweekly.org/newsletters - Data Science Weekly https://this-week-in-rust.org - This Week in Rust https://www.fightaging.org/archives - Fight Aging

Assuming that "crypto" was meant to refer only to cryptocurrency, there are a few companies working on non-blockchain/non-cryptocurrency crypto(graphic) tech which are paying as much as web dev jobs. For example, I stumbled upon ockam.io during my last job search (no affiliation, and never interviewed with them as they weren't actively hiring when I wrote to them last year). I vaguely remember there being a few others, though I can't remember any names off the top of my head (it has definitely gotten harder searching for those kinds of companies as most job ads are drowned out by all the blockchain jobs). Old job posts on https://this-week-in-rust.org/ often contain a few interesting companies. (Shameless plug: If anyone is interested in working at a non-profit focusing on non-blockchain cryptography in the field of multi-party computation, the company I'm working at is hiring at the moment and the salary ranges [for a 4-day work week] are listed: https://sinefoundation.notion.site/SINE-Job-Board-d28eda00c5db43f297c6…

I'm consistently blown away by just how good the project management for this language is. It's not just the forward progress that the language is making (which is considerable), but also just how well they package the information up into a form that the rest of us who are not involved day to day can digest, like has been done here. Another example is the "This Week in Rust" newsletter which takes progress that would've taken you hours to read about yourself, and puts it into a succinct format that you can get through in minutes [1]. The Rust 2017 roadmap which targeted forward movement on all the language's weakest features was admirable in itself, but even moreso is how much progress has already been made. In particular, I'm really excited about incremental compilation, which is showing as much as 5x speedups in early results [2]. I was also very happy to hear that the Rust team acknowledges that regardless of how performant they are, futures are not a particularly ergonomic or maintainable way to write code, and are considering what new constructs might look like over the longer term: > Over the rest of this year, we expect all of the above libraries to significantly mature; for a middleware ecosystem to sprout up; for the selection of supported protocols and services to grow; and, quite possibly, to tie all this all together with an async/await notation that works natively with Rust’s futures. I'm still on dabbling in Rust, but I'm fairly convinced that in another…

https://this-week-in-rust.org/blog/archives/index.html The first issue was on 2013-06-07, just over ten years ago.

Global: - https://www.to-rss.xyz/wikipedia/ (30/mo) Local: - https://publicola.com (19/mo) - https://washingtonstatewire.com (1/mo) - https://southseattleemerald.com/category/news/ (20/mo) - https://www.seattlebikeblog.com (21/mo) - https://seattletransitblog.com (10/mo) - https://wasmoke.blogspot.com (2/mo) - https://washingtonbeerblog.com (30/mo) Tech: - https://this-week-in-rust.org (4/mo) - https://matrix.org/blog/category/this-week-in-matrix (4/mo) - https://community.openstreetmap.org/top (150/mo) - https://discourse.nixos.org/top (150/mo) Plus about 100 personal blogs and update feeds.

>As always (this _is_ HN) because the poster thought _it_ might be of interest to the HN crowd I think you misunderstood the intent of gp's question. The "it" could be mean very different things: (1) It is this particular #398 issue has something notable in it that the previous 397 issues don't have: https://this-week-in-rust.org/blog/archives/index.html or (2) It is the whole TWIR blog of only which #398 is merely a representative sample that has no more and no less significance than the previous issues

If anybody is looking for a Rust job, they in fact do exist, and are growing. This Week in Rust lists 5 this week [1], and 5 is more than zero! [1]: https://this-week-in-rust.org/blog/2017/01/17/this-week-in-rust-165/

Copy paste from https://this-week-in-rust.org/blog/2021/10/06/this-week-in-rust-411/#q… There's a common trope among people unfamiliar with rust where they assume that if you use unsafe at all, then it's just as unsafe as C and rust provided no benefit. Comparing C's approach to safety vs Rust's is like comparing an open world assumption to a closed world assumption in formal logic systems. In C, you publish your api if it's possible to use correctly (open world). In Rust, you publish a safe api if it's im possible to use in correctly (closed world). Rust's key innovation here is that it enables you to build a 'bridge' from open world (unsafe) to a closed world (safe), a seemingly impossible feat that feels like somehow pairwise reducing an uncountable infinity with a countable infinity. Rust's decision to design an analogous closed-world assumption for safe code is extremely powerful, but it seems very hard for old school C programmers to wrap their head around it.

This >I have a very hard time grasping all the functionality/concepts is (partially) because this > if we ever want to control the tsunami of security flaws Most focus in how the borrow checker work "against" you but that is not even the harder. Performance and how manage memory are more "painfull" in rust. BECAUSE NOBODY KNOW HOW DO FAST & SAFE CODE. Not ALL the time. Without extra help of the compiler your assumptions can get wrong in invisible ways... Rust WANNA: - See what is costly - See what is unsafe or not - See what own what - See what is on heap or stack The borrow checker is just a part of it. From https://this-week-in-rust.org/blog/2019/07/02/this-week-in-rust-293/ Python and Go pick up your trash for you. C lets you litter everywhere, but throws a fit when it steps on your banana peel. Rust slaps you and demands that you clean up after yourself. – Nicholas Hahn

Here's a funny quote about that... >> Can you eli5 why TryFrom and TryInto matters, and why it’s been stuck for so long ? (the RFC seems to be 3 years old) > If you stabilise Try{From,Into}, you also want implementations of the types in std. So you want things like impl TryFrom for u16. But that requires an error type, and that was (I believe) the problem. > u8 to u16 cannot fail, so you want the error type to be !. Except using ! as a type isn’t stable yet. So use a placeholder enum! But that means that once ! is stabilised, we’ve got this Infallible type kicking around that is redundant. So change it? But that would be breaking. So make the two isomorphic? Woah, woah, hold on there, this is starting to get crazy… > new person bursts into the room “Hey, should ! automatically implement all traits, or not?” > “Yes!” “No!” “Yes, and so should all variant-less enums!” > Everyone in the room is shouting, and the curtains spontaneously catching fire. In the corner, the person who proposed Try{From,Into} sits, sobbing. It was supposed to all be so simple… but this damn ! thing is just ruining everything. > … That’s not what happened, but it’s more entertaining than just saying “many people were unsure exactly what to do about the ! situation, which turned out to be more complicated than expected”. https://this-week-in-rust.org/blog/2019/03/05/this-week-in-rust-276/ https://www.reddit.com/r/rust/comments/avbkts/this_week_in_rust_275/eh…