# Type classes vs interfaces

**URL:** <https://discourse.haskell.org/t/type-classes-vs-interfaces/7323>\
**Category:** Uncategorized\
**Created:** [August 16, 2023, 7:38am UTC](https://discourse.haskell.org/t/type-classes-vs-interfaces/7323 "2023-08-16T07:38:12Z")\
**Posts on this page:** 1\
**Showing post:** 9

<div class="post-metadata">

**Author:** ![graninas](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.haskell.org/graninas/32/983_2.png) [@graninas](https://discourse.haskell.org/u/graninas)\
**Post date:** [August 16, 2023, 11:58am UTC](https://discourse.haskell.org/t/type-classes-vs-interfaces/7323/9 "2023-08-16T11:58:24Z")

</div>

I’m afraid, any explanation will be just words (as it happened in the topic here: [C++ 20’s concepts are typeclasses and make object-based polymorphism obsolete - shockingly!](http://discourse.haskell.org/t/c-20s-concepts-are-typeclasses-and-make-object-based-polymorphism-obsolete-shockingly/7128)).

My general advice to all haskellers is to practice more languages, OOP included, and broaden their horizons. The notion of a programming interface is super important.

---

_[View the full topic](https://discourse.haskell.org/t/type-classes-vs-interfaces/7323)._