Sign In Register

How can we help you today?

Start a new topic

Cloud code support for Javascript ES6

It's probably a long shot, but ES6 contains many improvements over ES5, and it would make coding for GameSparks less painful for nontrivial projects. Once you get used to ES6 features, it's really hard to go back to the stone age. :) So, I'd like to suggest an upgrade.


10 people like this idea

Ohhh, maybe there's hope! :D
https://groups.google.com/forum/#!topic/mozilla-rhino/Z-Rq8sfIWUk


I would also like to see this, any news from the GameSparks team?

Any clue on this?


Best,

Ignacio

Any news on this? 

Hi,


The Cloud Code engine has recently been upgraded to Rhino 1.7.7.1 . You can read more about the upgraded features here.


Regards

Liam

Gah, still no template literals. RIP, Rhino development is incredibly slow.


var myName = 'Jon Snow';

var greetings = 'Greetings, '${myName}'!; // Error


Have to type it as:


var greetings = 'Greetings, ' + "'" + myName + "'!"


I'm about to make a giant parsing string to post a thread on our Discourse forum for reporting. This is not going to be fun without template literals ~


1 person likes this

sorry to necro a thread but i find template literals a necessary feature as well. Really helps make everything so much better. 



2 people like this

I second that request. I also think, that at switching to V8 might be the better long term solution. Not only is V8 considerably faster than Rhino, it also is more feature complete (as in: supporter a newer ECMAScript).

A switch a could also lead to a better CloudCode structure, with proper modules, not a single folder and a pseudo include with "require("Stuff")". This in turn would also improve support for Typescript, CoffeScript et.al.


I'm willing to wait a bit for a switch to happen, but currently I'm seriously considering switching to Nakama because working around the quirks of CloudCode is eating my time.


5 people like this

ECMA5 is painful. It actually came out in 2009. Since then, technology has not only changed to be more convenient, but there are certain new standards to follow that has been out for years that we're now having to go back in history to code using decade-old technology.


It's embarrassing to tell others when we're coding with this in a platform that's meant to be next-gen.


With Amazon's new acquisition, I'm surprised this isn't made a priority: Not just for existing customers, but for future ones. ECMA5 is a ticking timebomb.

 


2 people like this

Not sure what it takes to push a request like this through, but hopefully it is on the cards. 

Login to post a comment