If C has a million fans, then I am one of them. If C has ten fans, then I am one of them. If C has only one fan then that is me. If C has no fans, then that means I am no longer on earth. If the world is against C, then I am against the world.

nobuild is unironicallly a very cool tool. I wish more c/c++ devs didn't make you learn cmake or ninja or whatever to get a project running

This is my favorite project on your repo. I hope it receive more love in future.

It would be good imo if you make a list of benefits of using nob as build system. Most people never realize how important and versatile it is until someone says that.

I love it. It looks like nobuild is trying to reproduce what Zig and Swift have - completely integrate build systems that are for all intents and purposes built into the compiler. A Zig build script is a Zig source file, a Swift build script is a Swift source file (and I think Jai also does this). I think this is the best way to do a build system for a language, and someday I'll figure out how to do this for multi-language projects (Zig is inching towards this, but with Zig as the primary, I think all the languages should be on equal footing).

Another amazing video, bravo.

the entropy thing is interesting. In an assignment to create radio sender and radio receiver programs (to have radio stations "transmitting" over the network) the sender was the 100x easier part. The receiver had to worry about packet ordering, deviations from protocol and missing packets. Looks like the same principle

This single man made me learn C and make my own build system. What a chad

Ur one of my favorite programmers on yt, keep it up!!

Like the philosophical take on increasing or decreasing entropy 1:34:00 as in it takes only seconds to vomit yet it take several minutes - or depending on the fabric involved several hours - to thoroughly clean it all up.

I really love this idea.

23:18 reminds me the saying: Every sage writes the same book.

Your framework idea reminds me a lot of Cello (libcello), very interesting project imo.

Use nob to bundle your utility headers into the nob.h header. So like mongoose web server your repo has checked in both the build artifact nob.h, but also nob.c as the build script, and src/ folder with all your header libraries. Then when you run nob.c, it rebuilds nob.h from src/, and you commit that along with changed sources. You can replace shitty glibc and make in one repo

Love the "Buy more RAM lol!!" to handle out-of-memory by the way ahaha (around 09:00)

This dude is the goat

You did it again son! King Tso Ding brap brap

I'd love to see something like an extension of C with namespaces and maybe some other minimal but useful things that would fit well with C. Maybe call it C+ :^).

Smells like your work will introduce the end of java. You are my hero D:

Think you'll a lot of the benefits from unit caches just using ccache. Otherwise you'll need to generate a dep file (-MD flag I think) and store it somewhere, then check if any of the dependencies changed too. (say for example foo.h changed but not foo.c)

7:44 this is really good, I hate shell scripts, I would totally use C directly

I still think, the return value of your run command async function should be bool (if it isn't already), just to keep in line with the rest of the library.

Just leaving this military grade comment here: Good stuff!!!

1:34:33 : this bit about how parsing a format taking more work than producing it, I think makes sense, to the degree that I think it should maybe be possible to express as a theorem, but, I’m not sure how to formulate it. Hmm... Well, what if you just like, take your struct or whatever, like, whatever region of memory you have, and just, write those bytes to a file? I suppose an issue with that is that if your data structure isn’t a fixed-size struct on the stack somewhere, and is instead something which contains pointers to things of varying size on the heap, (or more generally, if it contains any pointers at all), then you can’t really just directly load it from the file and expect it to work. Hm, I suppose in that case, you *could* like, when writing it to the file, concatenate all the regions of memory together, and like, replace all the pointers in it with pointers relative to the start of the resulting blob of data... and then, when loading it, if you just loaded the file into memory, that would *almost* work, except you would need to have to add the base-point to all the pointers before dereferencing them. Well, I suppose, if it also had like, at the start of the blob, a number indicating the number of pointers to fix (by adding the address of the start of the region of memory), followed by a list of the (relative) locations of these relative-pointers, the loading from the file could consist of: 1) reading the file into memory 2) looping through the list of relative-pointers and converting them to actual pointers 3) casting the location of the next byte after this list, to the type for the head object of what was loaded And this seems like it would be pretty short, independent of the details of the structure, and, probably substantially simpler than creating the file? However: it would have absolutely no error handling! Perhaps *this* (the need to handle the possibility of invalid data) is what is responsible for the extra effort needed when parsing some encoded data? Or, it could instead be the mismatch between human-readable format and in-memory format? Edit: actually, I think probably for many kinds of data, if one cared not at all for error-handling, the parsing of the representation could exactly mirror the production of the representation? Write-string, read-string. Write-Int, Read-Int. Really, the processes involved in expressing some data in a file, if the file content is represented by just another region of memory, should be entirely reversible. If you wrote it in a reversible programming language like Janus (iirc?) you could probably write the “convert this data to encoding for a file” and “take this data as encoded for a file, and obtain the data it represents”, and have them be the same function, just run in different directions? That is, assuming you didn’t care about error handling. ... though, I guess you would need to make the file such that it can be read backwards? (Because, writing it forwards, would entail reading it backwards) which could be problematic? I guess the approach would probably be (outside the function) to copy the data structure, and then express every part of the data structure in the file, and then then using only what is in the file, subtract (or xor, or whatever) off all the parts in the copy, and then once it is all zeroes, de-allocate it. Though I guess maybe would have to do the zeroing-out and de-allocating recursively. Hm. How do you handle malloc in reversible computing, actually? I suppose something like: When you call malloc, you obtain a pointer to a region of memory which is all zeros, and in order to be able to de-allocate it, you are obligated to first zero it out (in a reversible way, of course). But, also, I guess it would be forbidden to use the pointer in ways other than as a pointer? E.g. it would be forbidden to malloc two regions of memory, and then have a switch statement on whether the difference between the pointers to those regions of memory is divisible by 3, and then de-allocate those two regions, because the details of how malloc behaves (what particular blocks of memory it hands out) shouldn’t be something that normal code should need to care about? Like, if I have two functions that have disjoint combinations of inputs and outputs, doing one function, then doing the other, then undoing the first function, then undoing the second one, should result in no overall effect. (Essentially , calling functions should be applying elements of a groupoid, and, where applicable, elements with disjoint support should commute... Actually, not sure if “groupoid element” is precisely the right idea?) At least, in situations where no error occurs.

