News for hackers. Stuff that matters.
Re:Scala Best Practices by tempodox on Friday October 31, 2014 @08:41AM (#8538405)
I'm not so sure what to think of Scala as a language, but I think the naming and formatting recommendations in this document have merit beyond a single language.

There are only two hard things in Computer Science: cache invalidation and naming things.

Truer words were seldom written. Just compare the naming culture in Common Lisp with that of OCaml, for example. Worlds of difference.

And don't even get me started on the “standard” way of formatting in C family languages...

Re:Scala Best Practices by nvader on Friday October 31, 2014 @09:00AM (#8538483)
There are only two hard things in Computer Science: cache invalidation and naming things and off-by-one errors.
Re:Scala Best Practices by rtpg on Friday October 31, 2014 @11:16AM (#8539155)
I've heard this a lot but is cache invalidation as hard of a problem as , say, distributed systems like bitcoin?
Re:Scala Best Practices by tempodox on Friday October 31, 2014 @12:10PM (#8539521)
I thought of a single process as the frame of reference. Once you enter distributed systems, complexity (and consequently hardness) can achieve arbitrary levels.