The London Stock Exchange moves to Novell Linux

The London Stock Exchange moves to Novell Linux
September 8th 2008 was one of the worst days ever for the London Stock Exchange (LSE), and high-end Windows server-based applications. That was the day that the LSE came to a crashing stop. What happened? While the LSE has never come clean on the whole story, my sources told me that the LSE’s Windows-based .NET TradElec stock exchange had crashed. What we do know is that the CEO who had brought Windows and TradElec in was fired, TradElec was dumped, and a Novell SUSE Linux-based platform was brought in to replace it.

A Language Independent Approach for Detecting Duplicated Code

A Language Independent Approach for Detecting Duplicated Code
Abstract Code duplication is one of the factors that severely complicates the maintenance and evolution of large software systems. Techniques for detecting duplicated code exist but rely mostly on parsers, technology that has proven to be brittle in the face of different languages and dialects. In this paper we show that is possible to circumvent this hindrance by applying a language independent and visual approach, i.e. a tool that requires no parsing, yet is able to detect a signi´Čücant amount of code duplication. We validate our approach on a number of case studies, involving four different implementation languages and ranging from 256 K up to 13Mb of source code size. Keywords: Software maintenance, code duplication detection, code visualization

PMD – duplicate code finder

PMD – duplicate code finder
PMD scans Java source code and looks for potential problems like:

Possible bugs – empty try/catch/finally/switch statements

Dead code – unused local variables, parameters and private methods

Suboptimal code – wasteful String/StringBuffer usage

Overcomplicated expressions – unnecessary if statements, for loops that could be while loops

Duplicate code – copied/pasted code means copied/pasted bugs

Linux Filesystems LOC | Eric’s Blog

Linux Filesystems LOC | Eric’s Blog
The XFS filesystem has taken a beating for being a big, complicated, foreign filesystem since it’s introduction, and there is no doubt that there is a fair bit of code in there. But an interesting thing happened on the way to the Linux Kernel v3.0.0 – XFS developers have steadily reduced lines of code, while other up and coming filesystems such as Ext4 and BTRFS are steadily growing in LOC and complexity. And XFS has been under constant improvement at the same time as well.