David Barsky

[David Barsky @endsofthreads]

a thing we’re very proud of at @erscio is that we don’t do *any* long lived secrets. it’s service accounts, oidc, and dpop-bound tokens (where appropriate) all the way down

[kitze 🛠️ tinkerer.club @thekitze]

to me it was always bonkers insane that in order to connect service A with service B i need to ... paste an api key ???

how come as a fucking industry we didnt invent a better way to connect deployments with services

[David Barsky @endsofthreads]

reposting some great content from bsky

[David Barsky @endsofthreads]

@nickgeracehacks good lord

[Steve Klabnik @steveklabnik]

very excited to see this out of A\

this is our thesis at @erscio ! But we are building a git compatibility layer: https://t.co/zkm2AhXN5v

enterprise adoption of new source control is a big ask, so making a smooth bridge from the past to the future is a big part of our offer

[Steve Klabnik @steveklabnik]

OH: “I should get my homelab SOC 2 certified for the lulz”

[David Barsky @endsofthreads]

holy moly @superlogical's rex is *so darn good*. just oozes with polish, style, and care.

[David Barsky @endsofthreads]

a tip for friends new to Rust: Geekbench's single-core CPU benchmarks are an unreasonably helpful proxy for how snappy Rust compilation feels on a warm development loop.

[David Barsky @endsofthreads]

@fasterthanlime you absolutely should

[David Barsky @endsofthreads]

@LParreaux @tigregalis @elricmann i mean, miri isn’t really community-enforced scrutiny, it’s a project-endorsed tool that provides mechanisms to verify whether unsafe code is sound. it’s certainly more advanced than anything i’m aware of that touches the JNI!

[David Barsky @endsofthreads]

@LParreaux @tigregalis @elricmann and i’m curious: how would you feel if unsafe was a nightly-only/stdlib-only feature? because that’s not too dissimilar to the situation you’ve got on the JVM.

[David Barsky @endsofthreads]

@LParreaux @tigregalis @elricmann agree to disagree, but to move the conversation a few steps back: you can’t simply remove sun.misc.unsafe and expect your program to work. you still have the JNI and the runtime itself. how is the runtime speaking to the os?

[David Barsky @endsofthreads]

@LParreaux @tigregalis @elricmann and yes, a runtime like the JVM or WASM help reduce the impact of soundness issues in Java or Scala, but a lot of places are using Rust where a runtime can't work (I include a lot of latency-sensitive developer tools in this!) or the alternative is *definitely* unsound.

[David Barsky @endsofthreads]

@LParreaux @tigregalis @elricmann rust does have a complicated type system—no argument from me—but nobody's found a fundamental soundness flaw within the overall design. people tried! i know that's not the same thing as a positive proof, but given it's been ~10 years, i know how I'm willing to bet.

[David Barsky @endsofthreads]

@LParreaux @tigregalis @elricmann put differently, there are a lot of mechanisms to surface unsound code + the community has developed extremely strong norms against using unsafe code. if unsafe code is used, it's generally heavily quarantined.

[David Barsky @endsofthreads]

@LParreaux @tigregalis @elricmann sorry, i wrote too many exclamation marks. what i'm trying to say: it's easier to audit for unsafe and me running miri during development/CI surfaces potential issues in the libraries that i'm depending on. a potential issue was surfaced for me yesterday!

[David Barsky @endsofthreads]

@LParreaux @tigregalis @elricmann anyways, i got annoyed by the wikipedia article and proposed a bunch of edits: https://t.co/6Fpku8kpce

[David Barsky @endsofthreads]

@LParreaux @tigregalis @elricmann as for that CVE crate: it's not really used and it's a soundness hole that'll be fixed: https://t.co/2avwgiCIHZ. nobody's writing that code in the wild.

as for unsafe: i think usage is pretty judicious and the data i've seen tells that it's not a cause for concern.