Making a relatively small project with a group of people. We all know C, but some fuckers think they know a ton of C++.
> Muh classes and objects
> vectors and strings
> can't into string.h and malloc()
> can't into structs
> stackoverflow "How to copy strings"
Fuck OOP, if you have to resort to predefined classes for copying strings, you're a fucking brainlet.
> std:: everywhere cause I'm so fucking cool
> code absolutely unreadable
> can't into namespaces
C is nice until you reach 2000 LOC. Then troubles starts.
C++ is nice until you reach 2000 LOC. Then troubles starts.
Being a chad is nice until you hit 2000 STDs
Being an incel is nice until you hit 2000 hours of inceldom.
Being a 2000 is nice until you hit chad STDs
being a terry is nice
.............
until you hit a train
Being a neet is nice until you hit 2000 years
C is fine until you need to handle a string without it being a security hole
ban
Calling C insequre is nice until you write 2000 LOC in Rust.
kek
>Fuck OOP
Welcome aboard my redpilled "C" fren.
Virginity is funny until you reach 20. Then trouble starts
merely using C++ does not mean OOP
OOP is a matter of design. just using classes/objects doesn't make it actual OOP
Have sex
>OOP means using a language's (badly written) stdlib
haha what a wild uni freshman opinion, you
sure told them
OP was a mistake
highjacking this bullshit-thread with a good language now:
I wrote a bashscript that checks every minute my external ip-address. The script is used as a cronjob and it reads a file every minute to see if the received IP is another than the last saved one. Now I get the autistic feeling that this is heavy for my poor ssd. How can I make this less heavy? I could write it as a daemon in a while loop and 60s sleeptime but making a config for systemd sucks too. So what am I gonna do besides sticking a raspberry pi up my ass? Please help.
It's not a matter of the language, but how you use it.
And OOP have a bizarre cult that enforces horrible to read practices around it.
It's like if there were an group of people that use goto for everything because the "labels make it more readable".
MainLoop:
goto GUIRenderer
ReturnFromGUIRenderer:
goto ProcessData
ReturnFromProcessData:
if (not_ended) goto MainLoop
you care confusing OOP with C++
>all these goto
makes me puke
Come on, it's very verbose and easy to understand.
"verbose" and "easy to understand" are literal antonyms.
*screams in goto*
Did a pythong "porgrammer" write this?
>> stackoverflow "How to copy strings"
at least they are not using things willy-nilly puking vulns all over your codebase by doing that, right?