And Rust experiences "is a plus"😁

Hah it's nice to see the project I worked at previously trending in crate of the week. Good job Qdrant team!

Crate of the week: Qdrant

This week's crate is Qdrant, an open source production ready vector database/similarity search engine written in Rust. There are APIs available for Rust, Python, Javanoscript/Typenoscript and Go.

Not a problem anymore

But you have to use a monad to print Hello World! 🌚

The game development process in general has a lot of tedious tasks so it's only logical to automate them as much as possible. Though there still remains a question how to integrate the artist's vision with the generated content.

https://blog.luden.io/generated-adventure-the-postmortem-of-a-game-made-with-chatgpt-and-midjourney-prompts-included-f87e7e615204

Oof nice release - Rust 1.70

Many things stabilized:
- OnceCell
- IsTerminal
- Arc, Rc::into_inner

These are a few immediately useful for me.

It's a good break from all the governance drama

A proposed ownership design for D Lang in an article published in 2009, which as you could guess predates Rust's ownership system - https://bartoszmilewski.com/2009/06/02/race-free-multithreading-ownership/

Though as the author himself notes on Twitter, Graydon Hoare when working on Rust might have also been aware of the papers that D Lang ownership proposal lists as references.

And another slide by Graydon Hoare explaining the move semantics from way back, when Rust was only incubating. I like how from beginning they decided to make the terminology not too academic.

And as usual Rust comes up as the most "admired and desired" language in the Stack Overflow survey

Rust fact vs. fiction: 5 Insights from Google's Rust journey in 2022

TL;DR

For those thinking about getting started with Rust here Google Devs confirm and debunk some rumors about the language:

Rumor 1: Rust takes more than 6 months to learn – Debunked (1-2 month to be productive)

Rumor 2: The Rust compiler is not as fast as people would like – Confirmed

Rumor 3: Unsafe code and interop are always the biggest challenges – Debunked (interop is easy, macros and async are the hardest)

Rumor 4: Rust has amazing compiler error messages – Confirmed

Rumor 5: Rust code is usually of high quality – Confirmed (people feel that code written in Rust is usually of high quality by nature)

Interesting trick, but there are usually easier ways to do typechecks during macro expansion in more specific cases

useful in macro expansions / codegen
playground
similar trick ICEd on 1.59: Rust issue

Yeah, I know, I am guilty af 😂

A new blog post from Bob Nystrom talks about sum types and making them look nice in a procedural language, while preserving memory safety.

Though they are not entirely type-safe, I agree with him that it's a good fit for the language that targets simplicity. Maybe Go should have also done something like that, it would definitely look better than simulating variants with interfaces like it's usually done there

Getting closer to ML ready state. Though in any case it won't be possible to iterate/prototype in Rust as fast as you can in Python. Which I guess is one of the reasons why ML is not present enough in Rust yet.