I want to write first about my admiration of ducks, and swans by extension. They are the animals capable of flying (birds), and they also swim. They also walk on land. Ducks, and also swans, are therefore truly all-terrain, all-element animals: they've conquered earth, water and air. (And they're metabolic, living organisms so we'll grant them the command of "fire" in the sense of metabolic oxidation.)

You may be familiar with the saying, "duck typing". The idea is that if something walks like a duck, talks like a duck... then it may be a duck.

Modern interpreted langugaes (python, ruby, javascript, php) are untyped: the programmer doesn't have to specify the type of every variable, when writing his program. This saves a lot of time, reduces the length of the code, and affords other benefits to code writers, maintainers and stakeholders.

Less code means less maintenance. Therefore, it is cheaper to maintain a small program, than large. Less code even means less chance of making a typo, when writing it.

Paradoxically, typescript goes against the concepts described above, and introduces strong typing to the javascript language. We see this largely as a bad move, and a deterioration of the javascript ecosystem.

We are aware of the limitations of javascript, but do not consider typescript a move forward - in fact, it appears to be a move back.

Parallels can be drawn between this and, the deterioration of the society, politics, and regulatory capture.

Microsoft invented and owns typescript. Microsoft is interested in shutting off easier technology, and raising the barrier to entry (to programming).

TS is convoluted. No personal project should use TS.

And remember: TS cannot run in an interpreter. It has to be compiled into javascript, to run in a browser. There are more than one negative outcomes of this: TS cannot be used in a REVL(?) loop. A piece of a programm cannot be easily copy-pasted, fracturing the ecosystem.

What is an ecosystem? number of libraries. amount of support. stack overflow is a great resource.

MS tries to further marginalize javascript, by introducing their own text editor. Their text editor, wrongly assumes that JS code is TS code, first. This is incorrect! But it excerts pressure on JS purists, and all employees of technology companies at large, to cancel javascrit.

Code clarity is better achieved with department-wide policies, than a make-belief structure of a language.