I agree to your point, but was it that difficult to decode or follow till the end? You think A, B, C, D would have been better? Or something more logical names to everyone
Re:Stackable Traits Pattern in Scala
by brandonmenc on Tuesday February 16, 2016 @03:05AM
(#11108487)
No, it wasn't impossible to follow, but the extra layer of indirection made me jump back to the top a few times to make sure I had everything straight.
//Legacy
abstract class Lannister
//Father
trait Tywin extends Lannister
could have just been: abstract class Family
trait Father extends Family
Otherwise, I appreciate the article - it was informative.Thanks, got your point, will keep it more simple and generic next time :)
Agreed. Disappointing because I think it's well written beyond that.
For those of us who don't know anything about Game of Thrones, and can't pronounce Elvish names, the example in this article reads like:
Flarg → Twipptch → Glorp → Boop → Fwyxnth → AnyRef → Any
So instead of being less boring, I have to use a decoder ring to figure out what's going on here.