[dfgdfg34545456]

It does smell like someone's pet project. I'm wondering what the folk at Microsoft had not figured out, that they indeed had at Figma. Typescript is open source, so why wasn't this optimisation just made as a contribution to Typescript at the time?

Also, was Typescript really as claimed in its "infancy" at the time mentioned in the article? They didn't mention a particular year.

[mirekrusin]

Let's not paint pet projects black. Most things we're using today were somebody's pet projects including linux, llvm/clang, swift etc.

[dfgdfg34545456]

>Let's not paint pet projects black.

I don't follow. Where did I do this?

[Drakim]

> It does smell like someone's pet project.

"Smell" has negative connotations in English. If you say that "this code smells" it means it's bad, and likewise it's very easy to read your "It does smell like" as you meaning it's a bad thing.

[dfgdfg34545456]

Thank you for the English lesson, but it's a big leap from this supposed connotation to "painting pet projects black".

[mpalmer]

Not so great a leap; every part of your comment implies you think they made a strange decision going the route of using someone's pet project.

[wewxjfq]

It's something Typescript doesn't want to do. Their goal is to remove the type annotations, maybe add some code for backwards compatibility, and otherwise do as little as possible to stray from the untyped JavaScript equivalent.

[apantel]

With enough investment, a pet project can become a mature platform.

[p_l]

Unix and C were pet projects until they enabled secretaries to better write patent proposals.