Move to ES6/7 (babeljs) and webpack

[socketpair]

This may significantly reduce and simplify code base, especially asynchronous parts due to usage of await paradigm and many other ES6/ES7 things.

[s-macke]

I observe the ES6 compatibility in the web browsers approx. every half a year. Looks like some browsers are still missing support for async and promises. So I would say it is too early to switch to ES6. Also I am not sure, if this would solve any of the timing problems I encounter. http://jor1k.com/jor1k-orconf2015.pdf Slides 30 to 36

[socketpair]

I understand,but babeljs transform ES6/ES7 code to ES5. That's why this code CAN be run in browser.

[socketpair]

When I talk about ES6/ES7 I mean code (user interface) around jor1k core, and maybe also some asynchronous tasks like getting blobs from server. I don't consider moving emulator itself to ES6/ES7 . At least for now.

[neelabhg]

@socketpair BabelJS will be useful, however I'm not sure how performance will be affected. Even in the best case, we'll lose the ability to control exactly what gets executed by the browser (due to transpilation), thus losing control over performance.

Although I agree with your comment that the non-performance-critical parts (initialization, getting blobs from server, etc) can be migrated.