วีดีโอ

Sane as in keeping it simple so that people can think "Hey I could have been writing this myself!" 😇

Thank you for watching the video! 😀 You can read the Motivations section pagghiu.github.io/SaneCppLibraries/#autotoc_md45 but in general it's just having fun building something cool and sharing my view on how to fight the endless complexity predicated by some of the libraries you've indicated. So many libraries are "sprinkled with complicated templated classes" for no good reason. Some programmers are just attracted by endless unjustified complexity. And yes, you got one of the main points at first sight! Readability is one of most important principles pagghiu.github.io/SaneCppLibraries/page_principles.html because the best code is the easy to read one. SC::Vector exists because the project doesn't use the Standard C++ library, so std::vector can't be used. The main reason for not using the Standard C++ library is that including a single header from the C++ stdlib is nowadays putting in every compile unit tens of thousands of complicated lines of code, slowing compile time of projects by order of magnitude. Fast compile time is another core principle of Sane C++ Libraries. Another reason for not using the C++ standard library is that uses exceptions for error handling, that is a non zero-cost abstraction (SC::Vector returns bools / error codes). There are many other reasons but I can't enumerate all of them here😁

You're right! Here is the new link discord.gg/tyBfFp33Z6

@@Pagghiu Thanks

I am genuinely just having fun building this little project 😄 And to avoid eluding your questions: 1. I feel very productive in my own selected C++ subset and none of the problems the Rust was born to solve are actual problems that I experience in my own daily usage. I very rarely have memory or threading issues, even if C++ is "unsafe" by nature. I do not write security critical code though, maybe Rust is great for people in that field. 2. I like Python and its stdlib is really so complete, and an inspiration for me when looking at the ease of use of its API. C++ committee delivers specifications through a voting process done in in-person meetings. I think it's very difficult for a Python level stdlib to be created through this process, it has not happened so far and I don't expect it to be happening in the future.

My dream is for C++ to have a shift in design that allows for a complete rewrite of the std lib but I know I'm deluded and it will never happen. But C++ is a fantastic language, I just find it to be weird in a lot of cases. And like you said Python has a complete std lib, it is so weird to me that C++ doesn't really offer this

The unity build for this project is just a convenient way of delivering the library to users without needing to impose them a build system that would be required by any non trivial library. The unit tests project generated by the internal build system for example doesn't use the unity build, all files compile just fine in isolation. I plan to generate build files for other build systems using SC::Build so that everyone can keep using their favorite build system...or no build system at all!