• Zach Klippenstein (he/him) [MOD]

    Zach Klippenstein (he/him) [MOD]

    1 year ago
    Thanks for sharing the roadmap! Lots of exciting stuff in there. I’m not sure what “Prototype multiple receivers” refers to. Does it have anything to do with this? https://kotlinlang.slack.com/archives/CJLTWPH7S/p1601136306105500?thread_ts=1601067741.085300&cid=CJLTWPH7S
    Zach Klippenstein (he/him) [MOD]
    Ahmed Mourad
    3 replies
    Copy to Clipboard
  • s

    serebit

    1 year ago
    It would make more sense to me to focus on hierarchical multiplatform and stabilizing the commonizer to make overall multiplatform development easier, rather than developing tunnel-vision on a single use case.
    s
    akapanina
    9 replies
    Copy to Clipboard
  • a

    audriusk

    1 year ago
    (for me) this road-map looks like my personal wishlist 😄 Almost... •
    Direct interoperability with Swift
    Would like to see this. But it's understandable why postponed. Probably very big task which focus on very narrow use-cases and doesn't fit in whole new IR backend theme. •
    KMM plugin: support for IntelliJ IDEA
    But this... I don't get it. If goal is to build multi-platform applications. Then developers from other platforms (not android devs) will have to join. And these backend/web devs uses Intellij IDEA, not Android Studio...
    a
    1 replies
    Copy to Clipboard
  • louiscad

    louiscad

    1 year ago
    @elizarov I think you'll like that change. Also, I believe the name
    primitive class
    is less confusing for value types, and
    inline class
    makes more sense for Kotlin's usage.
    louiscad
    elizarov
    3 replies
    Copy to Clipboard
  • gaetan

    gaetan

    1 year ago
    The road map is what I’m globally waiting for: give a better development experience. But, there are still some lacks to achieve this goal. I’ve been a little bit naive at the beginning when Dmitry Jerov said in 2011, “One thing to note: since we’re a development tools company, we’re building first-class IDE support for Kotlin in parallel with the language itself.” I thought that I would have in the IDE at least the same experience as in Java. Nine years later, some IDEA’s interesting features are still not supported for Kotlin like Structural Search and replace and Language injection. When a developer comes from Java and uses these tools, he expects to find it working with Kotlin.
    gaetan
    mikehearn
    4 replies
    Copy to Clipboard
  • mikehearn

    mikehearn

    1 year ago
    Ah, I came here to +1 the IDE comments. Not so much about features, but I'd really like to see some recognition of IDE exceptions as being a problem that could use tackling. It is something I always expected to be temporary in the early days but here we are in Kotlin 1.4 and I get IDE exceptions ~every day when on stable versions, and every few minutes when on EAP versions of either Kotlin or the IDE. Many of them are quite repetitive, but they do change over time as well, so this feels like a general issue where the IDE plugin has structural complexity issues that make it too hard to avoid bugs. I must have reported many hundreds of exceptions over the past years, perhaps over a thousand, but it's hard to notice any difference in plugin robustness.
    mikehearn
    a
    +1
    6 replies
    Copy to Clipboard
  • Kris Wong

    Kris Wong

    1 year ago
    I am surprised that I don't see a mention of the K/N memory model on the roadmap
    Kris Wong
    bezrukov
    3 replies
    Copy to Clipboard
  • mikehearn

    mikehearn

    1 year ago
    I'd like to know when the currently experimental features will be promoted to stable. It feels like this should be a relatively soon thing by the nature of 'experimental', yet there's no mention of this on the roadmap.
    mikehearn
    Nick
    +1
    9 replies
    Copy to Clipboard
  • mikehearn

    mikehearn

    1 year ago
    See: gRPC, Guava, etc. The problem is for the API designer it feels "free" to keep something experimental, because taking the label off probably doesn't increase usage much yet requires commitment and finality. So people launch beta APIs and then forget about them, and move onto the next thing.
    mikehearn
    1 replies
    Copy to Clipboard
  • mikehearn

    mikehearn

    1 year ago
    Like, isn't it enough to add
    @OptIn
    ? I also need a compiler flag, to opt in to the opting in? Isn't this a bit too Inception?
    mikehearn
    Kris Wong
    2 replies
    Copy to Clipboard