Waybar keeps crashing when clicking the idle inhibitor module. On sway it seems to work so that leads me to believe it is a problem with river not implementing the idle inhibit protocol.

I'm fine if you decide to not support the protocol, but could there be a little note about

Sooner or later we will need to add tests to check for regressions.

I propose the following three kinds of tests:

• Function unit tests (mainly for the parsing functions)
• I/O testing: simulate a client sending requests from a different process and check the responses are correct
• Internal state testing: simulate a client sending requests from a different process and check our intern

Replace usage of @bitcast with safer alternatives, it needs to work in debug builds

Currently, the driver will assume the disk is good and the boot and FAT sectors are valid. If not, then will throw and error. FAT32 has backup sectors the driver can parse before erroring. Possibly try to copy the backup to the main sectors.

Needing to load ROMs from the filesystem every time is really annoying. We can easily cache them in localStorage or something.

Also the load cart UI should be rethought to allow for "included ROMs", "saved ROMs", or "load from FOO"

The dream would be to have Python like "batteries included" stdlib.

In the interest of adding additional ideas for "good first issues", I would like to recommend potential new zig users to look into adding new flags for our applets. Please remove this issue if this post is redundant, but I think it is a good issue to have up for a general task/reminder.

One flag I would love to see implemented is colored formatting for ls, but there are many possible flags th