2018-11-24
2144
#typescript
Dmitry Pashkevich
327
Nov 24, 2018 â‹… 7 min read

7 bad excuses for not using TypeScript

Dmitry Pashkevich Web developer. Productivity geek. Linux user. Tea drinker. Amateur photographer.

Recent posts:

Fix over-caching with dynamic IO caching in Next.js 15

Next.js 15 caching overhaul: Fix overcaching with Dynamic IO and the use cache directive.

David Omotayo
Aug 6, 2025 â‹… 10 min read
LLMs are facing a QA crisis here’s how we could solve it

LLMs are facing a QA crisis: Here’s how we could solve it

LLM QA isn’t just a tooling gap — it’s a fundamental shift in how we think about software reliability.

Rosario De Chiara
Aug 4, 2025 â‹… 7 min read

Windsurf vs. Cursor: When to choose the challenger

Windsurf AI brings agentic coding and terminal control right into your IDE. We compare it to Cursor, explore its features, and build a real frontend project.

Chizaram Ken
Jul 31, 2025 â‹… 9 min read

The CSS if() function: Conditional styling will never be the same

The CSS Working Group has approved the if() function for development, a feature that promises to bring true conditional styling directly to our stylesheets.

Ikeh Akinyemi
Jul 30, 2025 â‹… 12 min read
View all posts

3 Replies to "7 bad excuses for not using TypeScript"

  1. “This makes the learning curve extremely lean”

    Most people don’t know what “learning curve” means. A steep learning curve actually means that learning increases rapidly with experience, i.e. it’s easy to learn.

    A “lean learning curve” can only mean the person who drew the graph with a sharp pencil and produced a thin (“lean”) line. 🙂

  2. JiveturkeyJay – 100% agree – TDD should be the first thing people look at if they aren’t doing it.

    The number of places using Typescript – lots more code only to catch a handful of bugs – when they aren’t even doing unit tests – which catch real problems and give you confidence refactoring.

    It’s kind of crazy.

Leave a Reply