The final hour of mental torture among many of finding a complex solution to an otherwise simple problem in a React/Typescript project:

  • 4
    I keep meaning to get into typescript but just don't get around to it.

    But man that reads on the surface like something trying to let you know what is 'incompatible' while obscuring whatever it actually is. I read that and think "Can't you just error out like a normal person?".

    Granted, this is probably because I don't know Typescript.
  • 1
    @N00bPancakes Omg yes! I spent 5 minutes trying to figure out what type something required
  • 0
    Oh shit... This is even worse than CPP trace when you're deep into templated stuff
  • 1
    React's typescript defs tend to be hacky. A good example is the poormansunknown type. They hard cast to avoid propagating an unknowable reference and pretend really hard.
  • 2
    @N00bPancakes in my exp Typescript is relatively pleasant to work with for own code, but it becomes annoying and messy when you need to fiddle with 3d party types and ensure compatibility (which is constantly with React & 100s of libs).

    That said Typescript is only pleasant insofar as I use VSCode.
Add Comment