C C Management: Fill & Download for Free

I have used each of them for 15-20+ years. There is no best. They have different strengths and weaknesses.C and C++ require a lot of discipline because you have to do memory management yourself.C++ is extremely powerful but also very complex.C and C++ are "dangerous" because, if you are not careful, your program can access and modify data that it is not supposed to touch.Python is elegant and designed to be easy to use and read. It has the least distractions when it comes to syntax.The syntax of C, C++ and Java look somewhat similar. Python looks different, it uses indentation instead of {} to group code.Python comes with "batteries includes", that means it has a lot of functionality build-in in the standard library.In Python there is 'one way to solve a problem'. On the other end, in C++ there are way more ways to solve the same problem. This added choice can distract you from solving the problem.Java has the best IDE support (e.g. eclipse or IntelliJ)C and C++ are also statically typed, but the preprocessor can add a level of complexity that can make it difficult to be sure what actually happens.In terms of speed C/C++ are fastest, but for most problems Java is very close in speed. Python can be slow, but if needed critical parts can be written in C. On modern execution speed is rarely the limit - cache behaviour, memory and disc access are the limits.If you want to learn programming, I would learn python first, then Java, then C and finally C++.I personally would not recommend C++ because of its complexity. However, if your are disciplined and have a strict set of rules for a project, C++ can be fantastic.I would use C only for low level stuff, like writing device drivers.Java is good for large projects, provided you write good APIs and you are carefully modularizing your software.Python is good for small projects. If the team and the software gets bigger, it can become hard to maintain unless you have a very good test coverage.

To quote Stroustrup: FAQThere is no language called "C/C++". The phrase is usually used by people who don't have a clue about programming (e.g. HR personnel and poor managers). Alternatively, it's used by people who simple do not know C++ (and often not C either).I wouldn’t say they are “totally different”, in the same sense as I wouldn’t say C and Java are “totally different” - they share a lot of the syntax and concepts inherited from their common ancestor, K&R C. I also wouldn’t fault an HR person composing a job ad for not knowing that “C/C++” is not a thing.It certainly isn’t “always C/C++”, though. Some ads actually write C++. Or actually write C, depending on what they really need.For example, a Bloomberg job, mentioning C++ and no C: Financial Applications Developer (C++) | London? or a QNX job, mentioning C and no C++: Systems Software DeveloperOh, found a Bloomberg job that wants something they call “C++/C”: Senior C++/C Systems Engineer | New York — perhaps they don't want Bjarne's quote to apply to them.Edit: here you go, a “C, C++” job ad https://www.dice.com/jobs/q-A2440A_%26%2345_Senior_C%2C_C%2B%2B_Engineer_%26%2345_Permanent_%26%2345_Austin%2C_TX-dsj-true-l-73301-jobs?icid=sr9-1p&q=Looking%20For%20:%20Polymer%20Chemical%20Engineer%20@%20San%20Marcos%20TX&l=78666

I believe there are a few reasons for this:Performance I. Java is slower than C/C++ compiled code in terms of start-up time. However, with a long-running server such as Cassandra, that is irrelevant. Java byte code on an optimizing JVM (Hotspot, etc...) can be almost as fast as C/C++ code, if not faster, depending on the exact configurations of the server / JVM / compiler.Performance II. Cassandra is also be disk-bound at least some of the time, making this discussion moot - C/C++ is not going to be any faster in getting disk I/O than Java.Security. It is definitely easier to write relatively secure software (i.e. buffer overflow problems, etc...) in Java than C/C++. It is possible to write secure software in C, but it takes much more time and effort to make it correct, which brings me to my final point:Ease of Development. Developing in Java (without worrying about memory management and so on) might be more productive than C/C++.I am guessing it all came down to a trade-off: Facebook (the original developers of Cassandra) needed the functionality provided by Cassandra quickly so they decided on a language that is reasonably high performance while allowing a high enough speed of development.Of course, most of the above is applicable to most server applications written in Java, not just Cassandra.