scomment

Hello, it's 2016. Did you heard Java or C#? Or even Delphi?

Okay, now give me some collection like object, who can handle everything. No, don't use void*.

There are some benefits if everything is an object, like generics.

And you started slow reinvention of OOP!

> Why would you want to cast mixer to something else?

Did you ever heard about interfaces? You can have a IMixer interface, a Mixer baseclass and some concrete mixer classes depending on your task. Like null-mixer for mocking, software mixer for legacy computers, hardware mixer with GPU support, etc. Use your imagination, Luke!

Okaaaaaaay, so if we left everything what OOP gived us (properties^1, generics, lot of good patterns^2, lot of abstractions for generic things, like interface^3, events, higher level datastructures, delegates, namespaces, modules^4 etc.) then we get C? Omg, thank you Captian Obvious! Learn OOP first.

What a bullshit article.

1) C++ for OO example? Seriously, why??? Grab a modern language who have properties at least. Even Delphi had it!

2) IMHO without OO patterns OOP worth nothing

3) I know, you can do interfaces in C++ with pure virtual classes, but you miss the abstraction behind that.

4) Java JAR, .NET assemblies, no matter what they called.