metaperl edited a comment on issue #9101: [SIP-36] Proposal for standardizing use of TypeScript URL: https://github.com/apache/incubator-superset/issues/9101#issuecomment-584239747 Given that [superset-ui is already 100% javascript](https://github.com/apache/incubator-superset/issues/9101#issuecomment-583637502), it appears this SIP is more about "standardizing" (enforcing type features of) the use of Typescript than deciding on something that meets the objectives stated in the overview. I.e, the overview stated: > We've seen significant improvements in code quality and a decrease in bugs by requiring Python type hints, and therefore propose to enforce a similar requirement for TypeScript. And so it seems that there is a desire for type-safety. And it appears that such type-safety is [optional in Typescript](https://www.typescriptlang.org/docs/handbook/typescript-in-5-minutes.html) as it is in Python. and the question arises why not use [Reason](https://2019.stateofjs.com/javascript-flavors/reason/) or [Elm](https://2019.stateofjs.com/javascript-flavors/elm/) so that the language itself enforces type-safety? Also, from the overview, I notice that Flow was rejected because: > it is only used by 35% of people (https://2019.stateofjs.com/javascript-flavors/other-tools/) compared to TypeScript with > 60% (https://2019.stateofjs.com/javascript-flavors/typescript/) Well, both Reason and Elm are used by much larger amounts of people, so that argument does not apply to them.
---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected] With regards, Apache Git Services --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
