rust is dead. long live rust https://hachyderm.io/@Mara/116580147649240612
Post
@hipsterelectron can't wait for the moment people will realise rust is bad, actually, and will "deoxidise" their codebases
@SRAZKVT C EVANGELISM STRIKE FORCE
@hipsterelectron no c fucking sucks
but none of the "c killers" actually solve any problem c has, while piling on more complexity
@SRAZKVT @hipsterelectron any specific problem you see with zig? I'm consistently amazed by it.
@kris @hipsterelectron only one implementation, not standardised, and not even stable yet, and also i get bad vibes from the fact it seems to be heavily discouraged to use a more proper build system (like meson) and instead insists on using zig build scripts
@SRAZKVT @hipsterelectron fair enough, but only one impl is just stating the fact that it's still not finished.
The zig build system is one of the reasons that i really love zig, since basically all you need is one executable to do anything that meson and friends require a whole posix setup to do (shell, make, python, autotools, various ancient macro systems)
If you're already building on that, sure that makes sense, but i really love that i can run complex builds in a sandbox that has little more than /bin/zig and its lib dir in there
@kris @hipsterelectron yea that's exactly what i don't want. i want individual responsibilities split up between different programs, such that i can switch them up as needed
@kris @hipsterelectron projects also tend to be based on several things and a language specific build system will usually get in the way (ever tried to build go code without using the go build system ? it's a nightmare, and not because of the gc), as they are designed to be sitting at the top, when in such cases it is expected they sit under another build system instead
@hipsterelectron 99% of c's problems are either the api being fucking dogshit or shit being implicit or unclear