When I saw the post the Newton Virus was the first thing I thought of. Thanks for making it. I remember showing my family the video and remarking about how cool it was.
As others have said, a full size HDMI port would be nice. However, I've been very satisfied with my JetKVM. I was about to order the GL.iNet KVM they just launched, but I ended up picking up another JetKVM now that sales are open.
My use-case is that I have it connected to an Raspberry Pi which I use to test the RPi builds of my application. I just ordered a second to connect to a mini-PC which is the minimum spec supported by my application. It has made my testing experience very smooth.
They were definitely my fault, to be clear. There was a crash at launch (I don't remember the cause exactly) and being unable to copy to clipboard when using the wlr-layer-shell extension. Those likely affected other compositors, but I did not catch them on Gnome when I was doing the majority of development and testing.
I can absolutely echo your sentiment. I recently released some software which has Wayland support. Immediately, I got some bug reports from Hyprland users so I setup a partition with EndeavourOS + Hyprland to work out the issues. I was pleasantly surprised to find that, as you said, the defaults are nice. Configuring it was a breeze as well. Now about 2 weeks later I am daily driving the system I setup for testing and am working to switch fully to it from macOS.
Say what you want about Tailwind's usefulness, but the author's claim in the section titled "Rule sets" is objectively false. In the Tailwind documentation they mention the @apply directive which allows you to use Tailwind's styles in your primary stylesheet.
In my own project, I moved to Tailwind recently and found @apply to be very useful. I experiment with the inline styles and move them to a CSS class when (and if) needed. Additionally, the Tailwind CLI translates the states like hover: and active: as well. I personally have found it super convenient.
I primarily do macOS development work and use Instruments for profiling, but have been working on Linux a lot lately and Hotspot has been pulled out a lot over the last few weeks. Highly recommended.
macOS 14.2 implemented something like this in Core Audio, but it is not user facing (and also documented extremely poorly). You can create a "Tap" that can capture audio from a particular application, or subset of applications, or an output device. This can then be added to a private or public Aggregate Device (depending on the Tap being private or public).
IMO cdm is a great resource for musicians. I have been reading it for close to a decade and have found many cool tools and learned a lot from it. I particularly like the DAW update summaries.