Re:Kotlin 1.0 Released: Pragmatic Language for JVM and Android
by lmm on Monday February 15, 2016 @09:06AM
(#11103436)
That's a very unconstructive post. Please be more specific about upsides and downsides rather than just saying "It has some clear downsides and it's not hard to figure them out".
[ Parent
| on HN ]
Re:Kotlin 1.0 Released: Pragmatic Language for JVM and Android
by merb on Monday February 15, 2016 @09:17AM
(#11103481)
sbt downsides:
- slow resolution (could be really really really slow)
- transitive dependencies could be a mess since it could actually will mostly give you a evicition but it's hard to actually resolve that.
- however if you have two plugins a evicition is not printed, so you will actually get a funny stack trace if you actually use a library that resolve something via reflections. (i.e. closure compiler)
- sbt is slow
- sbt has some wierd operators.
- has problem with dynamic ranged versions
- scoped settings are cool, but could be wierd to understand, especially for new people
- sbt-web which tries to use npm which it packages as webjars which actually is a total mess since you actually run into the great world of npm packaging and try to force it into a completly different format.
there are more, however these are the ones I often deal with