a guest that come from average and boring house, without invitation, to your glorious and successful estate, and immediately starts rorganizing and enforcing the rules and regulations that he know from his environment

Is like dev community that working to convince you use TYPES on your sharpened JavaScript architecture .

What part of duck-typing is glorious and successful?

https://destroyallsoftware.com/talk...

It's a good thing to catch errors at compile-time instead of on runtime and potentially in prod...

It is a rumor that all people who do not know better repeat .

The propaganda of microsot interests, whose IDE can not handle JS without Types. and they try... ho they try . so they decide a new strategic : if they can't write interpreter that understand JS let's teach the people how explain the JS to the machine. and that is absolutely for machine because it much easier to read JS without types. much easier

I and all serious JS programmers do not remember mistake in Typing on production.

that kinds or error JUST DOES'T HAPPEN

Dynamic types are evolution over types,not the opposite. so dynamic Types are a POWER not weakens

@perymimon I guess none of the people I know who make a living doing JS are "serious JS programmers then" because it's one of the most common errors I see, particularly when it comes to assuming that a null or undefined value is some other type. Frankly, I'll believe your code is bug-free in this area when I've seen it.

That it the common error on production ??

and when the type can be `config object` `number` or `string` how can it be possible to mistake.

or all the people you now involved with a lot of intense use of custom classes .

and if that is the case maybe that is the problem .

@perymimon or maybe they write less trivial applications than you do, or maybe you're in denial about the quality of code you're writing. No custom classes? I would hate to see what your API source code looks like because that sounds like a recipe for spaghetti. If you could really write better code without any need for types, you'd post the source so people could learn from it. Because clearly it's a common problem if people found the need to create Typescript to deal with it.

Honestly to me it sounds like you're a mediocre developer who only knows JS and doesn't actually understand type systems, and you're just angry because Typescript is too confusing and difficult for you. Based on this rant and your others.

first of all , the community of JavaScript live just fine before 1.5-2 years. aka before Typescript got common aka before angular make everyone use it.

so if you like to learn how to program good quality code that explaining himself just open some random high rank project in GitHub and start reading . I'm sure you finish it quickly, and probably will learn something

And I don't thinks the dashboard applications that everyone made today are more complex dashboard applications that we build two years ago.

and line about me : i'm start coding before 20 years from 16 age . learn and write pascal, c, c++, assembly, java, and before 10 years I landed in JavaScript for good. so I consider my self as expert in that area and really not a guest like all java programmers who just discovered how wonderful JS is. and come to contaminate it with their cumbersome habits.