- Joined
- Mar 28, 2016
- Messages
- 1,641
- Reaction score
- 1,479
- First Language
- French
- Primarily Uses
- RMMV
Yes that would be great is MV supports ES6, really. Is it planned ?
Yes that would be great is MV supports ES6, really. Is it planned ?
@Jonforum: Saw that but you need to use "use strict". It's causing a lot of issues.
Issues like what? If it's throwing errors, then it's pretty much trying to warn you that you're doing something dangerous.
@nio kasgami Modern browsers support about 95+ % of all ES6 features. What nade you think most features were not supported? The problem is mobile devices and outdated browsers, if you want to reach all platforms and a wider audience you need to transpile your code to ES5. I would love to see ES6 in MV too, it would be a great next step and when browsers finally support ES6 modules, plugins will be a whole new story.
@nio kasgami Modern browsers support about 95+ % of all ES6 features. What nade you think most features were not supported? The problem is mobile devices and outdated browsers, if you want to reach all platforms and a wider audience you need to transpile your code to ES5. I would love to see ES6 in MV too, it would be a great next step and when browsers finally support ES6 modules, plugins will be a whole new story.
Supporting modern browsers in anything is not typically a problem, but you very rarely make anything exclusively for the newest line of products (be it graphics cards for native games, or web browsers for MV). There's always going to be backward compatibility involved because you can't expect everyone to shell out money in order to be able to play your game. Sure, updating a web browser is free, but that still doesn't mean people will do it. People are notorious for not updating things. Look at Java, for example. How often do people just close the update prompt window instead of just updating it to make it go away? And making the user perform more steps to be able to use your product is a quick and easy way to lose audience interest fairly fast.
I'd rather have code I can understand in ES5 than the crap that comes out of a transpiler.
Lol it is definitly ugly, you will always have the main ES6 file though , just when its ready to be released and you want full compatability you can transpile it. Right now though most features work with nwjs so you dont need to transpile it for testing and even if you did sourcemaps will have you covered. I only wrote one plugin with ES6 and it was pretty fun but as you mentioned its easier and more manageable to have readable ES5 code.
Issues like what? If it's throwing errors, then it's pretty much trying to warn you that you're doing something dangerous.
Let's check the ES6 Table and reconsider if it's worth it. Notice the mobile section...
Any word on the updates with the Child generator options? How about the music/graphic errors?
Seriously? so the "elf ears" for adult is more important than Sound lags/ Memory leaks bugs?
.........
you should really try to understand the prioritization of game software dev in general.
This^