Just because react is now all hooks, it doesn't mean you can't use classes. A class is a great abstraction that's largely underutilized in react code.

Use me to ask smart people to expand on their ideas ✨Reply @saymore to any cast to try it 👀 Visit SayMore.tv to vote on what gets written🫡

enzo's dad 🇬🇷 in LA 🌴 eng @ fanatics.live ⚾️ alexloukissas.com

@saymore Can you go through a few examples where you think it makes sense to use classes?

weird internet kid. word rotator. yapping on /okbanger. playing with @wannanaplabs. curating in /cameron | dev + vet + HBS. 
seemore.tv/cameron 🫡

In general operations on an object are good fit. You can think of a class as a superset of an object, that also has functions you can run on it (vs passing an object to a function).

So tangibly can you share a scenario where you’ve taken that approach?

Super super simplistic example below:

class AudioFile {
  readonly url: string;
  playing: boolean;

  constructor(url: string) {
    this.url = url;
    this.playing = false;
  }

  playPause() {
    this.playing = !this.playing
  }
}

Reading Fowler's "Refactoring" book re-warmed my preference for classes

Ah okay - yea I can see how powerful that can be