0
Legacy C/C++ code is a nuclear waste nightmare that will make you WannaCry
interesting article that I read today. http://trevorjim.com
4 Antworten
+ 7
To add to Jacob Pembleton's answer, C is also being updated. We all know C89, lots of people know C99, lots of people have at least heard of C11 and C17 is coming soon !
+ 7
I dunno if I'm I the only one who smells advertising in that article, but the last paragraph sure did boast safe language big time, I strongly believe that article has a (not so) well camouflaged message hidden, and it goes like "use safe languages, unsafe languages bring nothing but trouble".
Just my opinion, never mind, black marketing campaign is everywhere and it's done anytime, it's nothing new : )
+ 6
What makes me want to cry is the fact that Python is more popular than C++.
https://www.sololearn.com/Discuss/280672/?ref=app
EDIT 1
After reading that article, I disagree.
It talks about reimplementing codes in safer languages, but that is highly unnecessary. C++ is still being updated every few years, so instead of reimplementing in a safer, likely worse language, why not just allow C++’s security issues to be fixed? They are constantly working to improve C++’s downfalls, which are security and simplicity.
Fixing these doesn’t have to mean breaking codes that already exist but no longer work, the fixed versions can go in different libraries. For example, fctime (fixed ctime) instead of ctime. That would allow developers to switch when they want. You would have to give time before removing the old unsafe versions, but this doesn’t have to happen soon, we’ve lived with these issues for decades, what’s one more?
EDIT 2
I just looked through some of the other articles, and they seem very biased. Their rants about C/C++ (which seem to be what most of the pages are about) sound like my rants about Python. Good arguments but highly biased.
0
all of you have very good views. although thanks for comments. :)