Wow, I'm blown away - thank you so much for the warm response! Advanced Hands-on Rust is atop the publisher's best sellers list already!
I've started work on the next beta release - fixing bugs, improving code, updating the Bevy version and tuning the next chapter. (Beta readers get every update including the final release)
Some may wonder why people would block CI on #rustlang nightly.
My answer is simple: either I block in CI, or I will completely ignore it. if we all stopped blocking on nightly, then a problem wouldn't be noticed until it reached beta, which is a much bigger deal to fix.
Nun ja, auch wenn Passkey was gutes ist und von grossen Firmen bereits angeboten im Einsatz ist, fast keine kleinere Firma investiert in die Tools daführ. Dies auch mMn weil sie es als "zu teuer & unnötig" ansehen.
»Chance verpasst – Webauthn-rs-Entwickler hält Passkeys für geplatzten Traum: #Passkey's sollen Anmeldevorgänge sicherer und benutzerfreundlicher machen. Der Entwickler einer #Webauthn-Bibliothek für #Rust sieht das Vorhaben inzwischen als gescheitert an.«
🧵 …wie im obigen verlinkten Artikel schon erwähnt, kann ich durchaus @bitwarden oder deren in Rust entwickelten Klon @vaultwarden_releases empfehlen, obwohl ich persönlich @keepassxc bevorzuge und über eine @nextcloud Instanz die Daten zwischen den Geräten synchronisiere 🔑
I wonder how to best describe how #RustLang influences design, for better or worse. Here is some rambling...
It makes you avoid cyclical data structures, and you are far more aware of ownership. This makes surprising action at a distance harder. It also makes it more difficult to misuse globals or struct fields as globals just to pass data along to where it is needed no matter how.
Enums turn out to replace dynamic dispatch very often. Inheritance is just gone.
That’s often what #rustlang feels like. I started learning C in the late 80s and BASIC before that. Since then I’ve become an expert in several languages and proficient in several others. I’m an experienced #polyglot and though the rust compiler is by far the most helpful - and pushing other compilers to improve - there’s a lot of sharp edges in the grammar itself. Some other polyglots I’m getting into the language agree.
Sure, #rustlang gets easier over time as you become more familiar with nuances but it’s not beginner-friendly, which makes it hard to teach - especially with most modern languages people are learning being GC’d.
Personally, I have no problems with the memory model coming from a C and C++ background, but the various issues with traits such as blanket impls preventing me from specializing (being worked on). Also hard to know when I’ll be allocating or not, even within std.
@ekuber one thing that would help both newer and more experienced alike is a sort of “best practices” guide. There’s so many helpful macros - derive macros especially, which make other #rustlang features work - that are hard to discover. Iterators unlock a lot of cool functionality that also isn’t always discoverable.
Idiomatic patterns could really help people not only learn the language but better participate in the community without feeling foolish.
I wrote a PDF reader with libcosmic yesterday. While it is very basic and not likely to be ready for the first COSMIC release, it is pure rust, lightweight, GPU accelerated, and highly portable.
@soller Saying an application is "pure Rust" feels to me like saying " I am pure [nationality]"
I don't get how every dependency needs to be 100% written in Rust, otherwise it's not "safe" or something. Different programming languages have different strengths, and Rust isn't the only language you can write "safe" code with.
Just my opinion, and I guess you didn't mean it, but just saying... #Rust#rustlang