>buy new USB-C cable
>ask the manufacturer if it's for data or just power
>they don't understand
>pull out full illustrated diagram explaining the difference between USB3.0-capable data and just power
>they laugh and say "it's a good cable, ma'am"
>plug the capture card in
>USB 2
the WASIX effort is actively harmful to Wasm/WASI and I hope it is forgotten with the rest of Wasmer
my view is: don't use it in your applications, don't implement it in your runtimes, don't contribute to its organization
@micko_mame the reversing part is long done; what's missing is cleanup and deduplication of the data + documentation (which I never finished because of lack of interest)
the feminine urge to just link a soft-float library because language-level float support is a complete mess that cannot be relied on to be deterministic in any way
me: okay, I'll carefully write serialization code for f64 so that it comes out bitwise-identical on the other end no matter what
i386 ABI: lol just returning a float from a function can and will change its value sometimes and there's nothing that can be done about it
current status: had a dream in which my window manager kept segfaulting and I got pissed off and decided to switch to a new one
I'm coming to the conclusion that the dream me was right; what are some nice tiling window managers that don't require much babysitting?
@meithecatte here: 2kLOC of custom wrapper types over Vec, IndexMap, IndexSet, BitVec that can only be indexed with the right newtype, plus a newtype-generator macro that uses NonZeroU* types internally so it ends up with a niche that can be used for Option<> layout optimization