April 2011
Programming in Scala, First Edition
by jpcaruana & 1 other (via)la 1ère édition gratos online ! coool
October 2010
February 2010
November 2009
August 2009
scala-migrations - Project Hosting on Google Code
by jpcaruana (via)Scala Migrations is a library to manage upgrades and rollbacks to database schemas. Migrations allow a source control system to manage together the database schema and the code using the schema. It is designed to allow multiple developers working on a project with a database backend to design schema modifications independently, apply the migrations to their local database for debugging and when complete, check them into a source control system to manage as one manages normal source code. Other developers then check out the new migrations and apply them to their local database. Finally, the migrations are used to migrate the production databases to the latest schema version.
The Scala Migrations library is written in Scala and makes use of the clean Scala language to write easy to understand migrations, which are also written in Scala. Scala Migrations provides a database abstraction layer that allows migrations to target any supported database vendor.
July 2009
osmos - Google Code
by jpcaruana (via)Osmos provides on-disk ordered key-value tables for Erlang, based on a sort-merge machine with user-defined merging semantics. This allows a very high volume of updates to be handled efficiently while still supporting a variety of useful operations with transactional safety, e.g., adding to a counter, taking the union of sets, or simply replacing a record.
Osmos is ideal for situations where updates are much more frequent than queries, for example, collecting statistics for reporting, and periodically generating reports.
June 2009
Erik Engbrecht's Blog: Pondering Actor Design Trades
by jpcaruana (via)# Why is the standard Scala actor implementation so complex when others have done it in a such simpler fashion?
# Is it better to have one, big actor library that supports a wide variety of use cases, or a bunch of smaller ones targeted at specific niches and programming styles?
# If there are to be a bunch, should they just be conceptually similar (e.g. all based on the actor model), or should there be interoperability among them?
scalacheck - Google Code
by jpcaruanaScalaCheck is a powerful tool for automatic unit testing of Scala and Java programs. It features automatic test case generation and minimization of failing test cases. ScalaCheck started out as a Scala port of the Haskell library QuickCheck, and has since evolved and been extended with features not found in Haskell QuickCheck.
The Pragmatic Bookshelf | Programming Scala
by jpcaruana (via)Scala is an exciting, modern, multi-paradigm language for the JVM. You can use it to write traditional, imperative, object-oriented code. But you can also leverage its higher level of abstraction to take full advantage of modern, multicore systems. Programming Scala will show you how to use this powerful functional programming language to create highly scalable, highly concurrent applications on the Java Platform.
Java to Scala with the Help of Experts | The Scala Programming Language
by jpcaruanaJava to Scala with the Help of Experts
The Scala Programming Language
by jpcaruana & 3 othersScala is a general purpose programming language designed to express common programming patterns in a concise, elegant, and type-safe way. It smoothly integrates features of object-oriented and functional languages, enabling Java and other programmers to be more productive. Code sizes are typically reduced by a factor of two to three when compared to an equivalent Java application
flatula - Google Code
by jpcaruanaflatula is a simple "write-once" database for Erlang that provides an easy way to remember a piece of data, then look it up later using a compact identifier. See FlatulaHowTo for a brief introduction and tutorial.
mochiweb - Google Code
by jpcaruana & 1 other (via)MochiWeb is an Erlang library for building lightweight HTTP servers.