Create accountLogin

Recent searches

No recent searches

Search options

Only available when logged in.
zirk.us is one of the many independent Mastodon servers you can use to participate in the fediverse.
Literature, philosophy, film, music, culture, politics, history, architecture: join the circus of the arts and humanities! For readers, writers, academics or anyone wanting to follow the conversation.

Administered by:

Server stats:

746
active users

zirk.us: AboutProfiles directoryPrivacy policy

Mastodon: AboutGet the appKeyboard shortcutsView source codev4.3.7

#rustlang

193 posts111 participants12 posts today
Public
Kris Warner 🦀 🐧

It's been a minute (almost 3 years, but who's counting?), but I've just released a new version of broken-links, to add a user agent to it (thank you @mike_k for the suggestion).

It's a link checker - give it a starting URL, and it'll recursively crawl all pages with that domain, checking all internal and external links found.

Install via `cargo install broken-links` or see the release page for other options: codeberg.org/kdwarn/broken-lin

Summary card of an release titled "v0.2.4" in repository kdwarn/broken-links
Codeberg.orgv0.2.4 - kdwarn/broken-linksSee the [changelog](https://codeberg.org/kdwarn/broken-links/src/branch/main/CHANGELOG.md#0-2-4-https-codeberg-org-kdwarn-broken-links-compare-v0-2-3-v0-2-4).
#RustLang#Rust#cli
Public *
Dave Griffiths

Had a interesting year or so learning #RustLang - started using it for a wasm based browser game (Nergal) and now the last few months using it embedded on a Raspberry Pi Pico (SmogOff).

Very different use cases, but pretty happy with it. Takes a while to stop being dismayed at the compiler and see it as a friend - but it definitely encourages good ways of thinking.

It helps a lot, when trying to figure out it's quirks - knowing exactly which bad situation (usually a C++ one) it's making impossible. Without that I can see how it feels very awkward and verbose.

I never want to use a language which isn't expression based any more, that's for sure.

Beyond the borrow checker, the simple things are what I've found the best - e.g. error propagation which is actually designed into the language (rather than a bolted on weird different thing like try/catch or a vague convention). In the embedded world, this has made it much easier to debug third party drivers and whatnot. Also to write code to cope with every single possible error state in a lot of peripheral devices.

Public
Chris Woody Woodruff

I'm learning Rust from a C# developer's perspective—one day at a time for 42 days.

I have 36 days left.

If you're curious how Rust stacks up against .NET, follow along here:
woodruff.dev/from-c-to-rust-a-

Chris Woody Woodruff · From C# to Rust: A 42-Day Developer Challenge - Chris Woody WoodruffI’ve spent over a decade writing C# and building solutions on .NET. But for six weeks, we will step outside the managed world of garbage collection and runtime JIT to dive headfirst into Rust—a systems programming language that promises performance, safety, and no nulls. Over the course of 42 days, we will learn something new about Rust every single day. We will fight the borrow checker. We will make mistakes. And I will blog it all from the perspective of a C# developer trying to make sense of it.
#RustLang#CSharp#DotNet
ExploreLive feeds
About