Why You Should Know C++
unknownprogrammer.com
Why You Should Know C++
1–10 of 63 posts
Re: Why You Should Know C++
#23. Code samples in books are more likely to be in Java or Python than C++.
6. Libraries are more likely to have native C bindings than native C++ bindings.
Re: Why You Should Know C++
#3Wow, I like C++ (at least, more than most), but I don't agree on any of those points.
In fact, I am sad to say that unless your job requires it, I can't really think of any reason to learn the language. It relies on a mixture of paradigms that are easier learned from other languages where they are isolated. And for lolevel stuff, you are better off learning C.
Re: Why You Should Know C++
#4[deleted]
Re: Why You Should Know C++
#53. Code samples in books are more likely to be in Java or Python than C++. 6. Libraries are more likely to have native C bindings than native C++ bindings.
I agree, most of the points seem to apply more on C than on C++.
Also this:
10. You will hardly be seen as a hacker if you don’t know C++
and this:
8. There will always (or, at least, for a very long time) be a niche for C++
Re: Why You Should Know C++
#6Wow, I like C++ (at least, more than most), but I don't agree on any of those points. In fact, I am sad to say that unless your job requires it, I can't really think of any reason to learn the language. It relies on a mixture of paradigms that are easier learned from other languages where they are isolated. And for lolevel stuff, you are better off learning C.
What's the point of using C when most modern programs on modern operating systems are written using frameworks that are a form of objectified C?
All serious development frameworks nowadays for desktop applications are either C++ or Objective C. Most native libraries are one of the two. Even the driver SDKs are mostly build on an object oriented approach.
And learning C++, you will know C. Your opinion is a popular opinion among web developers and people who do not do desktop development, but in the real world, it has a lot more advantages to learn C++ instead of C.
Re: Why You Should Know C++
#7Wow, I like C++ (at least, more than most), but I don't agree on any of those points. In fact, I am sad to say that unless your job requires it, I can't really think of any reason to learn the language. It relies on a mixture of paradigms that are easier learned from other languages where they are isolated. And for lolevel stuff, you are better off learning C.
What's the point of using C when most modern programs on modern operating systems are written using frameworks that are a form of objectified C? All serious development frameworks nowadays for desktop applications are either C++ or Objective C. Most native libraries are one of the two. Even the driver SDKs are mostly build on an object oriented approach. And learning C++, you will know C. Your opinion is a popular op…
Windows API is pure C. GTK is pure C. And these are quite serious (and not exactly obscure) development frameworks.
Re: Why You Should Know C++
#83. Code samples in books are more likely to be in Java or Python than C++. 6. Libraries are more likely to have native C bindings than native C++ bindings.
[deleted]
Re: Why You Should Know C++
#9In the context of code sampled, the difference between Java and C++ (and PHP and Javascript and a few others) is trivial and will hardly affect your understanding of the code. These are all part of a family of languages with C-style syntax.
Re: Why You Should Know C++
#10Wow, I like C++ (at least, more than most), but I don't agree on any of those points. In fact, I am sad to say that unless your job requires it, I can't really think of any reason to learn the language. It relies on a mixture of paradigms that are easier learned from other languages where they are isolated. And for lolevel stuff, you are better off learning C.
What's the point of using C when most modern programs on modern operating systems are written using frameworks that are a form of objectified C? All serious development frameworks nowadays for desktop applications are either C++ or Objective C. Most native libraries are one of the two. Even the driver SDKs are mostly build on an object oriented approach. And learning C++, you will know C. Your opinion is a popular op…
C is the lingua franca of computer languages. You can create bindings for almost any language if you have a c library. A lot of system libraries are in fact C, not C++: think of stuff like zlib, curl, openssl, libxml, iconv..
Sure, if you know C++ well, you'll be able to do C, but learning C++ is that much harder than C, that it's often not worth the effort. You'll be able to interface with most libraries once you know C, even if you use any other language as your primary tool. Learning C++ won't give you that much extra.