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

• commands to move a window up and down the stack
• commands to spawn a window in a location next or previous to the currently focused window in the stack where the window to spawn is given as an argument.

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

Many functions in the kernel allocate resources that are not cleaned up in the case of an error. We should analyse the source and fix where this happens, adding tests as appropriate to make sure this is maintained.

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"

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

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