omgbear

I have a gitolite server on a scaleway VPS, but it's only about $1 a month.

Oh man, the music in all their games is top-notch!

Printing the physical zines in exapunks as a reference was very cool, and a good throwback to when games shipped with boxes and detailed manuals.

Spacechem was my intro to Zachtronics, and it consumed me when it came out. The concept of instructions inside the actual work area is amazing and still makes my head spin. I consider beating Ω-Pseudoethyne one of my top coding/steam achievements.

I fell off for a bit because the leaderboard grind against friends felt draining, but rekindled my joy by mostly ignoring them (Unless I'm way out of distribution). I'm so glad Zach and the team are back.

I think my network card does that.

I've got this setup recently via pipewire! With something like barrier for kvm, it's great!

I have an alias on each side -- one gets a new source, the other a new sink.

  audio_recv='pactl load-module module-native-protocol-tcp port=4656 listen=0.0.0.0'
  audio_send='pactl load-module module-tunnel-sink server=target:4656'

Left to his own devices, I found Claude liked to copy the code under test into the test files to 'remove dependencies' :/

Or would return early from playwright tests when the desired targets couldn't be found instead of failing.

But I agree that with some guidance and a better CLAUDE.md, can work well!

I have the Kinesis Advantage 360 which is split but has all the non-numpad buttons.

I do spend lots of time in Emacs, but also use it for plenty of gaming. Just remap in-game to ESDF and only use the left hand. (Or set up layers, but I'm generally too lazy for that).

I think the thumb clusters are great, but may not be to your taste. I'm very happy with it, but have used various iterations of kinesis keyboards for a long time now.

Semi-related; One of the Zelda DS games required you to close the DS (so the top and bottom screen met), which moved a mark from the top to bottom screen. Was infuriating for me, only figured it out after closing the DS in frustration. Not really something you can do with modern portables, but clever in retrospect.

Yeah, having all the defaults for system keybinds be on super is really nice.

It feels like macosx lucked into this with their historical use of command as the modifier, but I also wish I could easily replicate. Instead I just go and remap a few line ctrl-a in KDE settings and otherwise try to live in emacs.

It's harder to learn the impact of your design decisions -- Seeing how software evolves to meet changing business goals and how the design choices made play out in the long run helped teach me a lot.

Coming up with a neat API that turns out to be difficult to modify in the future, or limiting in ways you didn't imagine would when writing it is a good learning experience.

Or seeing how long a system can survive growing usage -- Maybe a simple hack works better than anyone expected because you can just pay more for RAM/CPU each year rather than rebuild into a distributed fashion. Or the opposite, maybe there's some scaling factor or threshold you didn't know existed and system performance craters earlier than predicted.

I've thought about this a lot in relation to typescript over the years and had various opinions -- For some time I thought it'd be better if there was an implicit `await` on every line and require `void` or some other keyword to break execution like `go` in Golang.

But, eventually I realized the difference in pre-emption between languages -- Go can (now) preempt your code in many places, so locks and thread-safety are very important.

The javascript runtime only preempts at certain places, `await` being one. This means I can know no other code can be running without explicit locks around all critical sections.

Finally understanding the trade-offs, I no longer am as frustrated when recoloring a bunch of functions. Instead, I can appreciate the areas where I'm not required to lock certain operations that I would in other languages.

I was just trying this -- you can even do in-browser typescript compilation.

But I was missing hot-reload -- Constantly switching between the browser and my editor.

A refresh timer helped, but wasn't quite the same snappyness.