AI cannot replace humans spiteful spirit

The person on the video, known online as Tsoding (or by some as "mista azozin"), was writing a music visualizer program using the raylib library for writing videogames. raylib doesn't have code aimed at UI handling, meaning he had to manage the UI by himself. He likes doing a little bit of trolling, so that's why he picked that title.

Tsoding does by far the most entertaining recreational programming sessions I have ever seen on the Internet, so, despite them being quite long (about two hours), I recommend you watch at least a little bit of his videos/streams if you have time.

YouTube channel: https://www.youtube.com/channel/UCrqM0Ym_NbK1fqeQG2VIohg
Twitch channel: https://twitch.tv/tsoding

If you're interested specifically on this video in question:

The video: https://www.youtube.com/watch?v=SRgLA8X5N_4
The program's code: https://github.com/tsoding/musializer
The playlist containing the making of the program: https://www.youtube.com/playlist?list=PLpM-Dvs8t0Vak1rrE2NJn8XYEJ5M7-BqT

I see your pitiful vibe coding and raise you... SPITE CODING 👿

Spite coding is almost the original coding.
- I have definitely gone into a rageful fugue state and woken up a week later after reworking an entire code base from being an inconsistent mess of slop...
  ...into actually having a common library of functions instead of just rewriting slightly different versions of them 8 times, having those functions only actually instantiated for necesarry classes...
  ...rewriting every variable name and function name to an actually consistent and intelligible naming scheme...
  ... and finally, moving a whole bunch of shit out of some kind of global 'think' type loop that doesn't actually need to be called or checked every goddamned micro second.
  Done that more than once actually.
  Never look inside 'baby's first video game mod' code, unless you have healthy blood pressure.
  But uh yeah, spite, hatred, and anger are indeed powerful motivators for making good code, lol.
  ... so many idiots just jam everything into a global, called every tick loop, and then claim that it just can't be optimized, because "the game engine just can't handle it"...
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.

I moved from Visual Basic (3 no less!) to C because I needed to optimize the performance of a software synthesis (like, sound synthesis) application I was developing at the time (mid-1990s). It boggles my mind to this day how much fucking work you had to do just to create a simple window in C. It instantly made clear why UIs at the time were so bad and I went back to Visual Basic for the UI with a compiled C DLL to do the heavy lifting.

There's no excuse for why UIs are still so bad today.

The "excuse" is more or less the 20 or so replacements that have been made and died. I think Microsoft alone is responsible for 5 over the life of Windows.
We've more or less kinda settled on HTML only because it's already wide spread. But it's not perfect so more standards for the standards pile. Don't worry, react will end up buried by the next thing on the pile eventually.
- We’ve more or less kinda settled on HTML
  It's funny, one of the modern UI glitches that I hate the most is when a long bit of text is just truncated with ellipses instead of the whole thing being shown and you have to hold the mouse over to get it in a tooltip, or shudder actually click on the thing. HTML is great at word-wrapping and allowing the whole UI to "flow" with variable heights and widths as necessary - and yet that is never allowed to happen in apps.

Vibe coding in assembly.

I tried vibe coding a simple assembly program and it couldn't do it

What's this dude talking about?! Everyone knows no one hates React like people who code in React 😂 No one is gonna get pissed off watching this.

I used to be a React dev. The only thing I hated more than React was my boss.
I remember years ago when React was the savior of web apps Swooping in engineers from the clutches of JQuery and AngularJS (not to be confused with Angular 2+). Components we’re gonna make things simpler than the mess of JS files and global state.
And generally that’s true but we’ve traded that off for a mess of hooks and 700 line nested functions in nested functions and obtuse rules that only apply to react and not JS.
Complex web apps are hard.
Do React devs really hate React?
- Isn’t the adage that you either have haters or no users?
- I don't, but it can be really annoying when I accidentally fall for a common trap that I supposedly know how to avoid after all these years! Gah.
- I think it’s great and I’ve been working with it for 6 years. Many issues were resolved over time. We didn’t even have hooks back when I started! Those were dark times. And the new compiler helps with memoization.

Speaking of coding out of spite, is nobody going to mention that his C code features a struct with over 20 fields in it?

