Sorry. No language with dynamic typing can be best. You have to pick something else.

Rust is best, C++ worst

t. virtuallynothing about the subject knower

Define best/worst.

 

t. party pooper

best=your favorite

worst= your least favorite

Then

best - C++

worst - C++

 

t. oo deep into the hole to look at other languages

Example: if you don't follow this, you will likely get crazy memory errors.

I recently discussed this with someone that is currently in a C++ training course. For me it is the rule of none: Never declare a destructor, copy constructor or copy assignment operator yourself. Then you don't have to deal with that shit.

Are you serious?

One day you will need to.

 

Just give papa Bjarne another 10 years, he will sort it out eventually so we won't have to write all that extra bollocks.

I liked c++ until I discovered languages with garbage collectors that forbid people to do any low level memory manipulations

I used matlab all the time in uni and absolutely loved it; what's wrong with it?

 

don't know why but it always feels like cheating

This sounds something that could be relevant.

Matlab has a horrible performance when you use loops to process your data. That means if you have some problem with lots of data that you want to process you have to completely rethink you problem into using matrices and matrix operations because that is the only thing where matlab is somewhat good at. Doing so makes you code superhard to understand and difficult to debug.

 

If you have any complicated C program the return value of most of the functions often turn into some kind of error code so you can notify the calling function, or the calling function of the calling function, or the calling function of the calling function of the calling function, that something wihin you program went wrong. This does not only mean a lot of boilerplate code to write it means also that all returnvalues have to be given as a parameter by reference which makes the code even uglier. Having exceptions along with a stacktrace make errorhandling and debugging so much more easier you wouldn't believe.

Whataboutism.

argue properly, lazy boy.

There was no whataboutism in my bost. The right side of you picture complained about exceptions and I wrote why they are ans good idea.

Also here is the equivalent to your picture when you replace OOP with using bricks in buildings.

When you use your tools like a retard it is not the fault of the tool itself.

Pic was: "OOP is shit"

You were: "whatabout C?"

Replace 'C' with 'non-OOP language' and the point still stands lazy boy.