We decided to slowly start moving away from CoffeeScript to JavaScript! As this step is impossible to do it in one go, here is the list of things needs to be done before we sign it off.
app/script/config.coffee (#888)announce/ (#899)assets/ (#912)audio/ (#925)auth/ (#947)bot/(#941)cache/ (#946)calling/ (#1125)client/ (#976)components/ (#1207)connect/ (#1030)conversation/ (#1172)cryptography/ (#1048)entity/ (#1195)entity/message (#1097)ephemeral/ (#950)event/ (#1078)extension/ (#1081)links/ (#963)localization/ (#1036)location/ (#951)main/ (#1084)media/ (#1065)message/ (#1086)properties/ (#1079)search/ (#1082)service/ (#1080)storage/ (#1083)system_notification/ (#1052)telemetry/ (#1089)tracking/ (#1085)ui/ (#1120)user/ (#1138)util/ (#1114)view_model/ (#1236)view_model/bindings/ (#1222)view_model/content/ (#1235)view_model/list/ (#1233)worker (#1374)test/apitest/unit_tests/ (#1201)announce/ (#1201)assets/ (#1201)audio/ (#1201)auth/ (#1201)cache/ (#1201)calling/ (#1201)client/ (#1201)connect/ (#1201)conversation/ (#1201)cryptography/ (#1201)entity/ (#1201)event/ (#1201)extension/ (#1201)links/ (#1201)localization/ (#1036)location/ (#951)media/ (#1201)message/ (#1201)search/ (#1201)service/ (#1201)storage/ (#1201)system_notification/ (#1201)tracking/ (#1201)ui/ (#1201)user/ (#1201)util/ (#1201)view_model/ (#1201)Gruntfile.coffee (#885)grunt/config/ (#1376)grunt/tasks/ (#1376)*.coffee files in the projectpackage.jsonpackage.jsonNot sure what the reasoning is, but CoffeeScript v2 will be out soon: https://github.com/coffeescript6/discuss/issues/71
Over at Bevry, we moved from CoffeeScript to ESNext for all our things throughout 2016. Our reasoning is at: https://discuss.bevry.me/t/move-from-coffeescript-to-es6/30/1 - perhaps will have some useful resources for your own move.
Thanks for sharing this. Haven't followed the whole v2 discussion. Was quite surprised to see that they actually started working on this finally. But this doesn't change our decision. What you mentioned is similar to what we discussed. Besides that some more reasons from our site are:
To sum it up. CoffeeScript introduced some really helpful concepts and made coding more convenient, but JavaScript nowadays offers so much more.







Finally 馃槃






Another milestone passed 馃帀


B盲盲m

DONE!
KAPUT!
Now i should start drinking less coffee -_-'
but but but Java is Coffee 馃棥
Let's have a celebration tonight 馃帀
Most helpful comment
Thanks for sharing this. Haven't followed the whole v2 discussion. Was quite surprised to see that they actually started working on this finally. But this doesn't change our decision. What you mentioned is similar to what we discussed. Besides that some more reasons from our site are:
To sum it up. CoffeeScript introduced some really helpful concepts and made coding more convenient, but JavaScript nowadays offers so much more.