These things are in no order and I intend to grow the list out!

Eclipse for Google #AppEngine site-update is broken see http://code.google.com/appengine/docs/java/tools/eclipse.html

In less than 2 minutes Mike Repass was quick to follow up with a tweet to find out what the problem was! For those of you who don’t know, Mike Repass is the product manager on the Google App Engine project.

Now that’s what I call “Excellent Response Time!”.

Keep up the good work guys!

Update: The fix is to remove the ‘update-site’ per Mike’s request.

@rburton Update is coming soon, but I think correct links are also on this page: http://code.google.com/eclipse/docs/getting_started.html

The blog posting has a smell of BileBlog without the substance. As a person interested in this debate between Ruby and Scala, you should look at the facts and not the personal opinions being sold. Alex makes many claims about how Scala is a better fit for Twitter, which I personally agree with, but once again let’s ignore opinions and look at the facts.

Scala was designed with the mindset that Object-Oriented and Functional Programming paradigms both have a place in the world of Software Engineering. The combination of these two paradigms make Scala a ‘Scalable Language’. Let’s take a look at how Scala can scale up based upon the size of a project.

Scala can serve has a scripting language to solve rather simple tasks without a load of bloated code and unnecessary declaration of objects. This allows you to write quick scripts that clearly express the problem at hand without a load of noise. But as a project starts to grow, it’s important to be able to ‘scale up’ with Object-Oriented concepts. This is done though the creation of components with a statically typed language. I can’t stress the latter of the previous sentence for large code bases. It can be argued that with proper test cases and good developers, you don’t need a statically typed language, but the world isn’t perfect.

There are many things that Scala provides outside of the two points made in the above paragraph, like interoperability between Java, Actors (which yes, is found in Ruby, ErLang, etc.) and many more items which I won’t go into here. I believe these important things were never mentioned in Obie’s argument. Instead he made personal attacks on Alex’s virtual ‘star’ and doesn’t provide any reasonable arguments against using Scala.

For these reasons, I’m left to believe Obie’s post was done with intentions of going against the grain and draw attention for his own financial benefit. His company Hashrock and his books are heavily based on Rails, so naturally he feels the need to defend his source of income. Just because you’re objective for defending Ruby is financially motivated, it doesn’t mean Alex is doing the same.

- Richard Burton (rburton)

Richard L. Burton III