Stayed up until 4am reducing a Scalac crash, only to find it was the same bug I found last week. Different code, different project, same me.
-
-
-
Replying to @milessabin
@milessabin@propensive There are things I miss about Scala. scalac is not just not on the list, the list has a restraining order against it1 reply 1 retweet 0 likes -
Replying to @DRMacIver
.
@DRMacIver@milessabin If I were still doing just the things I was doing five years ago with Scala, Scalac would be 100% solid.1 reply 0 retweets 0 likes -
Replying to @propensive
@DRMacIver@milessabin But it seems like I've managed to keep apace with the bug horizon.1 reply 0 retweets 0 likes -
Replying to @propensive
@propensive@milessabin I think that's the natural state of any advanced usage of software. You keep pushing until it pushes back too hard.1 reply 0 retweets 2 likes -
Replying to @DRMacIver
@DRMacIver@milessabin Scalac is far from the worst part of the experience. Much bigger issue for me: dependencies and builds.3 replies 0 retweets 0 likes -
Replying to @propensive
@propensive@milessabin ...whileas now it's supposedly good enough that you feel compelled to actually use it and it's terrible.1 reply 0 retweets 0 likes
@DRMacIver @milessabin I'm still handrolling, and it's terrible, but at least it's terrible and I understand what's going on.
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.