Midnight

They don't have a close relationship with each other. This question makes no sense.

Uhh, but you said interface inheritance, which isn't really composition... And favoring composition will definitely complicate the design. Your logic doesn't make sense. Subtyping creates coupling. That makes sense, but you didn't follow through with your argument. I already said that it's generally bad, which means it's not always bad to do so, and you've (sort of) agreed with me in your last sentences. Finally, using interfaces, sub-types, and/or composition will produce their own "clutter code". You FAVOR composition over inheritance, not FAVOR ONLY composition. Otherwise, we wouldn't be having this conversation. I suggest you read (or re-read) Design Patterns by the Gang of Four.

I think you're confusing subtyping with composition, for which they are NOT the same thing at all. If that's the case, then how can I take you seriously? As I have implied before, if inheritance is done right, then there's usually no problem. Also, reduced flexibility and increased coupling are GENERALLY bad, but it can be tolerated depending on context and system design. Your attitude implies that it should never be allowed, and sometimes this is impossible without over-complicating the design. Finally, you didn't explain why it is inherently flawed and just telling me to believe you... and I won't, without good, hard evidence.

omg, use a namespace

don't start out with pointers and you should be fine.

I disagree with inheritance as an antipattern. There's nothing inherently wrong with inheritance. It's just that people misuse it too frequently.

Why don't you just go with C#? It's better than Java, in my opinion. Python isn't bad, but the writing style is a bit too unique to learn as the first language.

upgrade to 64bit? lol

Then print the output? Not sure what the big deal is...

The problem is precision, especially when you input the mean.

Why are you comparing an interpreted language over a compiled language? It doesn't make sense. Also, you do know that the Python interpreter is written in C, right? If it took 2 hours to speed up a program that has a runtime of 4 seconds to 2 seconds, then yes, it would be worth it.

And I will tell you that is impossible. I don't think you understand the purpose of benchmarks.

You mean enjoy the slideshow at 5120x2160.

Still masochistic.

And playing at a whopping ~10FPS. How masochistic.