3 ms·

Let's establish a couple things right off the start: 1. You can write great applications without the latest language features 2. The latest language features d

by pitaj 10y ago

Let's establish a couple things right off the start: 1. You can write great applications without the latest language features 2. The latest language features do make development easier Babel is necessary for #2 if you don't have control over the browser which your users use to access your site. If you don't want to transpile, don't. It's as simple as that. However, the future of JS is the future of web development, that is indisputable. Using Babel allows you to stay closer to the future and/or use these great new language features. You also brought up TypeScript. 3. Types make development much easier TypeScript is a combination of types and a transpiler for the ability to use the latest ES features. Types are great, providing: - Better self-documenting code - More safety - IDE interop to provide completion, as seen in VS Code > note: I expect serious down votes as opposing Babel is almost a serious crime nowadays and proves my unlimited stupidity. From the HN Guidelines: "Please don't bait other users by inviting them to downvote you or proclaim that you expect to get downvoted." > Maybe soon I will be forced to write in MS Typescript if I want to be taken seriously. Many would say that someone should be forced to write in a typed language in general in order to be taken seriously.

uranian 10y ago
typical.. I'm very glad you're not the person 'establishing things' in our team. > If you don't want to transpile, don't. It's as simple as that. Are you kidding? Please tell me your estimation of how many developers write in ES6/ES7 without using Babel or other transpiler??? You don't really need to tell me what Types are about, I have a long standing C/C++ background. And I really don't need Typescript. I use dynamic type checking based on ES3, does the job flawlessly already for years. Very rare for me to have a type related bug. I'm always wary of people that preach Typescript; what code do they write to get in so much trouble with types? > Many would say that someone should be forced to write in a typed language in general in order to be taken seriously. omg.. 'forced', this is bad. I'm only looking forward to webassembly, that will be the real game changer and the end of JS as we know it.
- pitaj 10y ago
  > > If you don't want to transpile, don't. It's as simple as that. > Are you kidding? Please tell me your estimation of how many developers write in ES6/ES7 without using Babel or other transpiler??? I was implying that you simply don't use ES6.

by pitaj 10y ago

uranian 10y ago

typical.. I'm very glad you're not the person 'establishing things' in our team. > If you don't want to transpile, don't. It's as simple as that. Are you kidding? Please tell me your estimation of how many developers write in ES6/ES7 without using Babel or other transpiler??? You don't really need to tell me what Types are about, I have a long standing C/C++ background. And I really don't need Typescript. I use dynamic type checking based on ES3, does the job flawlessly already for years. Very rare for me to have a type related bug. I'm always wary of people that preach Typescript; what code do they write to get in so much trouble with types? > Many would say that someone should be forced to write in a typed language in general in order to be taken seriously. omg.. 'forced', this is bad. I'm only looking forward to webassembly, that will be the real game changer and the end of JS as we know it.

pitaj 10y ago
> > If you don't want to transpile, don't. It's as simple as that. > Are you kidding? Please tell me your estimation of how many developers write in ES6/ES7 without using Babel or other transpiler??? I was implying that you simply don't use ES6.