So I whipped up the following function:

String.prototype.tr = function(from, to) {  
    var fromChars = from.split("");  
    var toChars = to.split("");  

    var mapTable = {};  

    for(i = 0; i < fromChars.length; i++) {  
        var c = i < toChars.length ? toChars[i] : "";  
        mapTable[fromChars[i]] = c;  
    }  

    var str = this;  

    var re = new RegExp(fromChars.join("|"), "g");  
    str = str.replace(re, function(c) { 
        return mapTable[c]; 
    });  

    return str;  
};

Maybe not the fastest nor safest but it does the job =)

JavaScript++

function do_something(array) {
  for (var i in array) {
    print(i + " : " + array[i]);
  }
}

I think one of the biggest differences between these groups is in the tools they use and prefer.

The first group (i.e the eccentric programmer group) generally say "hey, let's use the best tool for the job" even if that means they have to learn a new language or technology. These people have often been very specialized in their favorite tools but can see the beauty in others and *borrow* that to their toolset.

The second group almost always never want to learn something new and, I think, doesn't consider themselves to be programmers but rather Java-programmers, C-programmers or Ruby-programmers (or any other random language). My experience is that they will not consider ideas and concepts from other tools and just stick with how they've done things in the past. These people are often also very fond of the concept of software design patterns.

From a customer point of view neither isn't the one true solution. Having a system built from a mix of technologies does impact future maintainability when it comes to hiring staff knowledgeable in the technologies while just sticking to one technology will often result in a inflexible solution that takes time to adapt to changes.

On this blog I will write about what, why and how we use the tools we prefer. Hopefully you'll be able to pick something up.

Happy hacking,
Claes