RustViz - Interactively Visualizing Ownership and Borrowing

https://github.com/rustviz/rustviz

Well, yeah, sort of... Though Liskov's Substitution Principle I would argue is purely about objects. But I feel like the principles are rather common and just need to be reformulated in a more general way. It's time we stopped considering OO as the only model that exists 😁.

https://t.co/yuP2yyF7TX?amp=1

Wishlisted.

It's good that remote opportunities now are somewhat fixing the issue. I guess it's one of the positive outcomes of the whole COVID situation.

https://twitter.com/graninas/status/1382906570913284098?s=19

Omg those evil Rust developers😁

I was reading through some thoughts of the Rust newcomers. And in general I think there is a bit of confusion.

Rust is not only about memory safety with lifetimes.

As it is mentioned at the https://www.rust-lang.org/ Rust main goals are reliability and efficiency.

Rust achieves these goals through many different language features and design patterns, and lifetimes are just a part of it. In fact they support the more general concept: ownership model.

Ownership model is undeniably a great helper in terms of reliability. Though lifetimes are just an implementation aspect of it, not the main focus.

In conclusion I would say when trying Rust it's better to go one by one through the book chapters, it tries to show all of the aspects of the language tying them to the corresponding language goals. Rust introduces many new concepts and though lifetimes are maybe the most well known of them, it is just one of the many.

Ruby Ruby Ruby... (Song by Kaiser Chiefs)

*Music fades*

https://twitter.com/editingemily/status/1383509743977697288?s=09

One of the more elegant explanations of the financial side of bitcoin and many other cryptocurrencies.

Paul Graham to his kids:
https://twitter.com/paulg/status/1384040569710682113?s=09

"If we don't use metrics the imposters will win."

There is a huge debate whether Rust needs optional arguments that can be omitted instead of using None. And as always here is a macro to do this😁.

Overusing macros is not good for many reasons and I don't think this crate should be used extensively. But for the sake of proving the fact, this can be easily supported by Rust compiler in the same generative way.

https://www.reddit.com/r/rust/comments/mu4x5k/optargs_011_functions_and_structs_with_optional

Tor browser seems to be using Rust

https://www.torproject.org/about/jobs/tor-browser-developer/

Hell yeah, who would use kubernetes when you know a DevOps guy Michael😁

https://twitter.com/tomaka17/status/1384815348063559680?s=19

It really does feel like that. Actually it's quite difficult after that to get back to writing in other languages. You just expect a lot more from the compiler...

https://twitter.com/rust_foundation/status/1385310806498103297?s=19

Rust Language Cheatsheet. It seems like a good reference to check your knowledge of Rust topics. Also might serve as a basis for Rust tech interviews I guess.

https://cheats.rs/

Not that I was planning to join the hype, but someone went and made an NFT of me😂. Actually quite good and the interesting fact is I was really doing Kendo for several years.

The NFT is a part of the pack that was made by some community members for some employees in our company. Never thought this good about the community 😅.

Wanted to publish this for a long time. It is an overview of different RwLock implementations for Async Rust. Actually the results were quite surprising for me. I assumed everywhere fair scheduling was used, but seems like it is not the case.

The overview is 1 year old, so some things might have changed. And I guess this needs more investigation. Though might serve as a reminder of how careful we should be with async for now, especially with locks.

https://www.reddit.com/r/rust/comments/f4zldz/i_audited_3_different_implementation_of_async/

Facebook is joining Rust Foundation now!

https://developers.facebook.com/blog/post/2021/04/29/facebook-joins-rust-foundation/