Thus, TS should not have any influence over how JS evolves, but unfortunately that ship has sailed it seems.
Thus, TS should not have any influence over how JS evolves, but unfortunately that ship has sailed it seems.
Javascript library maintainers should not be berated like they (we) are when types are not added to libraries, for example, but these days it's an unspoken requirement.
Typescript community manages external typings for tons of libraries that don't want to support ts themselves. People can be referred to create type definitions themselves under DefinitelyTyped.
[0] https://docs.github.com/en/github/site-policy/github-communi...
Their bullying and harassment guidelines are very clearly toward ad-hom types of remarks and beyond.
Being on the receiving end of a dick comment about how not having typescript types is unacceptable and how I need to have them for one reason or another is never fun - but, assuming they don't personally attack me as an individual, I'll fight tooth and nail for them to make those comments as it pertains to the community guidelines.
That's not to say I appreciate them or let them influence my maintainership, but they shouldn't be disallowed or cause for punitive action by any means.