//
sign in
Profile
by @danabra.mov
Profile
by @dansshadow.bsky.social
Profile
by @jimpick.com
AviHandle
by @danabra.mov
AviHandle
by @dansshadow.bsky.social
AviHandle
by @katherine.computer
EventsList
by @katherine.computer
ProfileHeader
by @dansshadow.bsky.social
ProfileHeader
by @danabra.mov
ProfileMedia
by @danabra.mov
ProfilePlays
by @danabra.mov
ProfilePosts
by @danabra.mov
ProfilePosts
by @dansshadow.bsky.social
ProfileReplies
by @danabra.mov
Record
by @atsui.org
Skircle
by @danabra.mov
StreamPlacePlaylist
by @katherine.computer
+ new component
ProfilePosts








Loading...
this whole thread resonates with my view so much. writing haskell flavored rust lets you be confident & performant without overthinking, I'd gladly switch to something that hits that intersection better
picked this back up and turned it into a tool that can estimate within 10% the compile cost of functions. Think of it like cargo llvm-lines that rolls up to functions in your crate
18h
18d
stellz
xav
fp has a rep for being for smart people, but tbh i like it because i am old and dumb and sleepy and high, and it doesn't require me to think as much about what's happening. i know that what happens in my current scope, stays in my current scope. that's room freed up for another bong rip
prototyped a little tool here to break down the sizes of large futures. My objective is to help figure out how to reduce compile times in async-heavy projects by telling you which futures are worth erasing. Might work on surfacing call-graph depth next.