No, that's only partially true.
The infamous case you are referring to was a C programmer who had an apparent IQ of 49, but was actually a genius with an IQ of 305, since at the time of measurement only 8 bits were sat aside to store the IQ.
The man was adamant about keeping his privacy, which is why we never knew who it exactly was, only that he was a C programmer who claimed that defaulting to signed integers as the default was the biggest mistake to have crept into C.
He never mentioned anything about null-terminated strings, though.
Look at me mom! I'm doing the compiler's job for it! I'm such a good C programmer:-)
2 weeks ago
Anonymous
By this logic, you should just use Python.
2 weeks ago
Anonymous
Python doesn't provide zero-cost abstractions over C.
2 weeks ago
Anonymous
ASM to C >less code to write, okay
C to C++ >more code to write, no thanks
C sits at the golden ratio. Coincidentally, I, a C-programmer, have written an algorithm in Bohemia Interactive's SQF scirpting language that just happened to be centered around the golden ratio, because I am that awesome.
I know it's hard for you to fathom, but the truth of the matter is that over here in "C," we don't really give a shit what we use, and C's used just because it works. Don't touch a running system.
Rustgays, on the other hand, are not just touching the running system, they want to rebuild the entire thing in a new language as well.
These are the worst type of mindsets you can have as an engineer, and they don't even realize it.
2 weeks ago
Anonymous
>an algorithm in Bohemia Interactive's SQF scirpting language that just happened to be centered around the golden ratio
I had a formula that "activated" (i.e. spawned enemies and objects) a location when your player character is XYZ distance away from center, and I wanted to create a hysteresis for this activation when you leave, and the formula I created for that, when refactored and reduced to polynomials, had the constant (1 + 5^(1/2)) / 2, i.e. the golden ratio, in it.
Basically, I accidentally "discovered" the golden ratio while writing some shitty code for some shitty milsim.
Suck my dick.
2 weeks ago
Anonymous
Trust me, this 20000 line C project has no memory bugs since it passed all the unit tests!
2 weeks ago
Anonymous
You don't use unit tests to assert memory completeness, and I'm not sure if you knew that or not when you were posting that reply.
2 weeks ago
Anonymous
Sorry, I don't believe that you've ever written a mathemathical proof or touched Coq. No, it's not the thing you suck daily.
2 weeks ago
Anonymous
>No, it's not the thing you suck daily.
fricking kek.
2 weeks ago
Anonymous
You're too dumb to even discern between someone discovering something and someone (mathematically) proving something, anything I explain to you to make you believe would be a waste of my time.
Nay, you are my counterpart as we vie for the favor of the public, my moronic little friend.
Apart from that, you know I saw that coming, baby!
ASM to C >less code to write, okay
C to C++ >more code to write, no thanks
C sits at the golden ratio. Coincidentally, I, a C-programmer, have written an algorithm in Bohemia Interactive's SQF scirpting language that just happened to be centered around the golden ratio, because I am that awesome.
I know it's hard for you to fathom, but the truth of the matter is that over here in "C," we don't really give a shit what we use, and C's used just because it works. Don't touch a running system.
Rustgays, on the other hand, are not just touching the running system, they want to rebuild the entire thing in a new language as well.
These are the worst type of mindsets you can have as an engineer, and they don't even realize it.
>I know it's hard for you to fathom
2 weeks ago
Anonymous
Then you just showed us you don't even bother wrapping your asan/valgrind checks into proper unit tests. Hell, most Cniles don't even bother with using asan/valgrind. And then they cry about how nobody takes them seriously.
2 weeks ago
Anonymous
I don't think you even bothered to look up what SQF is...
Anyhoo, you can't even follow a casual conversation that borders on technical stuff, I wouldn't want to go bare metal with you, fren 🙂
Best of luck to you and your endeavours, I think you might need it ;D
2 weeks ago
Anonymous
I'm talking about C, not your shitty proprietary DSL
2 weeks ago
Anonymous
Why would I need mathematical proof for C?
Logical is enough.
2 weeks ago
Anonymous
(I'm ignoring you shifing the goal posts again, because otherwise this conversation wouldn't even get off the ground. The things I do...)
2 weeks ago
Anonymous
>Yes, I asserted my program's correctness. What? No, I did not do any tests... no, there were no proofs either... and I didn't use asan while debugging because that's bloat... >Just trust me it's correct, mkay?
2 weeks ago
Anonymous
Yes. My code works. There were hiccups, sure. But my code has been keeping machines safe, that have the potential to blow up buildings, for five years straight, 24/7.
It's a watchdog unit, it checks that a control PC for a machine changes a digital output every 1000ms (because if it doesn't, it means the PC has frozen).
The code overflows after 65535 milliseconds and has a finite set of states it can assume in accordance to that.
I *could* run whatever official test you want me to, but I know I didn't frick up.
Maybe you just don't know this code completeness feeling that you need these whatever tests. I have enough shit to do, my shit works with machines worth and earning millions, but none of them need certification like in the aerospace industry.
There's really nothing more I can add to that.
2 weeks ago
Anonymous
>and none of them need certification
Case closed.
2 weeks ago
Anonymous
LabVIEW, Siemens S7, all their underlying code, it's all C.
Not Rust.
They control nuclear power plants.
And I said I *could* certify it and it would pass with flying colors.
I just can't be bothered if I don't need to, doesn't mean I didn't write the code to be as perfect as possible so as to only have to do it once and never touch it again.
What have you done?
2 weeks ago
Anonymous
yeah thankfully after shit like Therac-25 engineers learned that cniles are mentally ill like (You) and thankfully all safety is in hardware so no matter how shit your code is, it won't matter.
2 weeks ago
Anonymous
>all safety is in hardware so no matter how shit your code is, it won't matter
Who do you think programs this hardware, JFC, lol, this is getting more and more ridiculous.
2 weeks ago
Anonymous
You don't know neither Verilog nor VHDL
2 weeks ago
Anonymous
Are all just formalizations of what you should be doing intuitively.
total moronic monkeys like you, that's why all safety is in the unprogrammable part of hardware
You know, I could just flip this around and say, well then, why even use Rust if safety doesn't matter?
C programmers thinking they are engineers is the funniest shit ever
Thanks, I'm flattered.
2 weeks ago
Anonymous
>You know, I could just flip this around and say, well then, why even use Rust if safety doesn't matter?
because I'm talking about this thing called embedded programming which is trivial compared to real programming, like writing real useful programs that are so complicated and need so many things in them and safety built in that people choose to write them in... C++ because C is for midwits who write most boring code that could be provided by the guys who created the hardware.
2 weeks ago
Anonymous
>are so complicated and need so many things in them...
skill issue
2 weeks ago
Anonymous
yeah just like in this example https://lwn.net/Articles/542457/ where C programmers admitted that they're incapable of maintaining their own compiler in their toy language inadequate for writing compilers in
Yeah, well, embedded is the only safety critical thing that matters, everything else is peanuts.
Everywhere else doesn't risk limbs being chopped off, bombs detonating too soon or too late, heart-pacing machines beating too fast or too slow, kidney filtering bypass machines operating reliably, etc., etc.
All your other "safety" critical bullshit are memes compared to life and death.
So, sincerely, shut the frick up.
everything you mentioned has built-in hardware safety that is impossible to override in software because engineers know that (You) are mentally ill and out to kill people
2 weeks ago
Anonymous
>engineers know that (You) are mentally ill and out to kill people
What the frick, man.
2 weeks ago
Anonymous
It's like he *hates* me more than I am ...annoyed by him.
Idk, it's the bed you made.
2 weeks ago
Anonymous
>others suck therefore you do
frick you too, crab
2 weeks ago
Anonymous
Yeah, well, embedded is the only safety critical thing that matters, everything else is peanuts.
Everywhere else doesn't risk limbs being chopped off, bombs detonating too soon or too late, heart-pacing machines beating too fast or too slow, kidney filtering bypass machines operating reliably, etc., etc.
All your other "safety" critical bullshit are memes compared to life and death.
So, sincerely, shut the frick up.
2 weeks ago
Anonymous
>Everywhere else doesn't risk limbs being chopped off, bombs detonating too soon or too late, heart-pacing machines beating too fast or too slow, kidney filtering bypass machines operating reliably, etc., etc.
*Correction, it does, when's being operated from a higher-level language/interface.
So the chain does extend upward.
I hope the Rust developer knows what he's doing when he interfaces wif my low-lewwel icky-fippy litty-bitty embeeddid C-progwammed EM-CEE-UwU *twerKs*
2 weeks ago
Anonymous
>Yeah, well, embedded is the only safety critical thing that matters, everything else is peanuts.
Most embedded software is not safety critical. It's toy software where nobody cares if it crashes.
2 weeks ago
Anonymous
>Are all just formalizations of what you should be doing intuitively
Hardware design and its logic doesn't come out of thin air Black person. It's not written in C.
2 weeks ago
Anonymous
>It's not written in C.
So it doesn't matter then.
It's not written in Rust either.
Ad absurdum.
2 weeks ago
Anonymous
C does not provide safety in modern low-level hardware designs. It also doesn't provide safety in complex programs. So why do you delusional Black folk keep lying that it's safe?
2 weeks ago
Anonymous
because it provides control
now go speedrun rust ack% somewhere else
2 weeks ago
Anonymous
C provides so little control you cannot even define a compile time constant in big endian without having to manually swap it when it changes
2 weeks ago
Anonymous
>C++ thread >Rust Rust Rust Rust troony troony troony
They truly live in your head rent free. Friendly reminder that most embedded programmers trooned out, including cniles.
2 weeks ago
Anonymous
never mentioned troondom even once.
meds homosexual
and not of the hrt kind this time
2 weeks ago
Anonymous
C is not a hardware specification language
2 weeks ago
Anonymous
total moronic monkeys like you, that's why all safety is in the unprogrammable part of hardware
C programmers thinking they are engineers is the funniest shit ever
total moronic monkeys like you, that's why all safety is in the unprogrammable part of hardware
2 weeks ago
Anonymous
C programmers thinking they are engineers is the funniest shit ever
2 weeks ago
Anonymous
C programmers are literal accountants of programming industry, they write most boring menial code like drivers and firmware which is just very spoopy words to the uninitiated but it basically boils down to writing basic functions like do_thing that wraps something like 3 bytes being sent to hardware directly which is a coded instruction for doing thing, very deep, requires very high intellect, and indeed, without C it's impossible to do, it's not like there's driver frameworks created in fricking Python because someone thought it would be funny to write drivers in Python because writing drivers is so complex even a Pyjeet can do it.
2 weeks ago
Anonymous
>t. Therac-25 programmer's nephew
>The NASA study of the Toyota electronic throttle control firmware found at least 243 violations of these rules.
https://en.wikipedia.org/wiki/The_Power_of_10%3A_Rules_for_Developing_Safety-Critical_Code
How many drive hours does Toyota have vs. JPL's satellite and spaceship flight hours?
Certification requirements depends on external factors and should never be taken for absolute.
Which is something every actual engineer knows.
2 weeks ago
Anonymous
every actual engineer learned the hard way that if he won't make it safe, then it won't be safe, the end user is ALWAYS fricking moronic and in this case end user is the C programmer
2 weeks ago
Anonymous
>t. Therac-25 programmer's nephew
2 weeks ago
Anonymous
>Why would I need mathematical proof for C?
I mean, how do you think glibc fixed condvars in pthreads? someone had to define a working model of C execution and and parallelisms to spot a deadlock. to be fair, sophisticated condvars are fricking nightmare fuel, but anyhow.
2 weeks ago
Anonymous
>implementation 0 was so shit it needed fixing
lol, cniles truly are geniuses
2 weeks ago
Anonymous
look at how condvars are implemented. It's not a problem limited to C, honestly. It's just a very tricky problem with how multithreading and how the C++ atomics model works.
2 weeks ago
Anonymous
yeah I know some trivial stuff is too hard for cniles who can only think in single thread because that's just how limited their brain is
2 weeks ago
Anonymous
implementing a trivial condvar isn't hard... implementing one that's free of ABA tier bugs trying to avoid spurious wake ups is, however.... what are we arguing about again?
2 weeks ago
Anonymous
all condvar implementations have spurious wakeups
2 weeks ago
Anonymous
implementing a trivial condvar isn't hard... implementing one that's free of ABA tier bugs trying to avoid spurious wake ups is, however.... what are we arguing about again?
*checked what tf is a condvar*
lmfao
fricking toddlerlangs
2 weeks ago
Anonymous
Ya, it's about avoiding them when possible.
2 weeks ago
Anonymous
>working model of C execution
You mean a working model of the machine code created by C.
This is ridiculous.
2 weeks ago
Anonymous
>Hell, most Cniles don't even bother with using asan/valgrind
to be fair, using it is nontrivial, especially in some cases where timing dependencies are involved.
I really just don't understand why people deal with this unknowable unworkable garbage instead of taking the Rust pill, but whatever. miri works well enough in the cases where you can't "know" anyhow.
>Modern C++ is much, much harder to write properly than C.
I can agree with this to some degree. It's generally to the point where It's better to just ignore the standard's garbage and make your own.
Artificially making it harder and then circlejerking yourself to it doesn't actually count, Seppletard.
I just ignore all the OOP crap and write as pure functional as possible. That solves literally 99% of problems anyone complains about. It's not my fault you all fell for the worst paradigm in history. A whole generation of coders writing spaghetti because university told them to inherent wheel from car and they drank the coolaid.
2 weeks ago
Anonymous
It's more than just the OOJeet. Fundamental shit like co-routines are unusable in C++.
2 weeks ago
Anonymous
This is what I mean bro. All my functions are pure, that means all my parallelism just werks. Don't even need to think about it.
2 weeks ago
Anonymous
Yep, late 90s to mid 2000s.
Then it was about making everything a webapp.
Now it's about rewriting everything in Rust.
In all cases, it was always about morons by morons for morons.
2 weeks ago
Anonymous
Yeah. Clojure saved me from this hell and showed me the light. Coding is fun again in any language. All I need is lambdas and all your classes can go to hell.
>owners
who? the shareholders? they can't do shit anyhow as long as the executive team (who will all be pajeet) are making the money roll in and don't say anything that will imply they are undermining the shareholders'.
>fire anon >hire 20 Indians on an HB for the same total monthly wage >rewrite whole program in Java >get government subsidies as a reward for ditching a memory-unsafe language
>>get government subsidies as a reward for ditching a memory-unsafe language
the last part is moronic, but the former is actually happening.
The Indian government is actually subsidizing offshoring tech work to India.
It's fricking horrifying how bad it's going to get if India keeps it up.
ok, so you're moronic. stop shitting up this thread.
2 weeks ago
Anonymous
Don't shoot the messenger! Biden's the one mandating Rust, not me.
2 weeks ago
Anonymous
Holy shit frick off idiot. I swear to christ bringing back /misc/ (neo /new/) was a fricking mistake. I fricking hate Hiromoot for not genociding it already.
>Things that instantly filter below 120IQ
Straight, pure and unadulterated C.
>C++
lol
lmao
he's right cus C is for 130+
and golang is for 140+
>Straight, pure and unadulterated C.
You need an IQ below 50 to use C.
>t. filtered
No, that's only partially true.
The infamous case you are referring to was a C programmer who had an apparent IQ of 49, but was actually a genius with an IQ of 305, since at the time of measurement only 8 bits were sat aside to store the IQ.
The man was adamant about keeping his privacy, which is why we never knew who it exactly was, only that he was a C programmer who claimed that defaulting to signed integers as the default was the biggest mistake to have crept into C.
He never mentioned anything about null-terminated strings, though.
my sides
c comes in stages, lads
Modern C++ is much, much harder to write properly than C.
Artificially making it harder and then circlejerking yourself to it doesn't actually count, Seppletard.
The funniest part is that this isn't even correct advice. It's actually much simpler.
>cute trap
c++ bros, we can't stop winning
Look at me mom! I'm doing the compiler's job for it! I'm such a good C programmer:-)
By this logic, you should just use Python.
Python doesn't provide zero-cost abstractions over C.
ASM to C
>less code to write, okay
C to C++
>more code to write, no thanks
C sits at the golden ratio. Coincidentally, I, a C-programmer, have written an algorithm in Bohemia Interactive's SQF scirpting language that just happened to be centered around the golden ratio, because I am that awesome.
I know it's hard for you to fathom, but the truth of the matter is that over here in "C," we don't really give a shit what we use, and C's used just because it works. Don't touch a running system.
Rustgays, on the other hand, are not just touching the running system, they want to rebuild the entire thing in a new language as well.
These are the worst type of mindsets you can have as an engineer, and they don't even realize it.
>an algorithm in Bohemia Interactive's SQF scirpting language that just happened to be centered around the golden ratio
I had a formula that "activated" (i.e. spawned enemies and objects) a location when your player character is XYZ distance away from center, and I wanted to create a hysteresis for this activation when you leave, and the formula I created for that, when refactored and reduced to polynomials, had the constant (1 + 5^(1/2)) / 2, i.e. the golden ratio, in it.
Basically, I accidentally "discovered" the golden ratio while writing some shitty code for some shitty milsim.
Suck my dick.
Trust me, this 20000 line C project has no memory bugs since it passed all the unit tests!
You don't use unit tests to assert memory completeness, and I'm not sure if you knew that or not when you were posting that reply.
Sorry, I don't believe that you've ever written a mathemathical proof or touched Coq. No, it's not the thing you suck daily.
>No, it's not the thing you suck daily.
fricking kek.
You're too dumb to even discern between someone discovering something and someone (mathematically) proving something, anything I explain to you to make you believe would be a waste of my time.
Nay, you are my counterpart as we vie for the favor of the public, my moronic little friend.
Apart from that, you know I saw that coming, baby!
>I know it's hard for you to fathom
Then you just showed us you don't even bother wrapping your asan/valgrind checks into proper unit tests. Hell, most Cniles don't even bother with using asan/valgrind. And then they cry about how nobody takes them seriously.
I don't think you even bothered to look up what SQF is...
Anyhoo, you can't even follow a casual conversation that borders on technical stuff, I wouldn't want to go bare metal with you, fren 🙂
Best of luck to you and your endeavours, I think you might need it ;D
I'm talking about C, not your shitty proprietary DSL
Why would I need mathematical proof for C?
Logical is enough.
(I'm ignoring you shifing the goal posts again, because otherwise this conversation wouldn't even get off the ground. The things I do...)
>Yes, I asserted my program's correctness. What? No, I did not do any tests... no, there were no proofs either... and I didn't use asan while debugging because that's bloat...
>Just trust me it's correct, mkay?
Yes. My code works. There were hiccups, sure. But my code has been keeping machines safe, that have the potential to blow up buildings, for five years straight, 24/7.
It's a watchdog unit, it checks that a control PC for a machine changes a digital output every 1000ms (because if it doesn't, it means the PC has frozen).
The code overflows after 65535 milliseconds and has a finite set of states it can assume in accordance to that.
I *could* run whatever official test you want me to, but I know I didn't frick up.
Maybe you just don't know this code completeness feeling that you need these whatever tests. I have enough shit to do, my shit works with machines worth and earning millions, but none of them need certification like in the aerospace industry.
There's really nothing more I can add to that.
>and none of them need certification
Case closed.
LabVIEW, Siemens S7, all their underlying code, it's all C.
Not Rust.
They control nuclear power plants.
And I said I *could* certify it and it would pass with flying colors.
I just can't be bothered if I don't need to, doesn't mean I didn't write the code to be as perfect as possible so as to only have to do it once and never touch it again.
What have you done?
yeah thankfully after shit like Therac-25 engineers learned that cniles are mentally ill like (You) and thankfully all safety is in hardware so no matter how shit your code is, it won't matter.
>all safety is in hardware so no matter how shit your code is, it won't matter
Who do you think programs this hardware, JFC, lol, this is getting more and more ridiculous.
You don't know neither Verilog nor VHDL
Are all just formalizations of what you should be doing intuitively.
You know, I could just flip this around and say, well then, why even use Rust if safety doesn't matter?
Thanks, I'm flattered.
>You know, I could just flip this around and say, well then, why even use Rust if safety doesn't matter?
because I'm talking about this thing called embedded programming which is trivial compared to real programming, like writing real useful programs that are so complicated and need so many things in them and safety built in that people choose to write them in... C++ because C is for midwits who write most boring code that could be provided by the guys who created the hardware.
>are so complicated and need so many things in them...
skill issue
yeah just like in this example https://lwn.net/Articles/542457/ where C programmers admitted that they're incapable of maintaining their own compiler in their toy language inadequate for writing compilers in
everything you mentioned has built-in hardware safety that is impossible to override in software because engineers know that (You) are mentally ill and out to kill people
>engineers know that (You) are mentally ill and out to kill people
What the frick, man.
It's like he *hates* me more than I am ...annoyed by him.
Idk, it's the bed you made.
>others suck therefore you do
frick you too, crab
Yeah, well, embedded is the only safety critical thing that matters, everything else is peanuts.
Everywhere else doesn't risk limbs being chopped off, bombs detonating too soon or too late, heart-pacing machines beating too fast or too slow, kidney filtering bypass machines operating reliably, etc., etc.
All your other "safety" critical bullshit are memes compared to life and death.
So, sincerely, shut the frick up.
>Everywhere else doesn't risk limbs being chopped off, bombs detonating too soon or too late, heart-pacing machines beating too fast or too slow, kidney filtering bypass machines operating reliably, etc., etc.
*Correction, it does, when's being operated from a higher-level language/interface.
So the chain does extend upward.
I hope the Rust developer knows what he's doing when he interfaces wif my low-lewwel icky-fippy litty-bitty embeeddid C-progwammed EM-CEE-UwU *twerKs*
>Yeah, well, embedded is the only safety critical thing that matters, everything else is peanuts.
Most embedded software is not safety critical. It's toy software where nobody cares if it crashes.
>Are all just formalizations of what you should be doing intuitively
Hardware design and its logic doesn't come out of thin air Black person. It's not written in C.
>It's not written in C.
So it doesn't matter then.
It's not written in Rust either.
Ad absurdum.
C does not provide safety in modern low-level hardware designs. It also doesn't provide safety in complex programs. So why do you delusional Black folk keep lying that it's safe?
because it provides control
now go speedrun rust ack% somewhere else
C provides so little control you cannot even define a compile time constant in big endian without having to manually swap it when it changes
>C++ thread
>Rust Rust Rust Rust troony troony troony
They truly live in your head rent free. Friendly reminder that most embedded programmers trooned out, including cniles.
never mentioned troondom even once.
meds homosexual
and not of the hrt kind this time
C is not a hardware specification language
>verilog
>vhdl
https://github.com/GPUOpen-Drivers/xgl
total moronic monkeys like you, that's why all safety is in the unprogrammable part of hardware
C programmers thinking they are engineers is the funniest shit ever
C programmers are literal accountants of programming industry, they write most boring menial code like drivers and firmware which is just very spoopy words to the uninitiated but it basically boils down to writing basic functions like do_thing that wraps something like 3 bytes being sent to hardware directly which is a coded instruction for doing thing, very deep, requires very high intellect, and indeed, without C it's impossible to do, it's not like there's driver frameworks created in fricking Python because someone thought it would be funny to write drivers in Python because writing drivers is so complex even a Pyjeet can do it.
>The NASA study of the Toyota electronic throttle control firmware found at least 243 violations of these rules.
https://en.wikipedia.org/wiki/The_Power_of_10%3A_Rules_for_Developing_Safety-Critical_Code
How many drive hours does Toyota have vs. JPL's satellite and spaceship flight hours?
Certification requirements depends on external factors and should never be taken for absolute.
Which is something every actual engineer knows.
every actual engineer learned the hard way that if he won't make it safe, then it won't be safe, the end user is ALWAYS fricking moronic and in this case end user is the C programmer
>t. Therac-25 programmer's nephew
>Why would I need mathematical proof for C?
I mean, how do you think glibc fixed condvars in pthreads? someone had to define a working model of C execution and and parallelisms to spot a deadlock. to be fair, sophisticated condvars are fricking nightmare fuel, but anyhow.
>implementation 0 was so shit it needed fixing
lol, cniles truly are geniuses
look at how condvars are implemented. It's not a problem limited to C, honestly. It's just a very tricky problem with how multithreading and how the C++ atomics model works.
yeah I know some trivial stuff is too hard for cniles who can only think in single thread because that's just how limited their brain is
implementing a trivial condvar isn't hard... implementing one that's free of ABA tier bugs trying to avoid spurious wake ups is, however.... what are we arguing about again?
all condvar implementations have spurious wakeups
*checked what tf is a condvar*
lmfao
fricking toddlerlangs
Ya, it's about avoiding them when possible.
>working model of C execution
You mean a working model of the machine code created by C.
This is ridiculous.
>Hell, most Cniles don't even bother with using asan/valgrind
to be fair, using it is nontrivial, especially in some cases where timing dependencies are involved.
I really just don't understand why people deal with this unknowable unworkable garbage instead of taking the Rust pill, but whatever. miri works well enough in the cases where you can't "know" anyhow.
>Modern C++ is much, much harder to write properly than C.
I can agree with this to some degree. It's generally to the point where It's better to just ignore the standard's garbage and make your own.
I just ignore all the OOP crap and write as pure functional as possible. That solves literally 99% of problems anyone complains about. It's not my fault you all fell for the worst paradigm in history. A whole generation of coders writing spaghetti because university told them to inherent wheel from car and they drank the coolaid.
It's more than just the OOJeet. Fundamental shit like co-routines are unusable in C++.
This is what I mean bro. All my functions are pure, that means all my parallelism just werks. Don't even need to think about it.
Yep, late 90s to mid 2000s.
Then it was about making everything a webapp.
Now it's about rewriting everything in Rust.
In all cases, it was always about morons by morons for morons.
Yeah. Clojure saved me from this hell and showed me the light. Coding is fun again in any language. All I need is lambdas and all your classes can go to hell.
>C
>he doesn't write asm
>shiggy
ASM is the cherry on top, fren :^)
how is fasm anyhow? It looks pretty macro-y.
hand writing modern ISA shit looks cancerous though.
If you don't use the standard library or templates C++ is pretty much the most astheticc language there is
>Don't want your job outsourced to India?
>Mehta-programming
sounds like the opposite would happen
do the owners of these companies ever visit these office towers and see that its completely staffed by pajeets not doing anything?
>owners
who? the shareholders? they can't do shit anyhow as long as the executive team (who will all be pajeet) are making the money roll in and don't say anything that will imply they are undermining the shareholders'.
>fire anon
>hire 20 Indians on an HB for the same total monthly wage
>rewrite whole program in Java
>get government subsidies as a reward for ditching a memory-unsafe language
>>get government subsidies as a reward for ditching a memory-unsafe language
the last part is moronic, but the former is actually happening.
The Indian government is actually subsidizing offshoring tech work to India.
It's fricking horrifying how bad it's going to get if India keeps it up.
>the last part is moronic
https://www.whitehouse.gov/oncd/briefing-room/2024/02/26/press-release-technical-report/
ok, so you're moronic. stop shitting up this thread.
Don't shoot the messenger! Biden's the one mandating Rust, not me.
Holy shit frick off idiot. I swear to christ bringing back /misc/ (neo /new/) was a fricking mistake. I fricking hate Hiromoot for not genociding it already.
> make software "safe" from outside attack
> include CIA backdoor