Is this the Future of Programming Languages?

44:30 "rekindle the enjoyment of programming and the believe what you are doing is important" (paraphrased for conciseness) – I changes vocation because the industry sucked the soul out of me and I didn't want to be part of that any longer. Personally I witnessed how software is used as a tool for legal extortion. There is only so much the consciousness can bear. As this is the prevalent usecase I didn't see where to fit in, so I quit. Worked in or for startups, academia, insurance and farms. Everywhere the extortion is somewhat similar and the last experience with the farmers and the state of repair was my final straw to at least not be part of the problem.

A year or so ago got to HMH and with aoc to you as I needed to scratch an itch. Casey like you cutting through the BS really put things into perspective. But you are keeping it more approachable or understandable (hard to put in words). Your take on keeping it simple, not over-complicating or not over-abstracting and exploring ideas with it recreationally was what I needed to hear and see, as I couldn't put it into words myself. Any it got me back to code again without monetary incentive just as a real hobby. Thanks.

Really like the explanations of why you like to do things. For example at 1:18:30 the Expr_Kind and Expr_As tagged union. Or your take and exploration with nob is just the right thing, like here to use nob for its very useful platform independent functions.

My only complain is there isn't support for WASM. If there was that would be genuinely awesome.

Yes, another language. That's why I initially subscribed to Tsoding Daily: because of the language creation content. 🙂
What about creating a minimalist yet useful language? Not another Porth, though.
Maybe a language that includes just: if, elif, else, while, variables, and functions. That would essentially be Turing complete. Perhaps arrays could be added, but that’s about it.
The goal would be to have as few keywords as possible.
Or, implementing some sort of old-school BASIC could be fun. You know, the kind without proper loops, relying solely on 'goto' and 'gosub' for control flow.

It looks like the trend is to either slap your wrist before you even start or try to read your mind before you code. Basically, it's getting to the point where you're almost scared to hit the keyboard, lol.

"I know that not everybody masturbates to simplicity as much as I do" 🤣 I like simplicity too. 👍

Repo for the code?

Zozin learned x86 calling conventions and called some raylib functions, now he is assembly programmer. He doesn't even read the main() function in stb_c_lexer.h that shows how to use it and already has a print_token function but he calls it a bad library. He used to be more humble about stuff he doesn't know instead of just talking shit.

51:35 Not only is raylib pretty easy to implement and work with, but it also has bindings for basically every language under the sun. It is pretty awesome lol. The fact that you can interface with it surprisingly easily from Assembly is icing on the cake. Name another framework that can do all of that! Lol

around 1:51:20 . Absolutely true. The React sorry, the Rust developers got on a path where they thought it was a good Outlook(pun intended) to the future. But in many cases this looks like patronizing the Rust language user. And another disturbing point: That "thing" we are talking about here is actually called "clippy". You remember that annoying BS from the Windows/Office 97/98-2003 (internal name "Clippit", publicly used was "Clippy") that permanently wants to "fix" and harass the User with its demands and "well-intentioned advice" = YOU!? So, the question is: Are the Rust developers comedians, or are they outright evil? Hehehehe:)
(Switching of that clippy BS, including warnings needs its own manual itself, LOL. And wow: Entries in the actual code. Like "#[allow(clippy::wrong_self_convention)]". What a joke!:)
Or, examples:
rustc -A dead_code / RUSTFLAGS="$RUSTFLAGS -A dead_code" cargo build

look into "RUSTFLAGS=-Awarnings", when you are down on your knees:)

Edit: I think this plague was introduced by languages like C# and their extensions/helper, like StyleCop, etc. C# a wonderful but also horrible language. A mish-mash and disaster that actually needs such documentation helpers and external styling tools, because of oversights of the language developers and what this abomination lacks of features. Also "Design Principles", all those fancy hard rules and all this great advice and guidelines that suffocate the programmer like a corset. Test Driven BS. And last but not least: effing AGILE Brainfart … Not only "should" … your "friends" will clearly suggest that to you! … the professional programmer follow all those rules and "ideas", but also the hobby programmer, because it is better to learn it the "right way", yeah … surely it is. Maybe you should question your friendship with those plonkers?!:)

All what I addressed has its use and can hopefully be switched off. Nonetheless forms every single piece of this modern infrastructure together not only a great toolbox, that may help you and give you good advice, but it also is a tool that easily allows to suppress individuality, own thoughts and worse: critical thinking. It also may have negative effects on creativity, deep knowledge or deepening your knowledge (WhyTF shudd I leearn orthUgraphI, whenn I has audo-corect? LOL) and is always biased in favor of the mainstream opinion and established values (especially A.I. BS, which is by design an horror example on that matter). Oh and all of those nice anti-democratic, anti-freedom, anti-artist, anti-human features are ENABLED BY DEFAULT! (Ask your management if he can wipe his own a… *g* )

Odin uses LLVM indeed, but I think they're planning of getting rid of it. Ginger Bill has stated in interviews that LLVM is the bottleneck of Odin's compile times.

ParserC pronunciation strikes back 💀

You should work at a promising startup with good ESOPS.