RSSAmplifier

Blog

Sam Sieber

Recent content on Sam Sieber

samsieber.techRSS feed ↗5 posts

Latest posts

No Namespaces in Rust is a Feature

Rust doesn’t have namespaces in its package management system. It’s often viewed as a bug. But it’s not a bug, it’s a feature! While there are negative aspects of a flat package registry, there are also real benefits. Stability, continuity, and unity (discourages forks and fragmented identity). Proposals that seek to add namespacing without addressing the positive aspects…

Rust 2020 - Embrace and Extend

I’ve used Rust a couple times at work for small tools, and written a couple of experiments in Rust. So before saying what I want out of Rust, I’d just like to say thanks to the wonderful community. I liked the Rust 2019 progress, and I can put most of my wants for 2020 under two main labels. Embrace The 2019 roadmap was great. We got a good start, but it seems like most areas still…

Strengthening the Unsafe Ecosystem through Collaboration

There’s been a bit of noise around on auditing usage of unsafe in Rust dependencies. I’d like to add my thoughts: a review of what unsafe is, why it gives people issues, and what I think a better (but currently non-existent) approach is. A Brief Rust Primer Rust is a language that doesn’t use garbage collection. Instead it has the borrow checker, which tracks data access,…

About Me

I’m a curious developer who loves throwing things at the wall and seeing what sticks. I enjoy considering things that seem hard, dumb or outlandish - I occasionally find ideas worth implementing from those. I have a small family and enjoy my time with them when not working. They are a great source of joy.

Type-Safe App-Specific E2E DSLs in Kotlin

A couple years ago I wrote an experimental strongly statically typed DSL for testing a web-app in Kotlin. It was actually composed of two parts: the DSL generator, and the generated DSL itself. It didn’t survive as the solution we were looking for, but it was an informative experiment, and I think there’s potential in the approach I took with it. At the time, I was one a few engineers…