Entrevistamos a Jaime González
summary
Asserts that Kotlin works well for pragmatic applications but does not replace primarily functional languages because some patterns require explicit encoding such as type classes implemented via libraries and manual encoding of higher-kinded patterns, describes having implemented a small production process using those techniques and finding tradeoffs in verbosity and performance, judges Arrow as a promising ecosystem component that remains a separate library and is unlikely to be folded into Kotlin core soon.
AI-written summary · about
related talks
29mKOTLIN FOR SCALA DEVELOPERS
43mKotlin: Boring Languages are dead Long Live Boring Languages
50mState of the functional ecosystem in Kotlin: Mid 2018 checkup
11mIs Kotlin right for you?
31mA Kotlin Journey
39mKotlin for the Pragmatic Functionalist
50mPure Kotlin.
27mWhy Kotlin is my favourite example of Functional Programming?