I've been ignoring your nobuild videos because on the surface it doesn't seem as interesting as some other stuff you've done. That's a mistake on my part; I'm learning so much from this video. Edit: lmao yep "military-grade" got me, I have no idea how but it got me to click

The actual king of programing is BetterC and C is the jester. True.

C is king of programming like lion is king of jungle

In one of Tsoding' latest videos he talked about how programming is self-destructive, does anyone rememer where that was? I cannot find it

I'd like to add another comment about touch and file creation in Linux. I usually create files with "> file.txt" and if i want to create files and start to edit it imediately i do cat > "file.txt" When i finish editing and hit ctrl+c it created and has content. Very useful imo.

would be more interresting to see same thing with modern c++, with modules as well. no header files.. something like.. inherent c++ build system for c++

40:34 Butchered the joke Mr Streamer. The 3 most difficult things in computer science are 1) naming things 2) off by one errors. Add we list also should parallelism ccuonrenrcy adn.

Hi Tsoding. How about raycasting (wolfenstein) with textures using C/Raylib? Would be super nice

Is static linking possible with nob? Why not make it detect the default rt environment target. You don't need a configuration file your computer already knows and hence nob already knows... assuming you got nob already installed on your system.

When I make build system hardest and most annoying thing is some header file included multiple c files and modified. Because of that i need to recompile c files which depends on that header file. Sometimes some c files didn't recompile and creates seg fault. In that case I need some sort of AST index database like IDEs. I don't use IDE. I like to code in my vim. So usually I do `make clean && make`...

Does this build system ignore already compiled files? Like in case of `make` a target is not build again if the sources have not changed.

why not use env variables instead of command line flags? it might be more suitable for this specific use case. then the parsing would be already handled by your shell and your application wouldn't need to be concerned with the extra state management issues which having config files introduce...

Omg! It is mindblowing! I hate C/C++ build ecosystem because of stupid unique build environment requirements when just trying projects.

Can u bump the Audio a bit before uploading to YT 🙂

❤❤❤❤

unit caching made me fail a uni assignment: I added a syntax error in a header but the only .c file that included it had a newer cached .o, so I didn't see a problem when I ran make... but the assessor couldn't compile the code

Very very cool stuff especially the self rebuilding. Correct me If but only nob is not recompiled in case nothing has changed. In other words the project that we are building with nob is always building from scratch at least with the current implementation of nob.c I think it would be cool if that was not the case like it is in Make where only the touched files would be recompiled. Although I am not sure whether it would make sense for nob.h to handle this at all or If it would make more sense for this to just be handled by nob.c on an individual project level.

The question is can nob automatically rebuild your tea? 🤔

Tsoding about to develop Tsai, a jai-like package/framework for C

This is cool but I am disappointed that there isn't a mature build tool that was literally recognized by the military as standard.

Ok, im a little confused. Isnt make and cmake written in c?

you look a lot like skylab

1:15:40 it fking worked

Build systems existing is just a sign that the compiler frontend sucks, isn't it?

Is C your favorite language?

30:21 hey, I have a PDP11 clone that I made myself

You just inspired me to write something similar in Go, primarily to learn. Maybe it will grow to become something, maybe not lol

military grade hahaahahaha I love it! what is this? a VPN? an encrypted email service?? haha tsoding is live tsoding is love

So are you telling me that if someone tries to build from a build cache and encounters an error, and we need to tell the user to re-bootstrap the build system that the error message will read "NOB_ERROR - Please touch nob to continue" 😂

append sister

macos works i checked

glibc is a mess. If I recall correctly, glibc talks to systemd out of band to resolve DNS things... I would just compile statically against musl or dietlibc or some other libc that doesn't need itself dynamically in static builds

I thought mingw rhymed with pingu.

voidf

Who disliked this video... like why?

military??????????????? bro

First comment

Stupid idea: build system that can be used from #!/usr/bin... as a first line in a main.c, so you can just run ./main.c as a plain executable. No more build system to bootstrap