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.

Passbook is one of the newest features of the iPhone. What many people were offput by standards today is that we rely too much on disposable tickets, and the like, such as when you go to the airport for a boarding pass, or a movie ticket. Apple strove to solve that with a new application that is bundled with the newest update: Passbook.

Passbook offers everything you need, especially when a ticket, coupon, or gift card is needed. When you first open the application you are greeted by a sampling of applications that support Passbook, and its features. To begin, install the particular application you want to use. For example, we will be going with the Starbucks application to satiate our coffee needs every morning, as we have a gift card to spend.

Open up the freshly downloaded application, and get ready to be blown away. Like most applications, especially when it has to do with airlines, or coffee, you are almost always required to sign up for a respective account. Don’t worry, it is easy. All you will be asked is to fill out your email, a password, and other miscellaneous information to identify you when you lose your password or others.

Once you have finished signing up, you’re ready to roll. It will prompt you to enter a gift card that you already own, or begin a digital gift card. If you don’t have a gift card, you can start a digital gift card (or, as many may call it: a prepaid card), and pay for your coffee in a fast, and efficient way. Just tap on “Tap to Pay” when you are ready to pay, and tap again after you have paid. It’s really that easy.

It is said that spoken languages shape thoughts by their inclusion and exclusion of concepts, and by structuring them in different ways. Similarly, programming languages shape solutions by making some tasks easier and others less aesthetic. Using F# instead of C# reshapes software projects in ways that prefer certain development styles and outcomes, changing what is possible and how it is achieved.

F# is a functional language from Microsoft's research division. While once relegated to the land of impractical academia, the principles espoused by functional programming are beginning to garner mainstream appeal.

As its name implies, functions are first-class citizens in functional programming. Blocks of code can be stored in variables, passed to other functions, and infinitely composed into higher-order functions, encouraging cleaner abstractions and easier testing. While it has long been possible to store and pass code, F#'s clean syntax for higher-order functions encourages them as a solution to any problem seeking an abstraction.

F# also encourages immutability. Instead of maintaining state in variables, functional programming with F# models programs as a series of functions converting inputs to outputs. While this introduces complications for those used to imperative styles, the benefits of immutability mesh well with many current developments best practices.

For instance, if functions are pure, handling only immutable data and exhibiting no side effects, then testing is vastly simplified. It is very easy to test that a specific block of code always returns the same value given the same inputs, and by modeling code as a series of immutable functions, it becomes possible to gain a deep and highly precise set of guarantees that software will behave exactly as written.

Further, if execution flow is exclusively a matter of routing function inputs to outputs, then concurrency is vastly simplified. By shifting away from mutable state to immutable functions, the need for locks and semaphores is vastly reduced if not entirely eliminated, and multi-processor development is almost effortless in many cases.

Type inference is another powerful feature of many functional languages. It is often unnecessary to specify argument and return types, since any modern compiler can infer them automatically. F# brings this feature to most areas of the language, making F# feel less like a statically-typed language and more like Ruby or Python. F# also eliminates noise like braces, explicit returns, and other bits of ceremony that make languages feel cumbersome.

Functional programming with F# makes it possible to write concise, easily testable code that is simpler to parallelize and reason about. However, strict functional styles often require imperative developers to learn new ways of thinking that are not as intuitive. Fortunately, F# makes it possible to incrementally change habits over time. Thanks to its hybrid object-oriented and functional nature, and its clean interoperability with the .net platform, F# developers can gradually shift to a more functional mindset while still using the algorithms and libraries with which they are most familiar.

Related F# Resources:

F# Programming Essentials Training

A business rule is the basic unit of rule processing in a Business Rule Management System (BRMS) and, as such, requires a fundamental understanding. Rules consist of a set of actions and a set of conditions whereby actions are the consequences of each condition statement being satisfied or true. With rare exception, conditions test the property values of objects taken from an object model which itself is gleaned from a Data Dictionary and UML diagrams. See my article on Data Dictionaries for a better understanding on this subject matter.

A simple rule takes the form:

if condition(s)

then actions.

An alternative form includes an else statement where alternate actions are executed in the event that the conditions in the if statement are not satisfied:

if condition(s)

then actions

else alternate_actions

It is not considered a best prectice to write rules via nested if-then-else statements as they tend to be difficult to understand, hard to maintain and even harder to extend as the depth of these statements increases; in other words, adding if statements within a then clause makes it especially hard to determine which if statement was executed when looking at a bucket of rules. Moreoever, how can we determine whether the if or the else statement was satisfied without having to read the rule itself. Rules such as these are often organized into simple rule statements and provided with a name so that when reviewing rule execution logs one can determine which rule fired and not worry about whether the if or else statement was satisfied. Another limitation of this type of rule processing is that it does not take full advantage of rule inferencing and may have a negative performance impact on the Rete engine execution. Take a class with HSG and find out why.

Rule Conditions