Scala Resurrection by John A De Goes

Critical problems in Scala:
- Scala 3 is still rather academic, should focus more on being production ready
- Scala 3 is not backwards compatible (Interesting to note this negative reaction to Scala 3 in context of recent Rust 2.0 proposals. I also think that any Rust 2.0 should just be a different language)
- Still poor IDE and build tools support
- Still only focused on JVM
- Difficult and opinionated community in a rather unopinionated language

# The Old Ways

A bit of nostalgia: how #RustLang package management looked like back in 2014 before Cargo got released? In my hobbyist experience, it usually was a mix of make, cmake, and messy shell noscripts :D

Nothing personal🤷‍♂

Rust Search Extension for Chrome/Firefox - https://rust.extension.sh/

Search docs, crates, builtin attributes, official books, and error codes

Talks from Rust Nation UK

I have not watched them all but from what I watched, I found Living with Rust Longterm to be pretty solid. Also planning to watch going beyond Arc<Mutex> talk as it promises to have some stuff about lockfree data structures.

Original - https://berserker.town/@moffintosh/109496375350601571

An interesting note, I was mostly writing C# before Rust for example.

One striking stat from the Rust Book Experiment is that 60% of Rust learners self-report as not proficient in a systems language (C or C++). 95% self-report as not proficient in a pure functional language (OCaml or Haskell).

Original

https://blog.rust-lang.org/2023/03/09/Rust-1.68.0

Highlights:
- Sparse registry protocol for Cargo allows downloading information only about crates you're actually using.
- Local Pin construction with pin! macro.
- Default alloc error handler. This allows usage of alloc on stable without requiring the definition of a handler for allocation failure (defining custom handlers is still unstable).

Not a major release, but it's good to finally see some movement in getting async utility functions from external creates to std.

Finally received this awesome book by Mara Bos (team lead of rust library team).

Judging by reviews it is kind of a more hardcore version of Rustonomicon.

You can also find me on https://gloomypixels.space/@egor_ivkov now.

Not that I hate Elon Musk that much, it's just that my feed on Twitter became exceedingly less interesting as all the tech people moved to Mastodon.

Just found Linus on Fediverse (e.g. Mastodon / Akkoma) - https://social.kernel.org/users/torvalds

I hope he keeps his presence there, though when he registered on Twitter it seems he quickly forgot about it.

Some Unix networking tools. Mostly common knowledge, but it's good to have them in one place.

Must move types - https://smallcultfollowing.com/babysteps/blog/2023/03/16/must-move-types/

A recent post by Niko Matsakis, one of the core contributors to Rust. It is basically about linear types, the concept which some of you might be familiar with if you played with Idris2 for example. These types have a restriction that they should be used exactly once.

On the practical side Niko ties this feature with negative trait bounds, which are required for it to work, and async drop, which might be easier to implement with must move types.

Cover of the dreaded and abhorred Rustonomicon

Good old C, though I prefer the "C: A Reference Manual" by Samuel P. Harbison and Guy L. Steele Jr. textbook.

Homesick for a place I’m not sure still exisis

A recent article by Alex Kladov - Zig and Rust

Most of you might know Alex as the original creator of JetBrains Rust Plugin and rust-analyzer and he is now working on TigerBeetle database in Zig. So this article is rather interesting, at least to me:
1. As it highlights a couple of insights into the architecture of TigerBeetle, mentioning exactly how Zig helped them
2. And gives a weighted opinion about Zig as a language from a perspective of a person who used Rust a lot.

The thing is I haven't seen yet any other weighted opinion on Zig, all of the other blogs/posts are usually hate/love comments without much detail. And about the TigerBeetle architecture what is curious is that they went for extreme controllability and simplicity at the same time and it seems that it works.

Original - https://twitter.com/locallycompact/status/1639662790016106497?t=t2pFFl2Kj-bJZN7Xf-KKzg&s=19