Oh man. You should see the source code for IOS (the Cisco one not Apple).
Spent 5 years working on it out of college. I think it's the most cursed code base you can imagine.
Not necessarily because of the massive struct defs everywhere. They are kinda needed when you're running an entire OS as basically a set of interacting Linux processes pretending to be an OS.
At some point Cisco realized they could not compete without putting a Linux kernel as their base. So they basically just copy and pasted the old code written in the early 90s for the IOS and put it into a set Linux processes.
To be clear. It's not just the front end. They didn't really change the code much from the old IOS. Its a cluster fuck of interprocess communication hacks that probably seemed like a good idea at the time.
It is a massive pain in the ass to code because you're basically doing everything on the Linux kernel and then frustratingly have to write the CLIs for IOS just so Cisco can continue to sell their proprietary OS with some of the most unnecessary hardware locks. Massive learning curve for any new engineer.
Literally, no one on the entire switching team knew how to send a message from a specific process to the IOS process. I had been assigned something that needed it. So I somehow figured it out and was "the guy" for that for the time I spent there.
Fuck. I'm gonna start ranting more if I go any further. But yeah, sometimes you need a massive struct because some idiot decided that forcing a closed source CLI on the market is a good idea for profits.
Definitely not a good idea for coding. But you learn quickly that no one actually cares about good code in this industry. There is no time for it. There is no reason for it. Just spit out garbage until it works and your manager won't care.
If you want clean code. Go write an open source project or a personal project.
- I used to work for Cisco but I can't say what it's like internally. Not because of an NDA but because I literally have no idea. I worked for a much smaller competitor of theirs that they acquired, obviously just to remove a competitor from the marketplace. We were all allowed to work remotely but given nothing at all to do for six months and then everybody (except the executives, of course) was laid off.
Sometimes you can't not have a god class (struct in this case). When doing UI specifically, I always end up with one.
You can try using encapsulation to reduce the amount of fields technically, but in the end it's the same amount of information in a single god class.
That's not uncommon, is it?
- Not really, but I'd probably try to organize those into sub structures where it made sense. A data structure holding the UI state and FFT data all flat is kinda messy imo since it becomes unclear what is actually required where.
That's the State struct. Globally accessible, I'd bet

I love this guy he's a fucking freak of nature

Data visualization ≠ UI and signal processing is traditionally done in C

That looks like buttons in the thumbnail, on the left of the visualisation.
I'd say that's enough to call it UI.
UI. User Interface. The bridge between a system and a user. So anything, literally any information transfer from the user to the system OR from the system to the user, is a User Interface.
- A definition so broad as to be useless.
  Is it a UI when someone calls memcpy to move data from a file to a screen buffer?
Would you agree that the dashboard of a car is UI? If so, isn't that just data visualization?
- Dashboard is a UI fed by signal processing code which is the backend.

React Native

can your React do that?? didn't fackin think so dabs mockingly

How I love mista azozin...

Umm this is just being retro. Like using a film camera.

Raw film is objectively higher quality than raw digital. Are you saying that C is objectively higher quality than Rust?
- Excerpt film isn’t objectively better…

There used to be a UI library on the Amiga called MUI.

It used a bunch of C macros to let you define the window and all the controls. Was honestly pretty good considering it was like 30 years ago.

Unrelated but there is microui, a 1100 loc library in ansi C for a basic UI.
https://github.com/rxi/microui
There is another called ImGui which is also cool! Written in C++.
https://github.com/ocornut/imgui
It was a pleasure to work with!
- Right? I can't tell you how disappointed I was to move to a "real" PC later and find the tools to be so much worse. Like you could position stuff with a GUI in VB or Delphi, but if you wanted to resize a window, it was a real faff to get everything moving about as it should.

What's React?

React is what powers your Windows Start Menu.
- Wtf is that real
React is a Javascript based web development programming language developed by Facebook to make pages run faster and better. I learned it as part of a MERN stack full web development course.
- to make pages run faster and better.
  Huh, well that's a funny way of saying "break the model of web page as document and fuck up the entire web!"
- Javascript based web development ~~programming language~~ UI library
- On the other hand React Native is a JavaScript based development language developed by Facebook to make applications run slower and worse.
- Used for rendering UIs on a Document Object Model. JS was a mistake.

this is like when I built that web server in x86 assembly lol.

- This. This project drained my soul lol.
I once write a web app in C, but this terrifies even me.. though Tsoding, the guy in the video, did that, too..
I bet that thing was fast!
- Meh. Even hosting static files in a RAM disk over localhost, you're 99% as good as you can be by using the sendfile() system call. The kernel can copy data from one file descriptor to another faster than any userspace program can. Implementing the Length header is a stat() call.
  If you're not on a RAM disk and not on localhost, then disk access or network throughput will predominate.
  Assembly is not magic go faster sauce.
- I mean, just because you implemented something in a low level lang, it doesn't mean you're gonna have the fastest implementation. Even in high level langs, there's usually heavy optimization involved in things that are done all the time (e.g. web servers)
- Who do you think is better at writing assembly? @harbard@fedia.io or a modern compiler with hundreds of contributors.

Honestly "C + SDL + Lua" is basically the best, most sane"full stack" I have ever used.

IMO it allows for the perfect level of abstraction.

This reminds me. I got a search engine to build.

Lakh views? 🤔

Indian
- More specifically, an Indian divider for large numbers, kind of like how 万 (read 'man') works in Japanese. While Japanese (and I think Chinese) divide numbers greater than 1,000 in increments of 1万, or 10,000, up until you hit 100,000,000, in India, large numbers get split into lakh, representing groups of 100,000.

I'm an elitist asshole and I hate that people say "react dev" when really it's "web dev that uses react"

react devs are not web devs. they're special
Is this distinction really all that useful?
I suppose you could write a react app that doesn’t use “the web”? But you still might just say they are a react developer.
- I think the web part refers to web technologies.
There are also react devs creating the windows 11 start menu.

laughs in Vaadin

I'm still waiting for the day we get a proper alternative to JavaScript.

If I had to make one, it would have a Bash-like syntax