3 ms·
What about libraries? What if you have to start trying to understand what's going on in Slick? I had two friends who were pairing and were trying to figure out
by ebiester 13y ago
What about libraries? What if you have to start trying to understand what's going on in Slick? I had two friends who were pairing and were trying to figure out how to get something done. They are both strong java developers and both had scala experience. However, they started diving in and got lost in even understanding what was going on.
I believe it was Dijkstra that said (paraphrasing) source code is meant to communicate to humans first and only incidentally machines.
- atto 13y agoI've seen this, too, but Scala's complexity does become more manageable with time. Slick seems to make a trade-off for a very nice API, at the cost of complex underlying code — which you sometimes need to understand when you want to use Type mappers and such. There's several Scala libraries that are on the border of "too clever". One is Play's Iteratees: it's a really nice concept, they take a few days to wrap your mind around. Trying to get a Java programmer to understand them borders on a lost cause.