Me when i wake up: looks like we are alive

"LLVM is the React of compilers" hahaha I loved that one, it's a great analogy though

I'm surprised to see my name here in this KZfaq video at 38:30 +/- along with my old PACC project. 🙂

"LLVM is basically the React of compilers, minus the toxic community."

Mr. Zozin congratulations on 100K subs! (it's funny how the "vod's" channel has more subs than the "main" channel lol). Anyways i just want to thank you for being the cool guy that you are. I really love programming, but i cannot keep programming much on my own because i get discouraged or distracted really easily. But watching your videos give me motivation to code again. So thank you really much! again congrats on 100K (you deserve more than 100K). love from maldives 💖

100k subscriber well deserved, amazing content as usual!!!!! You're making the difference my dear friend!

Your videos remind me why I fell in love with programming. They're also more informative than most of the university classes I recall. Good for the mind and the soul.

Love the rant about the lexer, that's a reason I usually just end up writing all my own stuff... A friend of mine always like to tell me "why do you waste your time writing your own stuff when there are perfectly good libraries you could use", I tell him A) what fun is that and B) stuff like you've just found. lol :)

I saw QBE in the recording of the Hare stream and was immediately excited... last time I build a toy language was in college like 18 years ago. But I had to use LLVM when contributing to one or two other language projects and it definitely felt too big (mentally and diskwise...). Cranelift seems like another simpler option but QBE takes it to another level.

Hey tsoding, I was thinking that maybe I'm the only person watching your videos from Iran :] Thank you they're great and worth the spended time

9:52 Vim actually has syntax hightlighting for Hare out of the box. Can your emacs do that?

congrats on 100k❤🎉

Perfixes are (for php case) for speed up parser/lexer interpreter

1:48:02 Really good perspective on lsp that I had not considered. I think this should be it's own clip.

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.

4:59 - in ideal world people program in python because it meets particular speed requirements, not because nobody cares about performance at all.

The most genuine channel I've ever seen on youtube.

2:30:00 that in particular looks like a bug: on in stb_lexer.h line 565 it sets string_len to n (aka 0) before the loop looking at the characters, but then doesn't set it after the loop when it is done. moreover it reuses the string storage, so if you have 2 different identifiers it the string view of the previous one will get overwritten.

9:45 "let's actually set the highlighting to javascript" LOL

I am putting QBE under “I want to build compilers, but I have no patience to try and learn GCC and Clang because they are somehow longer then Wheel of Time” I even have the dragon book. Lets do this.

From the user perspective prefixes were useful in the absence of LSPs and other code analysis tools to understand what you are looking at, it's for the same raison we see p_*,m_* conventions in old codebases

13:40 zozin talking about storing names as various types, like tagged unions, in tables while I'm in the process of creating a tagged union to put in my symbol tables.

This guy is cool, knowledgeable, funny and one of the best teachers i've seen. Not bad at all :-) Edit. Aaand the expression compiles to 69, also known as urmom 😂.

first time i've seen a tsoding vod before it got auto-generated captions

3:43 I think Zig used LLVM in the past, but will transition or has transitioned to being entirely self-hosted Rust does use LLVM though

how did i never notice the 'Porn Folder' in the lower status bar

3:51 yeah, glad i guessed the problem with llvm correct. huuuge size. the talk about zig (with trans) mentioned it - "it takes 4 hrs to compile"

QBE stands for query-by-example compiler? sounds pretty poggers.

awesome brother

zig used to use llvm(still do i guess) but theyre in the process of migrating into their own backend for reasons similiar to yours which i find very exciting

Congrats to 100K!

Would love to see how to compile a toy language from unusual paradigm, like purely functional or array language.

You are insanely good at programming.

The begin end convention also allows a nice way to describe an empty range. begin=end. The begin end token's does not need to point to anything real. Null is fine.

Yoooooooooo!!!! zozin fam 100kkkk congo 🎊🎋🎉🎈✨zozin

Make a fast compiler for a small scripting language? Such that it is super-easy to integrate into C/rust applications like games, but does not do any IO (such that it is designed for embedding into other apps from ground up, but compiled into native code).

Nooo....don't let it leak. Sure the OS cleans up for you most of the time. But sometimes someone will want to build your code to run in an environment where it does not. I had this problem with a compiler for the Spin language for the Parallax Inc. Propeller micro-controller. I built the copier with Emscripten into asm.js to run in the browser. Problem was everyone it was run it leaked and eventually crashed the page. The emscripten run time did not clean up. Luckily I convinced the author to fix that leak and all was well eventually.

31:05 It isn't. That's why Austral (and an earlier version of C++) generates C code before compilation with gcc

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

Great video! Which font do you use inside emacs? It looks really cool :)

That is a very big folder! 58.2gb!

Thank you....

Congratulations to 100 000 subscribers. You deserve that and even much more IMHO.

My couple of cents: 1. Using "$" and "%" in IR is justifiable - as a language writer, you can define symbols without any keyword clash. Example: write a function named "$export" which compiles to a symbol named "export" - perfect valid as a C function, but it would be a mess if QBE IR had no symbol prefix. 2. That "string_len" in the lexer probably makes only sense if you parse a literal string. I haven't checked the code, but I guess literals are pointer-copied to that "string" attribute - that would be a optimisation to avoid copying/strlen a string constant. That's why I favour writing my own libs when programming for fun. There is always some nasty surprise from an undocumented/unexpected behaviour that takes hours or more to troubleshoot.

