3 ms·
> a better Java: compatible with most patterns, tools, even libraries, but addressing some of his pet frustrations. But is this a main pitch of Kotlin?..
by riku_iki 8y ago
> a better Java: compatible with most patterns, tools, even libraries, but addressing some of his pet frustrations.
But is this a main pitch of Kotlin?..
- pdpi 8y agoBeing compatible doesn't mean that compatibility is the path of least friction, especially when it clashes with good design. A good example of that tension is the final/open thing: Wonky frameworks abuse inheritance and force you to use open all over the place, but Effective Java suggests you should make every class/method final unless you specifically design it to be extended.