Is your Scala object always a singleton?
There's only one instance, right? Well, here's some bad news...
Jacek Kunicki (@rucek)
|
Freer doesn’t come for free
I don’t regret the detour I took to understand and use the Eff monad in anger to structure applications but I really don’t think that the benefits outweigh the costs. Eric Torreborre (@etorreborre) |
|
Maintaining Binary Compatibility in Scala
Keeping our dependencies up to date is an important goal, but every once in a while a presumably simple version update turns into a nerve-wrecking odyssey. Ralf Gueldemeister (@rgueldem) |
|
Anatomy of functors and category theory
In this article, I’ll try to give you an intuition about what is a functor and what do they look like in Scala. Martin Menestret (@mmenestret) |
|
A little Scala 'sed' class
A few times during the past year I got tired of trying to remember the Unix/Linux sed syntax while needing to make edits to many files, so this weekend I wrote a little sed-like Scala class. Alvin Alexander (@alvinalexander) |
|
Don't Use Await.result!
Almost regularly I see Scala code where people program in a sequential, synchronous style and integrate an asynchronous I/O call by waiting for its completion with Await.result. But you really shouldn’t. Lutz Hühnken (@lutzhuehnken) |
|
Aecor - Purely functional event sourcing in Scala. Part 6
I hope this post demonstrated how much Aecor wins from using final tagless. It’s also a great reminder of how much power this pattern gives. Vladimir Pavkin (@vlpavkin) |