uh oh

I hear villain music

no **closed**

Can you get it merged soon? It's blocking my Rust rewrite PR.

LGTM

And the reason for why these libraries don't really require a package manager is because they're built to be standalone for the most part. Whereas in languages that have package managers as a feature, the culture is very much to introduce a chain of dependencies; to build a dependency they use lots of dependencies that use lots of dependencies and so on without any care in the world. It is quite horrifying what behaviour package managers normalise when it comes to an ecosystem. Everyone agrees spaghetti code is bad, but dependency hell is just spaghetti code on a module basis, but everyone just accepts it because of convenience.

@@jambalaya974 The culture (aka web dev) is that people after bootcamps (so without any understanding of underlying tech) copy-paste code without any thought. I mean, things like leftpad and isArray exist in npm-ecosystem, it's enough of a proof. Those people not only never read language docs, they don't even stop to think for a second - 'Do I really need to pull hundreds of dependencies to get this to work?'. Not to mention that some of those deps can be malicious. It's refreshing to see that it can be done "the other way".

​@@jambalaya974 C has make and cmake, which are basically just terrible package managers if you think about it. In languages with a decent package manager, many libraries are designed to work as small parts of many other dependencies. Apart from outrageous compile times (which are not uncommon) you get all the advantages of code reuse and small modules with non of the downsides. Also, many projects in C have many dependencies. Look at GAP for an example of spaghetti C code with a ton of dependencies.

@@jambalaya974 so your solution is to just not include package manager? it sounds kind of like "let's just not give smartphones to kids" -- it may sound ok, but the result is always garbage. maybe there is a better strategy like reviewing and pruning packages over time, or merging the ones that are downloaded concurrently into a single bundle? i mean, if you need a program to actually work, you will include whatever stupid thing. you cannot write on a short notice linear algebra or statistics or codecs, it requires a serious amount of time and effort, and a thorough knowledge of the subject. this is why, btw, such things exist as several separate packages in the first place. then there are also proprietary libraries (which in many cases are so hideous, that they can only be fixed by communism)

​@@Daniel_Zhu_a6f I did not make a prescriptive statement on whether package managers as a language feature are a necessary evil or not for the time being. Just that they are not ideal and the culture they breed is awful. To me, Nix is ideal.

I guess a single file is easier to move around, and probably easier to navigate through the code for some people

There's a section explaining this in in the STB repo. Single header isn't the only appeal though, it's also just that other C libraries like libpng are significantly more low level than the API you usually get with single header libraries. Experienced programmers like them because they get you started quickly. You can get a window up or image loaded in just a couple lines of code instead of hundreds and immediately start writing the applications you actually wanted to make. Once your needs become more specific you can either switch to the lower level API that the lib exposes or ditch it entirely for a more robust alternative.

I assume it's just for simplicity, it's easier to move one file around and you don't need to add header files to whatever build system or script you're using

or CLAP

Люди не могут прочитать Цодинг, поэтому часто называют меня Зозин :)

​ @TsodingDaily во дают. А я думал это твоя фамилия, ан нет, еще один уандерфул сарказм))) Так и слышу каждый раз - "Мистер Азузин" 😂

he was joking