@VTHistory25 I think we should be teaching philosophy throughout the entirety of high school. We need to teach people how to think, but of course that's the last thing a politician would want so little chance of that ever happening.
@falco_girgis@tsoding It was annoying actually. chibicc advertises support for C11 atomics so I figured I'd just use that, but it turns out it has a broken implementation so I had throw that work out. But what it does have is an atomic exchange and CAS so I built everything in terms of those.
Support for yet another compiler added to miniaudio. This time chibicc. The support matrix continues to grow! Thanks @tsoding for reminding me about that one!
Simple build system as usual. Just compile and run and you've got audio. No dependencies needed.
@falco_girgis@tsoding Only problem I had was getting atomics working. I had to add a new atomics backend specifically for chibicc. But atomics are always the hard part for new compiler support so nothing unusual.
Not having dependencies makes things so much easier to port to new compilers though.
@falco_girgis The more I see these militantly anti-AI posts, the more I think it's just insecurity. It's too hard to raise themselves up, so instead they just cut it down to their level. It's so pathetic.
A good use of AI is good, a bad use of AI is bad. I think this is a great use case!
@atoi6664 That's on my radar, and I'll definitely give a try, but I like the debugging UI to be tightly integrated with the development environment so I've got some reservations with how it'll integrate into my workflow. Definitely worth experimenting with when it's out though!
I just tried using LLDB instead of GDB (via the CodeLLDB VSCode extension) and holy hell I've only just now realised how bad GDB is!
I assumed my program was starting up slow because I hadn't optimized anything yet, but it was GDB the whole time! Now I feel very silly.
I've been using GDB since forever because it's kind of the "default" debugger on Linux and I just rolled with it without giving it any thought. That was a mistake. Now my turnaround times are so much faster and everything is snappier. No going back to GDB for me!
@valigo This 100%. People don't understand the importance of a simple build system. My most popular library is ~100K lines and you can just add the source file straight to your source tree and compile. No need for a build system. This is one of the best decisions I've ever made.
When it comes to errors when trying to launch a program, Python is so disproportionately represented. I cannot think of anything that causes as many problems on my computer as Python.
Another day, another Python related error. Either stop using Python, or bundle it with your app so it's all self contained!
Do not ever require the user to install Python separately. This disconnect causes so many problems!
@Bobini2@raysan5 It's one reason, yes. Too much bad code.
Also, as a solo developer my projects tend to be very personal, and often times large PRs include things that I just don't care about nor want to spend time maintaining so easier to just ban it outright. Too easy to be influenced by a PR.
Unpopular opinion:
AIโs worst code doesnโt even come close to the absolute garbage Iโve had to clean up from humans.
Post your worst inherited code story below๐
I have so much gratitude to people who wrote extremely complex software character-by-character. It already feels difficult to remember how much effort it really took.
Thank you for getting us to this point.
How do I stop GDB from doing this stupid bullshit?
Downloading 531.44 M separate debug info for /usr/lib/libLLVM.so.22.1...
I don't want to download half a GB just to debug my program!
I've tried adding "set debuginfod enabled off" to .gdbinit and it doesn't work. Any ideas?