3 ms·
It’s worked out ok for scala (though i don’t think anyone cares about it for android). Obviously a lot of code that only works on the JVM, because a lot of peop
by dropofwill 5y ago
It’s worked out ok for scala (though i don’t think anyone cares about it for android). Obviously a lot of code that only works on the JVM, because a lot of people just don’t care about native/js. But most core libraries will have ‘shared’ pure scala code and then have the platform specific implementations in separate folders. This is all fairly standardized with sbt plugins to do all the heavy lifting.
From the app side you just don’t use classes that you can’t use?
It will be interesting to see how things like Valhalla and Loom will pan out.
- pjmlp 5y agoDid it? The main company behind Scala changed its name and now also offers Java consulting. Unless the project requires Spark, there is little reason to even care Scala exists. Then there is the version 3.0 where they started having brain damaged ideas like changing the whole syntax. Scala today is Kotlin in 10 years. One benefit of being old in this industry is having survived multiple fashion waves of guest languages on each platform, then watching how those guest languages fade while the platform languages adopt some of their features. Or even how whole platforms become irrelevant making it a complete moot point regarding whose languages are on the platform.