🤣 wtf did I just read
Is this why C++ will never die?
Rather than dealing with this ‘cargo’ remote repository utility and reliving traumatic memories of remote artefact repositories with NodeJS, Java, etc., we’ll just copy the .rs files of the wrapper directly into the source folder of the project.
[forgets to copy some files]
[complains about compiler error]
This guy is a moron of the first order!
Rust: has stronger typing than C. This guy: I don’t like rust since it’s weakly typed.
Also this guy: doesn’t uses cargo because it downloads from the internet without taking the 5 seconds of research to know that
--offlineexists.Also this guy: I don’t like that rust calls C unsafe. It’s safer than assembly.
The guy is just dumb as rocks.
I don’t know how hackaday works. Is literally anyone allowed to write articles full of non-factual information?
Yeah I was wondering that and I googled it but didn’t find anything. The only thing you can obviously do is submit a tip.
If you click on the author’s name they’ve written over 1000 articles for Hackaday, but on their website they don’t actually mention it at all as far as I can see. You can tell how odd they are from their website anyway…
Full of WTFs.
My default development environment on Windows is the Linux-like MSYS2 environment
I think this sets the tone nicely lol.
it’s clear at this point already that Zig is a weakly-typed language
Uhm… pretty sure it isn’t.
You can only use the zig command, which requires a special build file written in Zig, so you have to compile Zig to compile Zig, instead of using Make, CMake, Ninja, meson, etc. as is typical.
Yeah who wants to just type
zig buildand have it work? Much better to deal with shitty Makefiles 🤦🏻♂️Ignoring the obvious memory safety red herring,
Uhhh
we can worryingly tell that it is also a weakly-typed language by the use of type inference
Ok this guy can be safely ignored.
the fact that the unsafe keyword is required to cooperate with C interfaces gives even great cause for concern
?
Rather than dealing with this ‘cargo’ remote repository utility and reliving traumatic memories of remote artefact repositories with NodeJS, Java, etc., we’ll just copy the .rs files of the wrapper directly into the source folder of the project. It’s generally preferred to have dependencies in the source tree for security reasons unless you have some level of guarantee that the remote source will be available and always trustworthy.
Lol ok… Ignore the official tool that works extremely well (and has official support for vendoring) and just copy files around and then is surprised that it doesn’t work.
Although you can use the rustc compiler directly, it provides an extremely limited interface compared to e.g. Clang and GCC
That is a good thing.
You get similar struggles with just getting the basic thing off the ground
Uhm yeah if you ignore the tutorials and don’t use the provided tools. It’s literally
cargo init; cargo run.What an idiot.
honestly, good. let people like this stay in their swamp of antiquated, headache inducing tools and systems.
it’s clear at this point already that Zig is a weakly-typed language
Uhm… pretty sure it isn’t.
They seem to think any type inference makes for a weak typing, judging by their previous rant about
autoin C++So, yeah, author’s views are a bit special, not sure this article will help me be better :(
