



TypeScript provides the following advantages over vanilla JavaScript:
Execute Program did a great break down of the benefits of using unions instead of enums. Their main argument is TypeScript is supposed to be JavaScript, but with static type features added. If we remove all of the types from TypeScript code, what's left should be valid JavaScript code. For example:
function add(x: number, y: number): number {return x + y;}
function add(x, y) {return x + y;}
Enums break this rule. If enums were removed like other type features, you would have JavaScript code referencing nothing:
enum HttpMethod {Get = 'GET',Post = 'POST',}const method: HttpMethod = HttpMethod.Post;method; // Evaluates to 'POST'
const method = ???;method;
I agree with Execute Program. I don't believe the benefits of enums outweigh the complication they add to the TypeScript complier model and the possibility of difficult bugs hidden in build steps.
Have any feedback about this note or just want to comment on the state of the economy?

