News for hackers. Stuff that matters.
Re:Stackable Traits Pattern in Scala by brandonmenc on Monday February 15, 2016 @12:00PM (#11104375)
> The example is based on characters of Game of Thrones, to make understanding concepts less boring.

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.

Re:Stackable Traits Pattern in Scala by saheb37 on Tuesday February 16, 2016 @01:02AM (#11108171)
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.
Re:Stackable Traits Pattern in Scala by saheb37 on Tuesday February 16, 2016 @07:32AM (#11109397)
Thanks, got your point, will keep it more simple and generic next time :)
Re:Stackable Traits Pattern in Scala by krschultz on Monday February 15, 2016 @12:04PM (#11104408)
Agreed. Disappointing because I think it's well written beyond that.
Re:Stackable Traits Pattern in Scala by saheb37 on Tuesday February 16, 2016 @01:07AM (#11108181)
Will try to improve in my next post :)