I dunno - I think its much simpler than ES6 and I can free-hand pretty well. I really do not see the benefit - or have the desire - to move to ES6.
On another note, I have no issue with Blaze, or globals, since Meteor’s packages are pretty good for filling in what imports/exports do. But dynamic imports are very attractive.
@msavin Meteor has gone to extreme lengths to preserve the old style of programming that you seem to love. What if you met us halfway and gave the modern stuff a try?
Yeah man - I really appreciate it! I respect the new way - but as you can tell I am comfortable in my “old” ways. I’m always a bit anxious that the ES5 way will be “removed” from Meteor, so it feels great hearing that.
When you say modern stuff - do you mean learning ES6 or trying some things in specific? I would be open to try it.
Just start writing async functions and await expressions! They’ve worked in Meteor since 1.3 (IIRC). The generated code isn’t lovely, but the good news is you won’t have to rewrite your own code to take advantage of native support, when browsers eventually catch up.
Nice. I’m now using the imports directory, modules, and ES6 whenever possible in my Meteor 1.3 application, but it’s taking a while to refactor everything.
So ES7 is included? Great! Do you know of a good resource to learn all about Async/Await in ES7 and maybe even how to make use of it with Meteor today?
Also, does anyone have an idea when Meteor 1.5 is dropping?