Mixins Explained in 3 Minutes (NOT The Same as Multiple Inheritance)

[@TheCodingGopher]

Thoughts on the new editing style?

[@debbie8062]

i’m a fan of it 🙂‍↕️

[@patrickdecabooter411]

I prefer the old style

[@joostvisser6508]

The fade-in on the subtitles is quite distracting, I'd prefer them to just cut from one line to the next. Otherwise I like it!

[@yarden-zamir]

Hate the fade in on the subtitles. Means I can't immediately read it

[@bee_irl]

not a fan of these brainrot tiktok-style captions

[@sebastianmoser9652]

Thank you, very clear and simple explanation. Mixins look very similar to what PHP calls Traits.

[@TheCodingGopher]

My pleasure

[@patrickdecabooter411]

I always love your content, keep it up!

[@TheCodingGopher]

Cheers!

[@splytrz]

I'm still not convinced that mixin is distinct from inheritance. It's just a pattern that uses (multiple) inheritance.

[@splytrz]

To clarify, I don't have an issue with the video. Maybe with the title though. I'm coming from Dart, where mixins have special syntax, which has made me confused for a long time because I couldn't see how they're different, and the video title has made me hope I'll finally understand it. But nope! Especially seeing you use inheritance to implement a mixin convinced me more that the Dart team has added them as a hack to enable multiple inheritance.

[@splytrz]

I think the core of my misunderstanding was that I was thinking about a **different category**. There is no difference between mixins and multiple inheritance **as a language mechanism**, but, **as patterns** they are different. So, while everyone was talking about a design pattern, I was thinking about the language mechanism. (This is reasonable though, because it was prompted by the language design that presented them as a separate mechanism)

[@nathaaaaaa]

Mixins are the foundations of modern Minecraft modding, but we just see it as bytecode modification framework.

[@thefanboy3285]

:o

[@anon_y_mousse]

I suppose it's kind of like Rust's traits. Maybe you could compare and contrast different languages and how they use the concept.

[@TheCodingGopher]

Yes, these are very similar. Though traits in Rust achieve the shared behavior without inheritance. That's a solid idea for a future video

[@debbie8062]

missed you Gopher! Sad to see no daily uploads but i hope that means ur enjoying the holidays!! i really enjoy this type of video, can’t wait to see what type of content you’ll make this coming year

[@TheCodingGopher]

🚀🚀!

[@vvhat]

Its the cpp equivalent of interfaces

[@TheCodingGopher]

Similar, but not exactly. Mixins in Python are more like reusable code snippets added via inheritance, while C++ interfaces (i.e. pure virtual classes) define a contract that classes must implement. Mixins add behavior; interfaces enforce structure.

[@davidrieger3160]

Any reason to use this over composition (e.g. make the logger class a field rather than inheriting from it)?

[@arijitgogoi5653]

All right let's mixin

[@TheCodingGopher]

Let's go mixin

[@lepch]

so mixins are just pytest fixtures

[@TheCodingGopher]

Not quite. Mixins are a way to add reusable behavior to classes through inheritance in OOP, while pytest fixtures are specifically designed for setting up / tearing down test preconditions in pytest. Fixtures are automatically injected into test functions (which is the core part of the pytest framework), whereas mixins are a more general programming construct used for sharing code across classes. They can overlap in functionality in some cases - but they're fundamentally different.