Should Phaser move to TypeScript or ES6?
As I start to plan Phaser development in 2019 I'd like to get your opinions in a quick poll.
I've always maintained that, when things settle down, I will recode Phaser 3 to get away from the ES5 prototype based classes that it uses today. When that time comes, would you personally (and professionally) prefer that it is rewritten in TypeScript or ES6?
To clarify: This would be an internal change. It shouldn't touch much, if any, of the public API. Ready-built dist files will still be published to GitHub, npm and the CDNs as plain JavaScript. What will change is how those files are generated. Either from a TypeScript source base or a more modern ES6 JavaScript based one.
Important: If we end-up using ES6 we will still provide TS defs!
Please understand that the results of this poll will not be the overriding factor when it comes to choosing. But I'm still really interested to hear what you think!
ES6 (130) TypeScript (80) Leave it as ES5 (9)
219 votes total
As I start to plan Phaser development in 2019 I'd like to get your opinions in a quick poll.
I've always maintained that, when things settle down, I will recode Phaser 3 to get away from the ES5 prototype based classes that it uses today. When that time comes, would you personally (and professionally) prefer that it is rewritten in TypeScript or ES6?
To clarify: This would be an internal change. It shouldn't touch much, if any, of the public API. Ready-built dist files will still be published to GitHub, npm and the CDNs as plain JavaScript. What will change is how those files are generated. Either from a TypeScript source base or a more modern ES6 JavaScript based one.
Important: If we end-up using ES6 we will still provide TS defs!
Please understand that the results of this poll will not be the overriding factor when it comes to choosing. But I'm still really interested to hear what you think!
ES6 (130) TypeScript (80) Leave it as ES5 (9)
219 votes total