I prefer the term “spite-driven development”.

I wrote an SDL replacement but worse after SDL refused to work with audio streams for me even after a week of googling, it took me the same amount to get it work with WASAPI directly as looking up audio streams, instead of the many easymp3playback.dll type solution. Another one week was making ALSA working. At least it’s in D, so I have an easier time with development.

I also almost was involved with a YanSim clone development called “Love Letter: My True Feelings”, but shit just started to hit the fan (character designer just left), so I decided to not get involved as a coder.

It’s not blue cheese! It’s mimonette, filled with bugs!

It’s similar to stealing code directly from Github, Stackoverflow, or some similar site, except you beg the chatbot to fix the bad code it spat out.

So is let in some languages. In Rust, you have to constantly opt out from immutability with let mut, which makes writing more procedural code feel like you’re fighting with the compiler, and otherwise I don’t really see the rationale behind full functional coding. I only had a bug caused only once by unwanted mutation, the hardest part fixing it was to learn the proper use of my debugger tool.

Good, now invent a keyword for variables you don’t want to declare the type.

auto. Also in D, you only need const if you don’t want to specify a type for a constant, the compiler automatically inferres it to you.

Function declarations can be easily decyphered from context, no problem.

I can draw programmer comedy at a relatively high speed, at no greater cost of water, power, etc., than I’m already using to live.

Speaking of which, I probably should draw some of my ideas…

We need to bring back system development! Not everything needs to be an electron app!

That’s why you self-host!

Basically by transpiling, I’m converting commands to a format with absolute time position rather than the current relative one, so I don’t have to deal too much with the relative wait commands, seeking would be easier to implement rather than one using relative positions, and I wouldn’t really have the issue with inserting extra commands when relative jump commands exist. As I said, the textual format already have some macros that function in similar vein, such as the [0]: note 0 0x7FFF s.:a-5 macro, that automatically inserts noteon and noteoff commands at the appropriate places when processed, and also jump commands use labels similar to some unstructured programming stuff.

I think I’ll try to work on a game for a while, then peek into someone else’s code that had similar problems on how they actually did it.

As for the MIDI 1.0 limitations:

• More than 16 channel implementation is a bit tricky, and I really didn’t want the composer to rely on automatic polyphony handling real time (which would likely conflict with sound effects, etc.), nor wanted to deal with that too on top of everything else.
• Precision issues with Control Change commands, and I wanted most if not all things to be controlled via MIDI easily rather than aggressive preset swapping or SysEx commands. Some special functionality still uses SysEx, like global waveform changing in the FM synth, where you basically command to change one of the 128 possible waveforms to be changed to a custom parameter-generated one. The only thing that cannot be done from MIDI is specifying path for files, which is intentional since it would mess with real-time features.
• Adaptive soundtracks. To my knowledge, there’s not a whole lot of formats for this, let alone ones that are known to be open, and even then many don’t go much farther than maybe mixing a few extra tracks they can swap-in, mute, etc., while mine could manipulate instrument parameters, pitch, etc. Instead of going the route of downloading easymp3playback.dll and easymp3playback.h (originally I used sdl-audio), I went with my own audio solution, and since my engine already was custom tailored for “retro pixelart”, I doubled down in that direction, and went with a pretty lo-fi sampler and an FM synth so far.

I personally needed the Pi for its Arm architecture.

Sopposotoro

This will just lead to more low-quality code.

I instead recommend using more productive languages. I’ve heard many good things about Rust, if you can deal with the OCaml-like syntax and the functional paradigm by default. As an alternative I can also recommend D, it doesn’t have the “const by default” issue of Rust (functional paradigm is still possible, you just have to opt-in), a very C-like syntax except more refined, memory safety features (3 levels of memory safety + arrays with bounds checking), at the cost of a bit hard to opt-out garbage collector (you also have to opt-out from many D features and the already scarce library ecosystem).

I did the “do something else”, and I’m still stuck…🙁

Functional: car, but without moving parts.

What no type safety does to an MF…

That’s like:

Car with the dashboard and the switches all ripped out >>>>> A normal car >>>>> A stereotypical Arab sheik car, with a solid gold dashboard and a fancy infotainment system

Kate >>>>> Vi$ual$tudio

Should I rewrite it in D, so not everything gets rewritten in Rust?

Rust: you’re an annoying nerd

D: you’re a nonexistent nerd

Weirdly enough, when someone asked an LLM for an OpenGL grievance for me, first it just recommended to use GLFW or SDL for the task, both of which I didn’t want to use (GLFW controller handling🤮), after that they got an answer that just bugged out on most WM.