I've been hacking on a #cli tool to control some smart bulbs using #rustlang and #helix, mostly to get more acquainted with both, and it's fun :)
A week ago I would have used #vscodium.
#RustLang
PSA: Please don't do this in #Rust:
if let (Ok(foo), Ok(bar)) = (expensive_op(), expensive_op()) {
println!("{foo} {bar}")
}
It can be very inefficient, causing people to wait on your software wasting their time (I've just seen this in a fairly popular open source project with 3k stars)!
For a better, more maintainable and efficient version, see second toot or have a look at the playground for the full examples:
1/2
ual v0.7.3 released
ual is a systems language for orchestration and embedded computation. It comes in two forms: a compiler targeting native binaries, and an interpreter for development. Both share the same runtime and produce identical results. This release marks the completion of runtime unification — the interpreter now has full parity with the compiler, including true goroutine-based concurrency, using Go as IR and bootstrapping tool.
What makes ual different
ual is built on a specific philosophical foundation: that coordination is the primary problem of programming and that types and computation are subordinate within coordinated contexts. Data lives in typed stacks accessed through perspectives (LIFO, FIFO, Indexed, Hash). Time is explicit — blocking waits, timeouts are native. Errors must be acknowledged before proceeding.
Binaries available for:
Linux (amd64, arm64, arm, 386), macOS (Intel, Apple Silicon), Windows (64-bit, 32-bit), FreeBSD, OpenBSD, NetBSD
Release:
https://github.com/ha1tch/ual/releases/tag/v0.7.3
Docs
https://github.com/ha1tch/ual/blob/main/docs/MANUAL.md
#ual #golang #foss #rust #rustlang #forth #programming #compsci
The Weekly Challenge 351: Special Arithmetic #Perl #RakuLang #RustLang #Postscript #CrystalLang #Typst #PerlWeeklyChallenge #BlogFiredrakeOrg https://blog.firedrake.org/archive/2025/12/The_Weekly_Challenge_351__Special_Arithmetic.html
Thank you @fasterthanlime that's how it should be done.
context: https://fasterthanli.me/articles/my-gift-to-the-rust-docs-team
#Linux 6.19-rc1 is out:
https://lore.kernel.org/lkml/CAHk-=wgizos80st3bL3EoEoh0+07u9zRjsw45M+RS-js-bcwag@mail.gmail.com/
""So it's Sunday afternoon in the part of the world where I am now, […]
[…] on the #Rust front, we are now starting to see several actual drivers starting to take form. The "mainly preparation and infrastructure" phase is starting to become "actual driver and subsystems development".
That said, despite a few unusual patterns, the big picture really looks pretty normal […]
Linus""
hotpath.rs
Simple #Rust #profiler with memory and #async data-flow insights - quickly find and #debug #performance bottlenecks.
Repo:
@vavakado Sophia, one of the people who resigned over it, put it in no uncertain terms that racism is one of the reasons: https://www.sophiajt.com/why-i-left-rust/
The summary by Amos is very centrist, but it provides a good overview into all the statements made (you can notice how toothless they are, but at least they are corporately apologetic): https://fasterthanli.me/articles/the-rustconf-keynote-fiasco-explained
Then, dtolnay wrote his own perspective, 3 months after the fact, in which he gave a non-apology and suggested that ThePhdDev wanted to do the talk much later and was "pressured" into doing it early. This is utter bullshit, ThePhdDev had regular nervousness and was encouraged many times, he wanted to give that talk.
ThePhdDev rightfully exploded on Fedi for this fucker, being one of the most vocal enemies of that talk, saying this gross lie and half-assing a non-apology. You'll have to forgive me; I don't have a link to it handy. I hope it should still be available.
Today, I once again wake up worrying about #Rust 's future.
Why is a shitbag such as #dtolnay still allowed to single-handedly maintain fundamental libraries for the ecosystem? Why is he part of Library API team? How is he not permabanned for single-handedly permanently damaging Rust by killing off comptime reflection over his racism? How is he not permabanned for the power play he attempted to pull with his "RFC" after pushing pre-compiled binary to serde without notice? Why are MIC companies routinely tolerated at Rust conventions? Why does no one talk about it, despite the problems not being solved? Has #Ruby takeover taught people nothing? Will Rust survive another year without turning into #fashtech?
So many questions. I think about them every time I use Rust, which is often.
Apropos of nothing.
This is a handy guide for this Perl guy:
Compound Types - From #perl to #rustlang #rust
https://oylenshpeegul.gitlab.io/from-perl-to-rust/compound_types.html
The state of the kernel Rust experiment, https://lwn.net/SubscriberLink/1050174/63aa7da43214c3ce/.
> Android 16 systems running the 6.12 kernel are shipping with the Rust-written `ashmem` module. So there are millions of real devices running kernels with Rust code now.
> Ojeda […]: can the "experimental" status be ended? Torvalds said that, after nearly five years, the time had come.
Listen to Glauber Costa (CEO of Turso) talk about building Turso - the in-process SQL database written in Rust and compatible with SQLite.
#rust #rustlang #programming
https://www.youtube.com/watch?v=1JHOY0zqNBY
Seven hours of chatting with llms can save you 5 minutes of reading documentation.
If you have a malformed attribute in your code, rustc will provide suggestions... but way too many sometimes. So now, if there are more than 3, we just discard all of them (original error is already very nice too).
Client Info
Server: https://mastodon.social
Version: 2025.07
Repository: https://github.com/cyevgeniy/lmst