BNF is not useful? I grew up with yacc and bison. There is no better way of understanding the syntax of a language than the condensed DESCRIPTION of the language in that metasyntax form. Okay, with the BNF of C++ (which isn't possible to describe C++ in that way, as a sidenote) your head will blow up. But you do not have to look at all the "arms". You can slowly crawl down from up to the bottom, which also represents DETAIL. Go as far as your head-internal-pressure allows. Don't be afraid!?!:)

where I can see the source for nob.h?

I've been trying to explain that a pointer is just a number to all the new developers i work with for years. it sometimes takes a while to stick.

2:44:30 you have to copy the constant into that temporary. you can do this like `%s0 =w copy 3` or whatever. I got stumped on this too when trying to figure it out for my own language edit: nvm you figured this out later lmao

2:37:06 hm.. stacksize-=1 hm, why can you reassign those stack slots in ssa.

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.

Is there chance to see more hare and qbe on this channel? And congratulations on 100k!

Repo for the code?

Wat up with that regex-escape codes combo. New hax with old techniques, I like.

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

start == (break main && run)

A hard watch.

Sounds good? Sounds gucci? Sounds atamagucci? Let'sa go!

I wonder if QBE could be used to compile GDScript and massively benefit the Godot engine.

The keepeer of enjoyment through programming. The saviour of fun through making computer go brrr. The code clown.

Zig uses LLVM but they at one point said it will eventually not use LLVM.

The problem with QBE is that it doesn't have a way to add debugging information. This makes it a no-started for me as any language that can't be easily debugged is useless IMHO. I know they are working on adding some support for it.

cuik tb (tilde) > qbe

The only problem with qbe is no windows support which is its only real problem

When your backend is essentially voodoo for most developers.

this seems much more easier to use than llvm

*ParserC* pronunciation strikes back 💀

You should work at a promising startup with good ESOPS.

"Who TF is Alexa?" **singing** hehehe

I have no idea, but having developed debuggers, I'm guessing @start either means that the function prologue is done or that it starts there. Also you're not supposed to write IR directly. You're supposed to translate your higher level constructs, into IR. The QBE IR looks exactly like LLVM IR (also looks a bit like wasm if i'm not mistaken, which also is just another form of IR).

Zig uses LLVM indeed, but they are working on their own backend and their plan is to throw LLVM, mostly because it's slow and bloated. And they might succeed, they are very focused on that

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.

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** )

you gotta enable sub-pixel anti-aliasing

the non-zero is not non-zeroing 49:42

37:00

You should be fair in regards of LLVM. OF COURSE it is "bloated". Look at the options and possibilities it gives you. For me, targeting X86, ARM, MIPS and RISCV this package is a gift ... all under one hood and standardized. Oh and BTW I am on Gentoo. So don't tell me what is "Bloat" as I have to recompile LLVM every time when there is an update. Oh ... and who would've guessed it? I compile only THE BACKENDS I USE! You didn't know that this is an option and absolutely speeds up compilation times and also space requirements? Now you know! For others that get a binary package ... WTF? You install that in seconds. It is 2024, so who cares about 1 or 2 GB disk space? Period! There is nothing wrong with using a dedicated solution like QBE or specialized compilers, f.e. for older hardware or electronic projects, etc. But that is a question of using "the right tool for the job", which is YOUR responsibility (and shows your expertise ... or not). Acting like a child and beaching(spelling) around about general purpose compiler infrastructure, which is OF COURSE big in every aspect, doesn't help you in any way besides getting your steam off. There are better ways, like touching grass, or getting laid, don't you think?:P P.S.: Oh and this comment is not directed at Tsoding. He is joking. "... React of compilers", hehehe. So do I. This comment is for YOU. Yes you, angry looking motherboard who didn't even understood my "tool" analogy, with that stick up your back:P Have fun coding and thanks for the great video!:)

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.

54:00

I am a simple man, I see a yt video on QBE and I press the "thumb up"

49:42 nice non 0 exit xd

qbe outputs pretty bad assembly though, unfortunately

yoooo

1:12:57 classic segfault face

1:55:55

w humor.

@TSODING you cant make a new language that doesnt have createWindow in 2024¡

MLIR+Autotune FTW

0:15 Hare language: "fn"

skill issue, dab dab dab

Would have needed this 15 years ago, when i had to use C as a target output. How does it handle stack unwinding, multiple results, stack switching and all this things that are not possible in C? Everything is easy when you have an add function. But C itself is limited and unfortunately had more influence to language design then necessary. In the good old SPARC register file days you had upto 7 return variables build into hardware. Also how is this working with incremental compilation? Recompiling only when offset values change? Okay, this one you can add with comments and string compares as i did, but whats about linkers? Unfortunately LLVM is not language independent for a decade or more, its total focused on creating a C++ compiler (or something like this). Linking was the main problem i had with my language. Like Jonathan Blow, i was writting on a system that should build one milion line program in under a second (incremental) and five seconds (full compile). Got the compiler that way but failed on the linking terrible.

Not a Lisp, so not the future. Next.

I would love to see you build a language with QBE as backend

No the best is QBasic

around 1:49:00 . If you do not like LSPs (Language Server Protocol implementations, Immediate Error/Syntax Helpers), or syntax-highlighters, tags, clang-format and all of that fuzz ... I have a REVOLUTIONARY NEW IDEA here for you: SWITCH THEM OFF! (Instead of moaning and whining around **g** ) I know, I am the world famous inventor of off-switches(ROTFL) and such a concept lies in my nature. But I shared that idea with you all. Now you know!:))))) No offense, Tsoding! I'm just kidding you:P

Please don't create any more programming languages, reading the documentation about QBE I see that it seems to be a mix of C and Assembly. The programming languages of the future are natural languages.

Odin is making a backend for their compiler cuik called tilde that can be used for programming languages as well