I've got a nice contract, but from time to time, I'm looking at LinkedIn and Upwork to check what interesting things can be found there. And today I've found this. I'm not sure what to say, but it's good to use spellcheck from time to time...
A few days ago, I received a license for Rust Rover from my company, and today I received permission to use it after hours for my personal projects. So it looks like I'll drop VSCode for a while (but not Helix 🤣). What I'm really happy about is the database schema compare tool.
It's quite possible that Rust 1.91.0 will be released today releases.rs/docs/1.91.0/
I've been using computers for over 31 years, and I had no idea that there was a specification for FILE_ID.DIZ www.textfiles.com/computers/fi...
Also, it's a cautionary tale about how to properly test a system. 🤦♂️
Cautionary story for all who want to rewrite old tools. www.phoronix.com/news/Ubuntu-.... It's better to create new tools and not have to think about backward compatibility. All drop in replacements are prone to such problems and need to take extra care about compatibility.
It's just data from Google AI, I'm not sure if it's true. In my experience, a small Dioxus app runs with just around 4 MB of RAM when I run development version with dx serve. IMO it's a huge business opportunity in replacing all this Electron-based, memory-hungry slop.
Currently, AI technology is flawed. Besides these flaws, it can be helpful for intelligent people who know how to deal with mis/disinformation. Those who don't know are pretty fucked...
When others train Artificial Intelligence, you should train your Natural Intelligence.
"Premature optimization is the root of all evil".
Before you start optimizing you need to really know what you are trying to do and how current implementation works. Something may look not 100% optimal, but it looks that way because there is a good reason for that.
match game().state {
State::Failure => rsx! { RenderGameFailure {} },
State::InProgress => rsx! { RenderGameInProgress { game, input_value } },
State::Success => rsx! { RenderGameSuccess {} },
} It's that simple with Dioxus 😀
"dx self-update
0.313s INFO Your version is out of date!
0.313s INFO - Yours: 0.7.0-rc.1
0.314s INFO - Latest: 0.6.3
0.316s INFO Downloading update from Github
0.316s INFO | Dioxus v0.6.3"
Ok, that was not expected 🤣
Today I've spent a few hours working on a side project - a simple numbers related game. I'm using Dioxus and Tailwind. I can't say it's trivial, but it's quite easy. It's really worth a try if you want a cross-platform solution for Windows, Linux, Mac, Android, iOS, and web.
I'm not sure if I should go down this rabbit hole - ./x.py bench --stage 1 compiler - I created some benchmarks for SmallVec vs Vec, and I'm starting to doubt in the sense of using SmallVec. Seriously, you should use SmallVec only when you benchmark and prove that it's better.
A lot of people are waiting for Reflections in Rust. I guess we are seeing here the first steps toward this goal github.com/rust-lang/ru...
Congrats to the compiler team!
If you were annoyed by Rust build speed, check the new release. You should be nicely surprised by both the full rebuild and the incremental build speed.
Of course, there are still many things that can be improved, but this is something that we have all been waiting for.
Last Friday I was in a rollercoaster park, because my son had his 10th birthday, so maybe I missed the noise and ovations. Today I had a nice 9,5 hours of work with Rust 1.90.0 compiler, and I must say that LLD is a game changer in terms of build process speed.
LLD is a great win for Rust. Can't wait for other performance improvements! 🤣
I've been using nightly for almost 6 months to use LLD for tests, because it has increased the speed of the whole testing process for me a lot. In Rust 1.90.0, I'm also using it for normal project development. And it speeds up things for me a lot. Finally! 😀
I wonder if dividing a proprietary project into multiple crates isn't an anti-pattern. You have like 320k LOC in 70 crates. Sometimes it's hard to refactor due to circular dependencies. Not to mention the orphan rule. It's not impossible to have that code in subdirs in one crate.
If a function returns Option or Result, it's a good practice to start its name with the try_ prefix. If a function returns a mutable reference, it's a good practice to end its name with the _mut suffix.
This is how new Rust devs feel after the first week 🤣
Just the index of this specification www.hl7.eu/HL7v2x/v24/s... is approximately 74 A4 pages in print.🤦♂️
Happy new Rust! 🎆🦀
Rust 1.89.0 has been released!
This release brings you inferrred array length, new lints, u128/i128 in extern "C", NonZero<char>, File::lock, many x86 intrinsics, and much more! ✨
Check out the blog post and release notes for all the details: blog.rust-lang.org/2025/08/07/R...
it.slashdot.org/story/25/08/... Just wonder how many of such devs work for companies that don't know they are from China 🤣
