Python and Ruby, each with roots going back into the 1990s, are two of the most popular interpreted programming languages today. Ruby is most widely known as the language in which the ubiquitous Ruby on Rails web application framework is written, but it also has legions of fans that use it for things that have nothing to do with the web. Python is a big hit in the numerical and scientific computing communities at the present time, rapidly displacing such longtime stalwarts as R when it comes to these applications. It too, however, is also put to a myriad of other uses, and the two languages probably vie for the title when it comes to how flexible their users find them.

A Matter of Personality...

That isn't to say that there aren't some major, immediately noticeable, differences between the two programming tongues. Ruby is famous for its flexibility and eagerness to please; it is seen by many as a cleaned-up continuation of Perl's "Do What I Mean" philosophy, whereby the interpreter does its best to figure out the meaning of evening non-canonical syntactic constructs. In fact, the language's creator, Yukihiro Matsumoto, chose his brainchild's name in homage to that earlier language's gemstone-inspired moniker.

Python, on the other hand, takes a very different tact. In a famous Python Enhancement Proposal called "The Zen of Python," longtime Pythonista Tim Peters declared it to be preferable that there should only be a single obvious way to do anything. Python enthusiasts and programmers, then, generally prize unanimity of style over syntactic flexibility compared to those who choose Ruby, and this shows in the code they create. Even Python's whitespace-sensitive parsing has a feel of lending clarity through syntactical enforcement that is very much at odds with the much fuzzier style of typical Ruby code.

For example, Python's much-admired list comprehension feature serves as the most obvious way to build up certain kinds of lists according to initial conditions:

a = [x**3 for x in range(10,20)]
b = [y for y in a if y % 2 == 0]

first builds up a list of the cubes of all of the numbers between 10 and 19 (yes, 19), assigning the result to 'a'. A second list of those elements in 'a' which are even is then stored in 'b'. One natural way to do this in Ruby is probably:

a = (10..19).map {|x| x ** 3}
b = a.select {|y| y.even?}

but there are a number of obvious alternatives, such as:

a = (10..19).collect do |x|
x ** 3
end

b = a.find_all do |y|
y % 2 == 0
end

It tends to be a little easier to come up with equally viable, but syntactically distinct, solutions in Ruby compared to Python, even for relatively simple tasks like the above. That is not to say that Ruby is a messy language, either; it is merely that it is somewhat freer and more forgiving than Python is, and many consider Python's relative purity in this regard a real advantage when it comes to writing clear, easily understandable code.

And Somewhat One of Performance

I suspect that many of you are familiar with the term "hard coding a value" whereby the age of an individual or their location is written into the condition (or action) of a business rule (in this case) as shown below:

if customer.age > 21 and customer.city == 'denver'

then ...

Such coding practices are perfectly expectable provided that the conditional values, age and city, never change. They become entirely unacceptable if a need for different values could be anticipated. A classic example of where this practice occurred that caused considerable heartache in the IT industry was the Y2K issue where dates were updated using only the last 2 digits of a four digit number because the first 2 digits were hard-coded to 19 i.e. 1998, 1999. All was well provided that the date did not advance to a time beyond the 1900’s since no one could be certain of what would happen when the millennia arrived (2000). A considerably amount of work (albeit boring) and money, approximately $200 billion, went into revising systems by way of software rewrites and computer chip replacements in order to thwart any detrimental outcomes. It is obvious how a simple change or an assumption can have sweeping consequences.

You may wonder what Y2K has to do with Business Rule Management Systems (BRMS). Well, what if we considered rules themselves to be hard-coded. If we were to write 100s of rules in Java, .NET or whatever language that only worked for a given scenario or assumption, would that not constitute hard-coded logic? By hard-coded, we obviously mean compiled. For example, if a credit card company has a variety of bonus campaigns, each with their own unique list of rules that may change within a week’s time, what would be the most effective way of writing software to deal with these responsibilities?

Data has always been important to business. While it wasn't long ago that businesses kept minimal information on people who bought their products, nowadays companies keep vast amounts of data. In the late 20th century, marketers began to take demographics seriously. It was hard to keep track of so much information without the help of computers.

Only large companies in the '60s and '70s could afford the research necessary to deliver real marketing insight. The marketers of yesteryear relied upon focus groups and expensive experiments to gauge consumer behavior in a controlled environment. Today even the smallest of companies can have access to a rich array of real-world data about their consumers' behavior and their consumers. The amount of data that is stored today dwarfs the data of only a few years ago by several orders of magnitude.

So what kind of information are businesses storing for marketing purposes? Some examples include:

- Demographic information — age, gender, ethnicity, education, occupation and various other individual characteristics.

HP is taking legal action against Oracle for allegedly breaching its 2010 partnership agreement of porting HP’s core software products with the latest versions of Itanium. In March, Oracle announced it would not be developing any new versions for products designed for the Itanium processor. Itanium has the ability to power the so-called Business Critical Systems hardware for extremely demanding enterprise applications. However, Oracle said the chip line is about to die.

The companies’ lawyer met in the Santa Clara County Superior Court with Judge James Kleinberg presiding to discuss their side of the event. Others in the courtroom included Ann Livermore, HP board member and former enterprise business chief, and Oracle’s co-President Safra Catz. Catz and Livermore were the two key negotiators for the agreement. Livermore was to testify later in the day. Kleinberg is set to rule if the companies had a legally binding contract.

Jeff Thomas, HP’s lawyer, focused on the so-called Hurd Agreement wording, where the companies reiterated their partnership after Oracle hired Mark Hurd, former CEO for HP. HP also sued Hurd for breaking the confidentiality agreement.

Thomas and the lead lawyer for Oracle focused on one paragraph of the agreement, which read Oracle would continue to provide its product suite on the HP platform in a way that’s consistent with the existing partnership before Hurd’s hiring.