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...

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...

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.

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 🤣

Over the years, I've got fewer and fewer things that surprise me in Rust. Today I discovered that to solve some problems, {} works better than drop();. 🤷‍♂️

Today, my colleague noticed that I broke a routing to api docs. (framework update fuckup) I'm 100% sure I tested it. Is it a sign of dementia if you fail to test your code changes so miserably? Or I'm just starting to see things that I want to see? (Which may be even worse)

"Rewrite it in Rust" is one of the worst marketing slogans ever. IMO, a much better one would be "Make great, new software with Rust". Or whatever else that doesn't make negative associations.

These are earlier ones. Indeed, it's most likely about organized corporate espionage.

It's from my private email. It's the second time in the last 3 months that someone wants to buy/borrow my account to scam people/companies. I guess it may be a popular scam.

The Rust compiler has crossed over 300,000 commits in its repository. It's now getting around 5,000 commits for each release.

For years I named the primary key of each table just id. After starting working on a large project that uses SeaORM I realized that it's nice to name a primary key like table_name_id and create a new type for it.

The problem with many startups is building features users don’t need, using limited development resources, to impress people who will never be their clients.

I tried to use ChatGPT today to help me solve one problem. It misled me totally. The problem was that I had to make a query in SeaORM with a few left joins, for which I had to use aliases. And I wanted to select one field from each of these aliased tables.

For a moment, I thought that it is about an original edit 🤣 Modern, Rust-based version github.com/microsoft/edit

Live from the 10 Years of Rust celebration in Utrecht, Netherlands, we are very happy to announce a new version of Rust, 1.87.0! See the blog post and release notes for all the details! blog.rust-lang.org/2025/05/15/R...

If everything goes according to plan Rust 1.87.0 will be released today. releases.rs/docs/1.87.0/ Only a few larger features. But what I'm really excited about are API stabilizations. Rust is getting more mature with every release. At a fast pace around 4000 commits/release.

The new version of the AI-based tool for suggesting Linux kernel patches for backporting to a stable version is of course written in the most popular language for writing modern tools 🤣 lwn.net/ml/all/aBj_S...

While googling for the best tools to debug memory leaks in Rust I've found an opinion that a garbage collector solves the problem of leaking memory. Partly yes. But believe me, I'm able to create a well-designed memory leak that GC will not be able to prevent.

It looks like we may have a memory leak. Typst crates or integration are suspects in my investigation. I've been using Rust professionally since the beginning of 2021, and I never had to track down a memory leak before. It will be a lot of fun 🤣

If AI says that I've been using Rust since 2008, it must be true 🤣

It's amazing how well uv integrates with nushell. I have not expected that.

There is some ongoing discussion about memory safety and memory leaks. Some people suggest that it's just about preventing the use of doc.rust-lang.org/std/boxed/st... Well, it's not that simple. Memory leaks are situational. It may be hard to judge what is and what is not a memory leak.

I've been using Rust nightly for the past 2 weeks for running tests in the project. rust-lld is great. I can't wait to see it in the stable version.

Since 2008 I used a few different ORMs in a few languages. For the past 3 years, I avoided ORMs and I used only sqlx in the Rust project. Now when I learn SeaORM I must admit that it's a really good ORM. I never was a fan of the Active Record pattern, but it works well here.

On the 1st of April, I started a new full-time contract with MedoSync. It's a company that makes products in the MedTech market and helps in cooperation with InsureTech. Yesterday and today I started working on my first contributions.