Scala Implicits - Not to be feared. Nice slide deck explaining what Scala Implicits are used for and why they make sense. Since Implicits are a feature that is often misunderstood outside the Scala community, it might be well worth taking a look.
scala
n8han/giter8. And another practical tool, not necessarily Scala-related, but very useful: templates stored on GitHub are used to set up project structures. There is also a template for Android projects that use Scala.
Getting started · jberkel/android-plugin Wiki. And here is the central element for Scala programming for Android. This provides various sbt commands that handle Android integration and delivery.
mpeltonen/sbt-idea. Hmm, interesting - an sbt plugin with which you can generate Idea project structures. With this, you can then use the IDE at the points where you want to use it on the same project. For example, for remote debug integration, the IDE is quite nice.
Android programming with Scala. A bit stilted language, but useful content. The article provides a nice overview of what you gain when using Scala for Android programming. I need to take a closer look at this myself, as typing in Java sometimes gets on my nerves. Additionally, a workflow with sbt and a normal editor sounds much leaner than the various Java IDE environments. And some Scala language features practically scream to be used in the Android environment (especially traits).
scalatra/scalatra. This is something like Sinatra, but not for Ruby but for Scala. It has direct support for Scalatest and also offers some nice features and DSLs to quickly and simply get to the result - could be interesting especially for creating web services in Scala.
scalaforandroid - Scala for Android. And for completeness, a project for creating Android applications with Scala. Scala does require a large runtime library of its own, but scalaforandroid uses a tree shaker (Proguard) that only transfers the used classes of the library during packaging, keeping the volume small.
Typesafe Stack is a distribution of Scala (2.9.0) and Akka (1.1, an actor framework for Scala with various tools for programming distributed solutions in Scala) for easy installation. Additionally, it points to sbt and Scala IDE for Eclipse (use the beta version 2, as this is completely new and the 1.x versions do not work with Scala 2.9.0 and are not particularly good) as supplements. Installers are available for Windows, OSX, and Linux (you can of course install them yourself on all platforms, but some people prefer normal installation paths). And if you want, you can buy support there - and the company belongs to Odersky, the Scala inventor and JVM languages guru. Actually, Odersky could also include his book on Scala programming as PDF (in the first edition, this is also free).
Mixing it up: when F# meets C#. As you never program in a closed room, the connections between languages are quite important - and especially on platforms like .NET and JVM. The mappings of F# data types to C# data types and the use of these look quite interesting. Using C# data from F# is trivial, but the other way around there are some peculiarities. A similar situation exists with Scala and Java.
Scala 2.9.0 RC3 | The Scala Programming Language. Hmm, especially the parallel collections sound interesting - so to speak map/reduce for multicore on local data structures.
Jess, the Rule Engine for the Java Platform. If you ever need a rules engine for Java, Jess is based on the core ideas of CLIPS, which has existed for quite some time now (around the mid-80s), but integrates into the Java world. An alternative would be Hamurabi, a rules engine written in Scala that features an integrated DSL with Scala language tools.
Akka Project. And I definitely had that on the old blog before, but never mind, everything is repeated on TV all the time. And a lot has happened with Akka lately, and it is increasingly establishing itself as the future platform for fault-tolerant systems on the JVM. Many parallels with Erlang's ideas, but with the broader JVM-typical platform (there is hardly anything for which there is not some Java class library and thus also for Scala). Very interesting: Akka brings an implementation of Software Transactional Memory for the Java platform.
Programming Scala. I think I already had this one, but never mind: the second online freely available book about Scala that I stumbled upon today. You can also read it alongside the other one, but it's at a similar language level (i.e., before 2.8).
ScalaQuery. Yes, Scala-Day today. One of the things I was missing so far was a good integration of databases that also makes use of the DSL features and type safety of Scala. So not just sending SQL around via JDBC, but something like LINQ, only for Scala. This looks quite nice.
Programming in Scala, First Edition. And since I have Scala on my mind: the first edition of Programming in Scala is now freely available on the web. Of course, it lacks some things that came with the current Scala version (especially the container libraries are indeed different in 2.8), but it is still certainly a good starting point to read into the language.
Scala IDE for Eclipse. Hmm, it seems that the tools are starting to develop there. I don't have anything against command lines in general and feel more at home on them than in IDEs, but for the general acceptance of languages, IDEs are quite practical. And Scala is still one of the more interesting languages in the JVM environment, even if it has become quite quiet about it in recent times.
hotzen/ScalaFlow provides a very interesting extension to Scala: dataflow programming with automatic resolution via continuations - you define variables, can access variable values before values are assigned to them and the system itself sorts all accesses and assignments into the correct order. Particularly interesting as a basis for parallelization, when partial areas only emerge later but corresponding processing should already be defined earlier. Dataflow languages have been of interest to me since Prograph. The integration into a normal language as a basis could be quite interesting.
A Type-Safe Database Query DSL for Scala. Sounds interesting, something between LINQ and ORM for Scala. I should check it out when I'm back from the cold.
Monads Are Not Metaphors - Code Commit. Definitely one of the better explanations of what a monad is that I have read.
Kojo Home - an environment similar to Processing with Scala as the scripting language. Very interesting because it runs on multiple platforms like Processing, delivers quick visual results but is not based on Java, but on a modern multi-paradigm language. In addition, it offers a small turtle right from the start, just like in Logo. Turtles are cool.
Squeryl - this looks very interesting, reminds strongly of LINQ (which is not necessarily bad, even if it comes from Microsoft). It definitely makes sense to use Scala's features to build an ORM that goes far beyond normal Java ORMs.
twitter's gizzard - could become interesting, a framework for distributing and replicating data across various backends. Gizzard deals exclusively with sharding and replication, the datastore itself is treated separately, making it interesting for various scenarios.
Scala: Post-Functional, Post-Modern, or Just Perl++? - interesting post that addresses some of the points that also bother me when looking at Scala. I particularly like the designation as Perl++, as that is exactly the impression that comes to me whenever I delve deeper into Scala. Perl has always fascinated me, but by the time I built larger projects with it and used the advanced features of Perl more intensively, I had some doubts about the maintainability of the result - especially with regard to handing over the work to one of my colleagues for further maintenance. At that time, I switched to Python because it offered me many of the features in a much cleaner language concept. I think this could also explain why I just can't warm up to Scala, even though many aspects of it fascinate me.
Squeryl — Introduction - I should also take a look at that, as I was not so enthusiastic about the previous persistence layers for Scala. And for initial experiments, I actually don't want to build a web application with Lift right away, but perhaps just rewrite a few tools that I have solved differently with Scala.
Scala 2.8.0 Beta 1 | The Scala Programming Language - Scala is also getting ready for the next release. The extensions and changes sound quite good - and the impact on existing sources seems to be low.
A Postfunctional Language - recently there have been more discussions about whether Scala is really a functional language. Here are the statements on this topic from the creator of Scala himself, Martin Odersky.
Introducing Akka - Simpler Scalability, Fault-Tolerance, Concurrency & Remoting through Actors - nice overview of a quite interesting project in Scala (I think I've already linked to it) that provides STM, distributed Actors and the Erlang Supervisor Model for Scala. I should definitely check it out.
ScalaCheck User Guide - an interesting approach to a unit testing tool. Based on the ideas of QuickCheck for Haskell. I particularly like the approach of declaring tests as properties and then generating random data (or controlled test data) and checking whether these properties actually fit. This works particularly well with purely functional code, as functions are much easier to test with random inputs due to the lack of side effects.
technically.us Git - sling.git/blob - project/build/AssemblyProject.scala - nice small custom task for sbt to create standalone jars.
Play framework - a rather interesting framework for Java in the style of Django or Rails. In the dev version 1.1, it also supports Scala for the view functions, which is quite interesting, because no matter how nice the framework is, I won't subject myself to raw Java.
alandipert's step - a Pico-Framework for website tinkering with Scala. Looks quite funny for simple REST web services in Scala.
Enterprise scala actors: introducing the Akka framework - sounds a bit like OTP (the server platform for Erlang) for Scala. Could be very interesting, let's see.
ScalaCL: Reap OpenCL’s benefits without learning its syntax (Scala DSL for transparently parallel computations) - and anyone who wants to play around with OpenCL will find what they're looking for here, without having to delve into the hardware depths.
Spde - and then there's also a combination of Scala and Processing. Also quite interesting to play around with.
Neat Graphics with Scala Processin - exactly what you need to play around with Scala, a Processing version in Scala instead of Java, but with the entire graphics API.
robey's kestrel at master - loosely ordered, reliable message queueing. In Scala. Sounds very interesting, could be useful for some projects, especially since it simply uses the memcache protocol for access, so many clients for various languages are already available. Scala and its ecosystem of projects is becoming increasingly interesting to me.
simple-build-tool - an interesting build tool for Scala that doesn't rely on XML orgies. I find Maven somehow terrifyingly monstrous - and quite honestly, editing XML files I consider an imposition.
Dev Thoughts: Scala: Program like you mean it. - interesting article about some of the nice features of Scala.
Dispatch → Guide - Library for accessing web services (RESTful) from Scala.
NetBeans 6.7 focuses on Maven and Kenai integration - in connection with the Scala support for Netbeans (unfortunately not yet for the current version) it could become more interesting than Eclipse for me in the long run.
scala.xml - how to mangle XML with Scala (quite interesting, Scala can directly embed XML in the source)
Lift Web Framework - for Scala. Inspired by ideas from Seaside, Rails, Django, and Erlyweb. Sounds at least good.
The Scala Programming Language - sounds interesting. Not that we urgently need another programming language, but this one has some interesting approaches and the really smooth integration into Java and .NET worlds has a real advantage: the availability of many libraries. However, whether the functional character of Scala will survive when combined with various Java classes?