Re:Interoperability: Swift’s Super Power
by fzeindl on Friday September 22, 2023 @09:57AM
(#37612132)
Which Java baggage do you mean?
Re:Interoperability: Swift’s Super Power
by jwells89 on Friday September 22, 2023 @10:12AM
(#37612324)
Package/build management is one, gradle drives me crazy sometimes. Haven’t used maven so can’t speak about it.
Re:Interoperability: Swift’s Super Power
by geodel on Friday September 22, 2023 @12:00PM
(#37613720)
Exactly right. It seems difficult for so many folks to understand Kotlin is not some independent language from scratch but another JVM language trying to avoid Java's supposedly shortcomings. And Kotlin/Native/Web doesn't matter because core language design is simply informed by Java and other JVM ecosystem languages' features and limitations.
I think Kotlin is newer/better horse cart to Java's old cart rather than automobile.
Further as others have mentioned Java's 6 month release cycle and ton of changes at language/VM/library layers will make it difficult for Kotlin to choose between complying to latest JVM or chart an independent path.
Re:Interoperability: Swift’s Super Power
by whoopsie on Friday September 22, 2023 @12:06PM
(#37613788)
So true. I feel sorry for my Android colleagues. There’s a reason our iOS team ships much faster and has a far lower crash rate.
Re:Interoperability: Swift’s Super Power
by fzeindl on Saturday September 23, 2023 @01:27AM
(#37620776)
This is correct but not because of Java. The android SDK is terrible because of many reasons.
Which is also the reason why kotlin is so popular there. Using extensions function and concise syntax you can build clutches around this terrible abomination of an SDK.
And while it’s syntactically similar to Swift, I find it to be overall less ergonomic in various ways.