[HN Gopher] Strategic Scala Style: Principle of Least Power (2014)
___________________________________________________________________
Strategic Scala Style: Principle of Least Power (2014)
Author : brok3nmachine
Score : 24 points
Date : 2021-06-13 09:25 UTC (1 days ago)
(HTM) web link (www.lihaoyi.com)
(TXT) w3m dump (www.lihaoyi.com)
| dhconnelly wrote:
| Oh man, I read this article a few months back and it immediately
| resonated with me. I've never used Scala, but this advice has
| been applicable in every language, project, and team I've ever
| worked with, and I very much regret that I didn't already have
| this resource to cite in past code reviews.
|
| A lot of the worst tendencies that developers complain about in
| complex programming languages (i.e. all of them, they're all
| complex) could be addressed by this advice.
| MrBuddyCasino wrote:
| A developer that is concerned (and rightfully so) with the
| Principle Of Least Power choosing Scala as his weapon of choice,
| in 2014, meaning before they partially saw the errors of their
| ways in Scala 3: a theoretical possibility, sure, but not one I
| have ever seen in the wild.
| nikitaga wrote:
| This principle as presented is not universal, it's built on a
| set of assumptions that are true for Scala but not for other
| environments.
|
| For example, it assumes that refactoring is easy, making it
| easy to switch your initially simple solution to something more
| complex if / when the need arises. That is true in Scala thanks
| to a rich and safe type system, but in other languages it may
| not be as easy, and it's certainly not easy to replace a python
| app with a Scala app.
___________________________________________________________________
(page generated 2021-06-14 23:01 UTC)