3 ms·
There are languages for teams, and than there are languages for individuals. Kotlin is a great language for individual productivity, but _can_ be terrible for
by jatins 8y ago
There are languages for teams, and than there are languages for individuals.
Kotlin is a great language for individual productivity, but _can_ be terrible for teams.
You can do the same thing in Kotlin in so many different ways that it makes hard to read other's code, and a lot of time gets wasted in code reviews over preferences.
Compared to that, limiting languages like Go are great for teams since well there's only one (or max, two) ways you can iterate a collection, as compared to what, like, seven ways in Kotlin.
- ralphc 8y agoProblem is, in most companies "languages for teams" means "languages for the JVM". What is the Go-like team language for the JVM?
- insertnickname 8y agoJava
- jatins 8y agoI agree with you when you say in most companies "languages for teams" means "languages for the JVM" But I am curious, is that just out of familiarity or are there things that JVM ecosystem has that are just not there elsewhere? I understand that some of the distributed data processing ecosystem (Kafka et al) are _built_ on JVM but there's nothing inherently stopping people from using these things from other languages.