3 ms·
We use it in my team and it works well enough, but iOS is a bit second class citizen. Everything translates to Obj-C (NSObject at the root), so even something a
by afro88 1y ago
We use it in my team and it works well enough, but iOS is a bit second class citizen. Everything translates to Obj-C (NSObject at the root), so even something as simple as a data class becomes NSObjects with a cumbersome dev experience rather than a native swift enum.
We're looking forward to native swift export to go stable - it's currently experimental / beta.
- deleted 1y ago[deleted]
- ignoramous 1y agoThanks. > looking forward to native swift export to go stable - it's currently experimental What are the timelines given for a stable release? And when it does, what else would you say are the next big things annoying/missing in terms of devex?
- afro88 1y agoNothing certain, but I reckon it'll be a while: https://kotlinlang.org/docs/components-stability.html#stability-levels-explained https://kotlinlang.org/docs/components-stability.html#stabil... The other big problem is debugging. It's impossible to breakpoint kotlin when debugging from swift, so some bugs that are realised only from the swift client side can be tricky and time consuming to fix.