Skip to main content

Ruby, Java and rewriting everything

Here's ( a nice article on the pros and cons of Ruby as compared to Java development. While it seems to be a bit too biased for my taste it still gives a nice overview and I agree with the points the author has collected.

On the other hand I asked myself if the guy who wrote this really wants to rewrite a large Java-based system in Ruby. If so, that kind of venture reminds me of the efforts to rewrite office suites in Java back in 98 (remember Corel?). It's like "hey, I've got this shiny new tool, now let's re-implement everything". Well, when you've got a hammer everything looks like a nail.

I remember Sun's campaign for "100% pure Java" and really don't think we need need a new dogma "100% pure Ruby". I go for "100% the right tool for the job".


Popular posts from this blog

NoSQL talk at Developer Summit

Three days ago I had to chance to talk about NoSQL at the Internet Briefing's Developer Summit. On top of general ideas and concepts like the CAP theorem I chose to talk about Apache Jackrabbit, CouchDB and Cassandra. My slides are embedded below.
It was a really good event with interesting speakers and a knowledgeable audience. I was especially pleased that when I talked about CouchDB's HTTP API someone from the audience mentioned that Apache Sling does something very similar for Jackrabbit.
Special kudos to Christian Stocker of Liip for daring to do a live demo of the "real-time web" - he took a picture from his phone and had it pop up on Jabber and Twitter in about 5 secs.
Vlad Trifa has posted a good summary of the whole event (part 1, part 2) - he also gave a great presentation about the application of the REST architectural style to the "Web of Things".

No SqlView more presentations from mmarth.

NoSQL: A long-time relation(ship) comes to an end

(cross-posting from here)

OK, I admit it, declaring that "the RDBMS is dead" is a meme that has been going around the software industry for a while. Remember object-oriented data bases that were supposed to replace the relational ones? Well, guess who is still here. However, despite the RDBMS's amazing survival skills I would like to propose a related prediction:

I believe that the year 2009 will go down in history as the year when the "relational model default" ended. The term "relational model default" was coined by me to describe a peculiar thing that goes on in application development: start talking to your average application developer about some arbitrary business requirement and chances are that simultaneously he mentally constructs a relational model to fit those requirements.
That relational approach to modeling your problem may or may not be suitable. The real problem is that all too often this default does not get challenged. As a consequence,…