JS translator will be?

or it stopped too?

"The JavaScript backend can now compile code to modules which are compatible with AMD, CommonJS and UMD module systems. See the documentation for more details."

so some development is in progress regarding Javascript backend

but I cannot say much about it, haven't tried and didn't do any reading in this regard

but at least it means that it's not killed completely 🙂

sounds good

@akoncius u wrote "I think you will face resistance here - language is too young to go "all in" - that's why i want to represent it to our company. if i will do it correctly, and put this idea (reuse HTML and CSS normally) in developers heads, we can help community to grow

and make it "all in" faster

sure

just make sure everybody understands risks

I've seen many talks on internet when people were talking how they used first versions of node.js in production

and it was horrible because node.js was constantly breaking api, and they needed not only maintain app as a business app

😁

but also they had to update their project because nodejs was breaking

that's why I suggest to move to Kotlin gradually

smaller risk

better stability in your production apps

better sleep at night 😉

now Kotlin is quite stable regarding API

but for example frameworks are quite young and can change their API quite frequently

so you will have to add this risk in decision making when choosing language/platform/framework

at the end of the day your job is to make sure that application works, not "work with shiniest tech"

so now it's best to use Kotlin and frameworks on toy projects or small apps which can be replaced in several days

to test and make sure platform is working properly

and then gradually increase size of projects

this is my view

another example when "all in" goes wrong is when in earlier days of MongoDB some project was in production and used MongoDB and it reached one point when on certain amount of writes whole database got locked

and project faced some serious downtime