Should you use the Scala built-in enumerations, or roll your own? There are pros and cons.
You’ve heard that Java 8 now has the main prerequisite for functional programming: functions. But you’re too busy writing Scala code to dig into the details, so we’ve put together a crib sheet on what’s in Java 8 from a Scala developer perspective.
Notes from my presentation on implementing CRDTs for text editing. CRDTs are data structures designed to combine together when you have no control over order of changes, timing of changes, or the number of participants in the data structure.
There's a three part series over at programming.oreilly.com on why you might be interested in the Lift web framework.
Clues on how to resolve local DTDs using Scala.XML.
We've published a Lift module to allow you to talk to Amazon SNS, which is Amazon's pub/sub system. The module lets you register a function to receive messages from an SNS topic, and send messages to SNS.
Don't commit time and effort to a service you care about if it doesn't give you the ability to get your data out. A promise of an export feature isn't an export feature.
I've updated the Lift Google Analytics plugin to make it easier to match the changes in EU cookie law.
I've found the O'Reilly Cookbook series to be handy, so I've applied the pattern to the Lift web framework documentation.
ReminderThing (RIP) was a fun project to find anniversaries in your contacts and calendar and send you an email nudge a week before.
An external module is one way to share lumps of code with the Lift community. The word “external” indicates that these are distinct from the modules in the core Lift repository maintained by Lift comitters. But the pattern to create a module is the same, as Peter outlined on the Lift Wiki and in one or two posts on the Lift mailing list.
Anyone can create one, anywhere they like, and people do. So there’s nothing to talk about.