Skip to main content ↑ ↓
Topic: RPG Maker MV "They finally ditched Ruby for javascript!"  (Read 273229 times) previous topic - next topic
0 Members and 3 Guests are viewing this topic.

Re: RPG Maker MV "They finally ditched Ruby for javascript!"

Reply #15 –
Quote from: Rukiri – on
I would still say performance probably isn't as good as sphere

If there's already a performance gap here, it's only going to widen with miniSphere 5.0.  Chakra is blazing fast.  Which JavaScript engine is RPG Maker using, do you know?

Re: RPG Maker MV "They finally ditched Ruby for javascript!"

Reply #16 –
Can't say which engine it uses but I believe it's ES5 compliant but also read it has ES6 features so there probably was an update that updated it to ES6.

Re: RPG Maker MV "They finally ditched Ruby for javascript!"

Reply #17 –
Google tells me that RPG Maker is running on NodeWebkit version 0.12.3 (reference: http://endlessillusoft.com/rpgmaker-mv-es6-feature-list/ )

The NodwWebkit github's changelog tells me that this would be running on Node.js version 0.11.13 (https://github.com/nwjs/nw.js/blob/nw25/CHANGELOG.md )

The node.js website tells me that this would be v8  version 3.24.35.22 (https://nodejs.org/dist/v0.11.13/docs/changelog.html) which per V8 github is the 10th February 2014 version of v8 (https://github.com/v8/v8/blob/master/ChangeLog )

Performance wise that will be a dog compared to a current gen Javascript engine; there's been a LOT of performance related innovation in javascript engines in the last 2 years; also obviously that was early days for ES6 - before the spec was actually agreed... so it would have a few early features more there as an experiment/for testing than seriously implemented.

That said the list in the first article I linked is longer than I'd expect.

Re: RPG Maker MV "They finally ditched Ruby for javascript!"

Reply #18 –
@Rhuan That first link is a 404.