I think I will just scrape all the kotlinjs stuff
# science
b
I think I will just scrape all the kotlinjs stuff
a
Well, I managed to work with it. The main problem is the quality of js libraries, I think that it will be much more comfortable with more mpp libraries. Feel free to post here if you need something specific. For device control we are going to work with tango/waltz. They have a lot of widgets already written in js and are willing to adapt them to the protocol we will develop together.
b
Calling from JS is pain. So yes as long as you stay in kotlin world, everything works beautifuly
a
Never tried to call from JS. The other way arround works reasonable (not good yet, but could be managed)
b
didn't try to call JS from Kotlin outside of callbacks
a
It is quite OK if you have d.ts definitions. I believe that experience is at least as it is on TS. The problem arises when JS part does not honor types.
b
I don't use TS (yet?)
for now my calls are really simple so I didn't have any type issues
a
I did not have any significant issues with integration yet. Most of my frustration comes from JS ecosystem itself. Also js plugin is in the progress of migration, so I am waiting for 1.3.70 for better documentation and dce in multiplatform.