Notices by Hailey (hailey@hails.org), page 2

everybody wants to be the guy to write the filesystem that solves data loss once and for all because it would look good as hell on a resume

lot’s of people clowning on google ai today but i won’t be knocking glue pizza til i try it

from https://isocpp.org/files/papers/P2809R3.html where the C++ committee has just adopted a proposal to make some infinite loops not UB

what on earth is going on over at C++

are they ok

@tursiae totally, and it's just not how the social contract works. I am giving something to you out of my own kindness, take it or leave it, but placing some burdensome task on me is the exact opposite of reasonable

nothing ruins my motivation to send fixes to your open source project more than to ask me to sign a CLA for it.

sorry guys I'm just not that interested in reviewing a legal contract just to improve your software for free

there is a certain originalist leaning among unix people where they believe that unix was a perfectly conceptualised design from the beginning, and that all we need to reach unix nirvana is just do things more like we used to

of course the reality is that everything is informed by the realities of its time, and computing these days looks nothing like what it did 20, 30, 40 odd years ago. keep what's good, chuck out what isn't

the corollary to this is that we have a much better understanding of the domain now.

we scoff at terrible old APIs like libc's gets, but at the time we just didn't really know better. now we do, and it's easy to see why an API like that can't be fixed and shouldn't be used.

by the same token, it's unlikely that more complex constructions like an init system or build system from back then is really all that fit for purpose today. we have more suitable conceptual models for understanding and solving the problems we work with now than we did back then

despite that whole “everyone thinks they’re an above average driver” thing, having driven the Hume a few times in recent months, I’m convinced that if:

- you keep left unless overtaking
- you turn your headlights on when it’s wet
- you generally use your headlights to be seen, not just to see

you are comfortably in some upper percentile of drivers

the javascript people have discovered ASP.NET

https://twitter.com/AdamRackis/status/1717607565260124613

Introducing Bark! Low-latency multi-receiver live-sync lossless audio streaming for local networks. It's like Sonos, but open source, so nobody can brick your devices remotely. It's also written in Rust :)

https://github.com/haileys/bark

It sends 48khz uncompressed float32 data over UDP multicast. It can achieve playback sync to within hundreds of microseconds in ideal conditions, and usually to within a millisecond.

I've been working on it in my spare time over the past week, and I'm pretty happy with how it's shaped up. I have three receivers setup and it works remarkably well at keeping everything in sync as I walk around my house. For now it only really works on Linux, and supports Pipewire (and Pulse in theory), but there's no huge impediment to making it truly cross-platform.

It also features a fancy live stats subcommand, which can used on any computer in the same multicast domain to watch the status of the stream cluster:

Gaming

Can’t wait til this catches on and every profile edit page has a reminder that people want me dead

Coward shit from GitHub