Hacker News Reader

Scala screwed up by having no filter. Implementing every idea someone with a PhD thought of from the entire history of programming seems like a good idea until you have to use the language. Everybody doing whatever they want because of the freedom and no guidelines didn't help. And build times killed it

Kotlin feels like it has a much better plan and it seems like so far it won't suffer the same death.

View on HN

I agree about no filter*, I disagree with your reasoning. Scala (2) as a language is quite simple. The complexity came from the incredible power of its building blocks (e.g. implicits and path-dependent types). The lack of filter, as I felt, was moreso on how different two Scala codebases could be. That was part of the point though -- a scalable language, which means changing to the needs of each team.

Which also means less transferable knowledge. That killed it for me. If you muscle through it you'll get there, sure, but in the meantime I found languages that have smaller surface, are just as (or more) productive, and you can be onboarded in a project in half an afternoon.

Reply on news.ycombinator.com