@quazarsamcoupe @brouhaha @janamarie I saw a future of eventually needing a dedicated EAGLE laptop with old versions of everything if I didn't make the switch, so I forced myself to do it since I didn't want to be in that boat.

I still don't love the linkage between symbols and footprints, EAGLE's way of doing that seems better/cleaner to me, but overall after doing a reasonably complicated project from start to finish (https://hachyderm.io/@sen/115505095475507161) I like KiCad now, it's got a bunch of quality-of-life improvements over what I was used to and I'm up to like 85% the speed I was at before, which is fast enough to not be annoying.

I was musing on this because, as a for-fun thing, I'm rewriting some complex Go code in Rust, replacing ornate goroutine concurrency with compiler-managed concurrency with async... with no runtime.

It turns out the Go code is chock full of data races. I'm finding them because they're compile errors in the Rust code. So it's very nice to be able to draw lines around "this bit is async but not threaded" vs "this bit is not even async."

This turns out to be a surprisingly complex computer for its day, with something like four independent CPUs.

I'm awfully tempted to take it apart, but that may have to wait.