I have met a couple of them in real life, and a few I have met online. The sample is not significant enough to draw any conclusions about their point of view and background.
I am more than interested in your opinions about the personality and political makeup of people who express this type of pro-C bigotry.
It’s crazy to me that people don’t do this, once you’ve learned a few languages you can basically just pick up new ones (assuming they don’t use entirely foreign concepts like Rust does)
Which foreign concepts do Rust use? The borrow checker/ownership is new but that’s really the only thing that doesn’t already exist in some other language.
The borrow checker, the way it handles exceptions and nulls, the way it handles stack/heap (possibly foreign to me because I’ve never done much on C), composition pattern instead of oop, probably more I’m forgetting
Rust can be picked up the same way. I was in the situation you describe. Knew a dozen languages. Picked up rust and really enjoy it. It added a dimension to my thinking (ownership). I feel closer to the metal yet safe. That said, it still gets tricky with system design. That’s where it’s a lot harder due to ownership stuff. Just syntax wise it’s not bad tho
It’s no different from anyone else with arbitrary, narrow-minded views. People like that, whether they realize it or not, don’t believe in the intrinsic value of personhood.
This extends to their view of themselves and creates a need to feel valuable for some other reason. So they create a narrow idea of what it means to be good and valuable and it just so happens to align with their own traits, interests, and beliefs.
C++ is pretty awesome but anyone who thinks a single language is the solution to all problems is dumb… unless you’re smart enough to realize that the one language to rule them all is PHP of course!
If there is anything I’ve learned in my 10+ years as an engineer, it’s that there are no good or bad languages, just pros and cons of each in different applications.
Except NodeJS. Never use JavaScript on the backend.
If there is anything I’ve learned in my 10+ years as an engineer, it’s that there are no good or bad languages, just pros and cons of each in different applications.
I dunno if I agree really - the more languages I’ve learned, the more I see an evolution from less sophisticated, less usable languages to more sophisticated, more usable, modern and just generally better languages.
C and C++ are old, and you can tell. There’s so much complexity and legacy in those languages that it’s crazy. But it’s not just legacy - it’s also bad design choices. There’s a lot of really bad APIs and bad usability and footguns everywhere. You see the same thing in languages like JavaScript (whose design journey has been fraught with peril). Even Java has some bad stuff I would say, mostly from the overzealous insistence on OOP.
However, if you look at some modern languages that were more deliberately designed, you really start to see how they are just intrinsically better. Python, while still being a dynamically typed scripting language which I would never use for large systems, is still leagues better than JavaScript in terms of design and usability I would say. Haskell was born from research and you can really tell - the language just makes sense in a very scientific way - although that does mean ease of use and developer experience has not always been the priority.
Rust was developed for a very particular purpose, basically to provide the same speed as C++ but without any undefined behavior. From that design principle, a lot of good has resulted and Rust is basically an objectively better language than C++. The only thing still keeping C++ in the game is the historical reasons, just due to the sheer amount of code that exists out there in C++. C++ has more support in all kinds of places, but that’s just due to history and Rust will likely gain ground soon enough. For instance, C++ still rules for game development, but this could change within the next 5 or 10 years.
It’s not that surprising when you think about - languages like Python, Haskell and Rust were built on the giant pile of experience the whole industry has amassed from using previous languages. It also helps that we just have more computing power today to make languages like Rust feasible. Rust compile times probably wouldn’t have been realistic 30 years ago.
i find javascript to be a great language for throwing together quick and dirty hacks.
I hope that last part wasn’t a joke at PHP’s expense.
I am actually surprised what PHP can do over the past few years. We converted a few critical REST APIs into PHP and it wasn’t just lightning fast, it’s also incredibly readable that we had non-PHP developers convinced it was the right move.
In my opinion, C purists are people who REALLY need to wash their fucking dishes, touch grass and get some sunlight. They get too worked up because “all the important things are written in C”, the important things being drivers, kernel and most basic stuff that OS needs.
Whenever one talks about performance, just reply with “use Assembly” and their argument is immediately invalidated. You can also mention networking, fault tolerance and how Erlang does a much better job than C or C++ could do, which is why “real adults with real jobs” created it in the early 90s
But mostly, it’s ironic that they’re becoming C-Conservatives, blaming the “hot new language” for bringing “the kids”. You can read the same kind of logic and disdain for C programmers, from LISP programmers, in the Unix Hater’s Handbook (1994)
Nah, I like using C for low level stuff, it balances that it’s reasonably high level and procedural with pretty great performance, size and flexibility. ASM is faster, but you are slower when it comes to understanding someone else’s work.
For projects that aren’t size or performance sensitive, write it in python or whatever the fuck you like, idgaf.
They are wrong. The correct answer is Rust. Have a great day.
HERETIC ! CAST THIS FOUL USUPER FROM THE TEMPLE !
C-ing is believing.
C ++ is double plus good.
C has always been at war with Rust.
Your statement already terminated from a NullPointer error when you said “CAST”. Better luck next time, gancho.
