Lightnews — Scholar-powered news

Steve Klabnik

@steveklabnik.com

27K followers 1.8K following 9.7K posts

#rustlang, #jj-vcs, atproto, shitposts, urbanism. I contain multitudes. Working on #ruelang but just for fun. Currently in Austin, TX, but from Pittsburgh. Previously in Bushwick, the Mission, LA.

Posts Media Videos Starter Packs

Pinned

Steve Klabnik @steveklabnik.com · Nov 6

For posterity's sake, "Not thrilled to be spending another 4+ years thinking about your old pinned tweet" is a sentence said to me today

A post on june 25, 2015, from me on twitter:

For posterity's sake, "I hope you don't end up getting killed by nazis" is a sentence said to me today

A follow up: While people are digging through my twitter history, hopefully that's a tweet people remember in the future.

12 22 410

Reposted by Steve Klabnik

nrc @ncameron.org · 5h

It's been a while, but I've written another blog post - on panicking and what Rust programmers should do about panicking: www.ncameron.org/blog/to-pani...

To panic or not to panic

From a user's perspective an uncaught panic in a Rust program is a crash. A panic will terminate the thread and unless the developers have taken some care, that leads to the program terminating. This ...

www.ncameron.org

1 5 27

Reposted by Steve Klabnik

Mark Russinovich @markrussinovich.bsky.social · 5h

More Rust goodness for security critical code: Microsoft has joined the Open Device Partnership (ODP) and is investing in foundational security capabilities that will ship in every Surface device and is available for the PC ecosystem:

techcommunity.microsoft.com/blog/surface...

Surface Joins the Open Device Partnership (ODP) | Microsoft Community Hub

Surface joins the Open Device Partnership (ODP) to drive innovation in secure, reliable, and future-ready device firmware—leveraging Rust, modern EC...

techcommunity.microsoft.com

3 22

Steve Klabnik @steveklabnik.com · 9h

thanks to everyone who tuned in to this, and to @zed.dev for having me. conversations are hard! hopefully we can have better ones

Reposted by Steve Klabnik

Zed @zed.dev · 10h

Starting in one hour: @steveklabnik.com and Richard Feldman are talking about why AI discussions keep derailing (and what we can do about it).

12pm ET. Join us: us06web.zoom.us/j/82722563108

1 2 29

Reposted by Steve Klabnik

leon @leyawn.bsky.social · 11h

mtg in 1997: this card is selenia, a guardian angel from the heavenly realm of serra. twisted by the phyrexians, she drove crovax of urborg insane with unrequited love

mtg in 2025: this card is spongebob. from spongebob squarepants

mtg in 2035: we ran out of ideas. this card is your coworker jeff

43 380 1.7K

Steve Klabnik @steveklabnik.com · 21h

it's so good

1 1

Steve Klabnik @steveklabnik.com · 21h

hell yeah

1 1

Steve Klabnik @steveklabnik.com · 1d

Thanks so much!

Steve Klabnik @steveklabnik.com · 1d

Maybe…

Reposted by Steve Klabnik

Deborah McDowell @dem8z.bsky.social · 1d

PLEASE SPREAD THE WORD!!

The University of Texas-Austin is beginning a process to eliminate the Black Studies, Latino Studies, and Gender Studies departments in the College of Liberal Arts. This is a grave threat to the educational liberty of students, faculty, staff, and the people of Texas. 1/

26 990 1.3K

Steve Klabnik @steveklabnik.com · 1d

GraphQL: it's pretty okay

except when the API you're dealing with turns off introspection and also the documentation does not properly describe the api

7 1 84

Reposted by Steve Klabnik

rain 🌦️ @sunshowers.io · 1d

Been meaning to put this somewhere for a while — a real, solid technical reason linear VCS history is better than one full of merges, going beyond taste and subjective preference

lobste.rs/c/cix1sm

> git works best when it has the full merge history available

I used to work on source control. This is actually not true, because (among other things) having a full merge history leads to the likelihood of what are known as criss-cross merges: situations where there isn't a single nearest common ancestor/merge base between two commits. (Merge bases are a crucial piece of information for many source control algorithms.) Criss-cross merges are a pain to deal with, both within the version control system itself and within tools written on top of the VCS. As a result, many tools simply consider criss-cross merges to be outside of their design parameters.

In contrast, a linear history can never have criss-cross merges, greatly simplifying many algorithms.

In general, linear history is friendlier for both tools and humans.

edit: to give an example, a tool I helped build for work needs to load files from the merge base of a commit so it can ensure that "blessed" files don't change in nontrivial ways. The tool simply (and correctly) considers criss-cross merges to be out of scope: https://github.com/oxidecomputer/dropshot-api-manager/blob/bb71488cfa2f642b232ef619bbb3d2c287c8e336/crates/dropshot-api-manager/src/git.rs#L22

Opting into a history full of merges means imposing a burden on the entire ecosystem.

8 12 100

Steve Klabnik @steveklabnik.com · 1d

My brain always misreads it as “be right there filesystem”

1 4

Reposted by Steve Klabnik

tef @tef.bsky.social · 1d

it's just weird how we phrase it as "remote doesn't work" despite all the evidence pointing otherwise, rather than an abject failure of management "i can only run teams if i can physically touch them" and "three hours of traffic and wearing headphones all day is peak productivity"

4 23 200

Reposted by Steve Klabnik

tef @tef.bsky.social · 1d

it's kinda weird that all the software i am expected to use for work are all written by distributed teams, go, python, postgres, linux, chrome, k8s etc

and despite being told "the best teams work in an office together" i don't know of any software i use that's actually written that way

20 270 1.1K

Steve Klabnik @steveklabnik.com · 1d

you need types

2 21

Steve Klabnik @steveklabnik.com · 1d

rust doesn't use get_ idiomatically, you shorten it to the version without the get_

2 5

Reposted by Steve Klabnik

brendan @schlage.town · 1d

atmospheric attractor acceleration assembly:

if you could spend time and/or $ in new ways to accelerate migration from twitter to bluesky (+ github to tangled, substack to leaflet, etc!) what would you try?

experiments, incentives, rhetorical strategies? drop your wildest ideas; let's try em!

25 14 57

Steve Klabnik @steveklabnik.com · 1d

How is that different than handle

Steve Klabnik @steveklabnik.com · 1d

Oof

Reposted by Steve Klabnik

Bryan Cantrill @bcantrill.bsky.social · 1d

As a reminder, this is coming up in a little bit -- join us!

Bryan Cantrill @bcantrill.bsky.social · 3d

🚨 OxF EUROPE-FRIENDLY TIME ALERT 🚨

On Monday, @ahl.bsky.social and I will be joined my Brown CS prof Michael Littman (and AI provost!) to talk AI in higher ed. Join us at 9a Pacific for what promises to be a lively and wide-ranging discussion!

discord.gg/QrcKGTTPrF?e...

Join the Oxide Computer Company & Friends Discord Server!

The Oxide Computer Company and friends; home of the Oxide and Friends podcast. | 4522 members

discord.gg

5 15

Steve Klabnik @steveklabnik.com · 1d

Sized, Default, Iterator… lots of non-verb trait names

Steve Klabnik @steveklabnik.com · 1d

Lmao

Steve Klabnik @steveklabnik.com · 1d

Yea I never did

1 3

Steve Klabnik @steveklabnik.com · 2d

🎉