Why my code isn't in TypeScript | Remy Sharp

Remy has some good arguments for why TypeScript can be just as much of an issue as it is a benefit. I've personally got a love/hate relationship with the abstraction, so it's always good to have some of my own feelings validated 😉 And it's good to hear from someone working "at scale" that these issues only compound, rather than smooth out, as that had been what I would have guessed.

On the confusing semantics:

A "well crafted" definition, type or interface (still no idea when I should use each), is often a huge cognitive load on me.

On one of the greatest frustrations:

Having to rewrite correctly and infallible JavaScript so that it was friendly enough for TypeScript to understand

Explore Other Notes

Newer

PWA quickstart

An interesting – albeit flawed – attempt at a zero-dependencies, web standards focused, PWA based UI framework, and a potentially useful quick-start template for using web components and native […]

Older

What powers do PWAs have right now

A useful single-purpose site that implements most (if not all) currently spec'd PWA APIs and lets you play around with them. Good for testing cross-browser quirks and for seeing a quick overview […]
  • Remy has some good arguments for why TypeScript can be just as much of an issue as it is a benefit. I've personally got a love/hate relationship with the abstraction, so it's always good to have some […]
  • Murray Adcock.
Journal permalink

Made By Me, But Made Possible By:

CMS:

Build: Gatsby

Deployment: GitHub

Hosting: Netlify

Connect With Me:

Twitter Twitter

Instagram Instragram

500px 500px

GitHub GitHub

Keep Up To Date:

All Posts RSS feed.

Articles RSS feed.

Journal RSS feed.

Notes RSS feed.