ES6 will be nice when I can write it without the worry of a compilation stage. I still use MooTools on my personal projects. I don't care. I get shit done.
Turn your ES5 code into readable ES6
21–30 of 31 posts
Re: Turn your ES5 code into readable ES6
#22I am asking as a poor JS developer - what are the benefits of this newer style?
Readable, and intuitive. The syntax is like a standard class (constructor, methods, getters, setters) you'd see in C or PHP.
What is the benefit of using classes rather than just bunch of functions, calling each other?
Re: Turn your ES5 code into readable ES6
#23Earlier quoted context omitted.
Readable, and intuitive. The syntax is like a standard class (constructor, methods, getters, setters) you'd see in C or PHP.
What is the benefit of using classes rather than just bunch of functions, calling each other?
There are strong arguments for both, but if you're going to decide on classes, ES6 classes are preferable to ES5 style.
Re: Turn your ES5 code into readable ES6
#24Re: Turn your ES5 code into readable ES6
#25Earlier quoted context omitted.
Readable, and intuitive. The syntax is like a standard class (constructor, methods, getters, setters) you'd see in C or PHP.
What is the benefit of using classes rather than just bunch of functions, calling each other?
That's a big question, its usually a first year software engineering degree assignment. Its the question of object orientated programming vs procedural programming.
The main thing with having classes is about encapsulating functionality into objects which can be tested, reused and extended as a component in its own right.
Re: Turn your ES5 code into readable ES6
#26Earlier quoted context omitted.
Readable, and intuitive. The syntax is like a standard class (constructor, methods, getters, setters) you'd see in C or PHP.
What is the benefit of using classes rather than just bunch of functions, calling each other?
Often when you use a bunch of functions together, you end up passing the same arguments. Those arguments represent some kind of state that your pass around from functions to functions. Sometimes you might even add an argument to a function just to pass it over to another function. After a while you might get tired of changing your function signatures and it makes sense to group those common arguments into a single data structure that can be accessed by your bunch of functions working together. While you're at it you might as well put the functions in that data structure too, so you can see clearly how they relate to each other. That's basically what a class is for.
Re: Turn your ES5 code into readable ES6
#27upvoted. Damet garm amoo :D
Re: Turn your ES5 code into readable ES6
#28Neat. How about translating "require" calls to "import" statements (and exports statements)?
i did that yesterday by hand with 3 find-replace-all regexes. it isn't that big a deal :-)
(that said, not all uses of require can be translated to import statements)
Re: Turn your ES5 code into readable ES6
#29I have started a similar project, but stopped working on it, and seeing this I decided to put it on GitHub, even though it's not very well tested and not feature complete. The most complex feature in my code is the ability to turn var into let/const optimally using an esgraph-based dataflow analysis, and it also has the ability to introduce arrow functions, shorthand/method properties and classes. It is implemented a…
That's great! It's kind of you. I will use that.
Re: Turn your ES5 code into readable ES6
#30Sadly I get an error "Cannot find module './block-statement.js"
I fixed it