model-view-projection VS miniaudio

> Copilot is a horrible crutch. I will never use it, because I know how to read the documentation/source and write my own code.

I think it depends on how you use it. I never let Copilot make design decisions, because it kind of sucks at that, and it that carries a lot of risk of wasting more time than it saves in the long run.

But there are some tasks that I think it's well suited for. In a recent commit[1] to one of my side projects, I swapped out one graphics library for another, which involved replacing a lot of library calls and would have been very tedious to write by hand. I turned Copilot on for this, and after I did a couple substitutions by hand it was able to do most of the work and was easily a net positive.

For my own usage, I keep copilot off in my text editors, and opt to flip it on with a keybinding if and when I have a tedious task that I think it would be good for.

[1] https://github.com/jpe90/model-view-projection/commit/1ed4fb...

I used Nuklear for a little demo project I put together to wrap my head around matrix transforms in graphics programming. It's very easy to use and pleasant to work with!

https://github.com/jpe90/model-view-projection

Unfortunately, I can't currently capture any videos (I added miniaudio.h to play back the Jurassic Park theme song) since I had to move my mom into my home (she's getting a divorce from her narcissistic husband soon and the guy lost his marbles and locked her out of her own home) and it's late at night currently.

miniaudio - so far the best entry in cross platform audio. It is a stack allowing to use device alone, decoders and mixers, or node based engine for sophisticated audio processing. Extensible where it should be. Written in C, so there are no creature comforts of having C++. Aways can be wrapped to get advantage of RAII.

So, I wanna implement this library to the source engine. Is that possible? And also, since source is based on SDL, is it possible for me to implement Nuklear on my source game?

The most straightforward lib for this is miniaudio. It's straightforward,l to use and easy to integrate into a build system.

You give little clues what this is… so cl-miniaudio defines CFFI bindings to https://miniaud.io/ which is "an audio playback and capture library for C and C++. It's made up of a single source file, has no external dependencies and is released into the public domain." and is cross-platform.

Get the update on GitHub: https://github.com/mackron/miniaudio

* Miniaudio - A single header file audio library https://miniaud.io/

Both (actually, not just three systems) cross-platform.

For their design and cross-platform support they make for great bases for Go libraries, unlike most C code out there.

I've used this library before: https://miniaud.io/