0:00 / 0:00
- Recommended by 2 people: 2 in engineering communities.
- Presented by Martin Odersky, creator of Scala
- An opinion. It argues one side of a question engineers disagree on.
Intermediate. Assumes working knowledge.
13K views3 years ago2 recommendations
Programming languagesSoftware designScalaLanguage design and type systemsSimplicity and complexity
Martin Odersky discusses simplicity in Scala, addressing criticisms of complexity and proposing how the ecosystem can improve.
Scala lets us write beautifully simple code. It incurs very low boilerplate and does not restrict expression in arbitrary ways. Scala itself is also quite a simple language, with few constructs that compose well. On the other hand, Scala is often described as difficult. I believe this criticism is not so much directed at the language itself but at certain libraries, frameworks and applications written in Scala. In my talk I want to raise this problem, and start a discussion how the Scala ecosystem can do better.Why it's here
2 people recommend thisWhat people say. Recommended as an important keynote by Scala's creator on the direction of the language and ecosystem simplicity.
Moments people linked to
u/verydumbdevin r/Kotlin • Mentions
On “What is the most important reasons to prefer immutablility?”
If you have ever worked in some larger code bases that use a lot of mutability you will quickly realize that they are absolutely horrible to reason about. Immutability improves this quite a lot by demanding an explicit flow of data that we can derive from function signatures. Besides being easier to reason about it also protects us against a slew of bugs that can and probably will happen in mutable programs. The good news is that immutability is starting to become the norm in almost every programming language.
This does not mean that we should never use mutable data structures. It is sometimes more performant and more readable to use mutability to solve whatever problem it is we want to sol…