Catboy Ranch
kiwifarms.net
- Joined
- Aug 21, 2022
The Rust language caused a /Selection Effect/ because they went woke with their public cons fairly early on, so every programmer who is also a sex pest in a Party City wig obviously heard good things about Rust because I FEEL SCEEEEEEEEEENOMG YAAAAAAASKWEEEEEN
unlike other programming language homes, the one for Rust is always littered with wokeshit
Having used the lang, for what you get out of C and Go out of the box and the SDKs you can already get out of you distro, you're not really getting much of anything--except for newshit that other devs are working on that don't already have an analog on C, Python, Go. And Rust is more symbol-heavy than C++ is, so bullshit complicated nightmare structures are just as easy to create in Rust as in C++. I dunno I think the current environment in C where you check your shit (hello, use valgrind you homofag) is better than switching. But some people won't trust your ability to check that you cleaned shit up and will insist that you move into a GC world and they prefer the tranny lang because they post all the correct up to date wokeshit in advance of all their cons.
Can't wait until someone tries to combine a Women In Tech event with an invite to Rust devs. That's going to be HILARIOUS to be at one of those.
Then I went to look at what he was doing his work in.
even with two (CRT) monitors this shit was unusable.
That IDE would later be rebooted a few years later as Eclipse, which was also AIDS. I wrote all my shit in emacs over screen and had ci/cd scripts (that's what the Tcl was for) before the term ci/cd was even invented.
I deal with C++ quite a bit and even with the new modern build tooling it is still AIDS. No, CMake doesn't make things any better than before, because most of the problems with maintaining it are not because of autoconf, it's because of all the contract assumptions in the headers and all the workarounds that get added later because the class structure will never bend to future needs as much as DP promises it will if you just use the right patterns. And the debugging... my god. I have VMs that took me months to get working right with IDA Pro that I don't even remember how I got all the fucking deps to work right much less the 9 billion env var and conf tweaks, and that's even with the manuals of docos that I wrote at the time when I built all that shit.
Unless you are writing a GUI and need Qt+, there's no legit reason to start a new C++ project. Whatever you're thinking of that you need to write, it can be done in C or something else besides that fag language.
Yes, you will make more, but do you really want to maintain OLE and CORBA objects from the 90s? And 99.99% the time your paymasters will not give you architectural authority to launch your own refactoring project that has no user feature benefit. If the C++ projects are wrapping hardware directly, they may give you some slack on the leash. But if it's non-hardware based or post-hardware, if you don't demand the autonomy up front when interviewing with the manager you won't get it post-hire.
The only benefit to C++ is the Indian quotient is way lower than every language. There are very, very few Indian programmers who are good at C++. I know some good C pajeets but none of them want to go anywhere near C++. I've only worked with one in my lifetime, and he wasn't that good a C++ coder.
unlike other programming language homes, the one for Rust is always littered with wokeshit
Having used the lang, for what you get out of C and Go out of the box and the SDKs you can already get out of you distro, you're not really getting much of anything--except for newshit that other devs are working on that don't already have an analog on C, Python, Go. And Rust is more symbol-heavy than C++ is, so bullshit complicated nightmare structures are just as easy to create in Rust as in C++. I dunno I think the current environment in C where you check your shit (hello, use valgrind you homofag) is better than switching. But some people won't trust your ability to check that you cleaned shit up and will insist that you move into a GC world and they prefer the tranny lang because they post all the correct up to date wokeshit in advance of all their cons.
Can't wait until someone tries to combine a Women In Tech event with an invite to Rust devs. That's going to be HILARIOUS to be at one of those.
I remember working on C and Tcl using a full screen terminal at one job and the person next to me was rah rah rah C++ is da future, it is God, it is the essence.
Then I went to look at what he was doing his work in.
even with two (CRT) monitors this shit was unusable.
That IDE would later be rebooted a few years later as Eclipse, which was also AIDS. I wrote all my shit in emacs over screen and had ci/cd scripts (that's what the Tcl was for) before the term ci/cd was even invented.
I deal with C++ quite a bit and even with the new modern build tooling it is still AIDS. No, CMake doesn't make things any better than before, because most of the problems with maintaining it are not because of autoconf, it's because of all the contract assumptions in the headers and all the workarounds that get added later because the class structure will never bend to future needs as much as DP promises it will if you just use the right patterns. And the debugging... my god. I have VMs that took me months to get working right with IDA Pro that I don't even remember how I got all the fucking deps to work right much less the 9 billion env var and conf tweaks, and that's even with the manuals of docos that I wrote at the time when I built all that shit.
Unless you are writing a GUI and need Qt+, there's no legit reason to start a new C++ project. Whatever you're thinking of that you need to write, it can be done in C or something else besides that fag language.
C++ pays more because the new kiddies are afraid of stepping foot into 25+ year class taxonomies with fiendishly complex dependencies on ancient OS deprecated features. That's where the bulk of the work is that the employers are posting for. You might luck out and find a hardware shop with a buttload of Qt+ work but 99% of the time it's not gonna be that.
Yes, you will make more, but do you really want to maintain OLE and CORBA objects from the 90s? And 99.99% the time your paymasters will not give you architectural authority to launch your own refactoring project that has no user feature benefit. If the C++ projects are wrapping hardware directly, they may give you some slack on the leash. But if it's non-hardware based or post-hardware, if you don't demand the autonomy up front when interviewing with the manager you won't get it post-hire.
The only benefit to C++ is the Indian quotient is way lower than every language. There are very, very few Indian programmers who are good at C++. I know some good C pajeets but none of them want to go anywhere near C++. I've only worked with one in my lifetime, and he wasn't that good a C++ coder.
Last edited by a moderator:
