Stories by: Peter Wayner

It's been a big year for Apache Hadoop, the open source project that helps you split your workload among a rack of computers. The buzzword is now well known to your boss but still just a vague and hazy concept for your boss's boss. That puts it in the sweet spot when there's plenty of room for experimentation. The list of companies using Hadoop in production work grows longer each day, and it probably won't be long before "Hadoop cluster" takes over the role that the words "crazy supercomputer" used to play in thriller movies. The next version of the WOPR is bound to run Hadoop.

Was it the philosopher George Santayana who said, "Those who don't remember the past are condemned to repeat it?" Did he offer any hints for those of us who want to repeat the past, especially the successes? We're beyond the teary elegies of 2011 and deep into making resolutions for 2012. If we're going to stand half a chance of creating something great this year, it only makes sense to pause and celebrate what went right in 2011.

Depending on your perspective and proximity to the bleeding edge, the world of programming evolves either too fast or too slow. But whether you're banging out Cobol or hacking Node.js, one fact remains clear: Programmers must keep an eye on the latest programming trends to remain competitive in ever-shifting job markets.

Let's begin with the good news. Google's Dart is a modern, full-featured tool designed by grabbing the best features of Java, JavaScript, and C.

For the last few years, the world of NoSQL databases has been filled with exciting new projects, ambitious claims, and plenty of chest beating. The hypesters said the new NoSQL software packages offered tremendous performance gains by tossing away all of the structure and paranoid triple-checking that database creators had lovingly added over the years. Reliability? It's overrated, said the new programmers who didn't run serious business applications for Wall Street banks but trafficked in trivial, forgettable data about people's lives. Tabular structure? It's too hidebound and limiting. If we ignore these things, our databases will be free and insanely fast.

Scripting languages are the hot technology today for application and Web development -- no longer the backwater afterthought of the early days running in a pokey interpreter. Nor are scripting languages any longer merely the tool used for quick-and-dirty patching (someone once called Perl the duct tape of the Internet, and it stuck so well that Perl lovers wear the label proudly). No, today, scripting languages are popular for "real" programming work. In fact, entire systems and large-scale enterprise-grade projects are built from them.

At the movies, almost every thriller seems to include a moment when a character says, "That was easy ... a bit too easy." Then everything falls apart.

HTML5 heralds some nifty new features and the potential for sparking a Web programming paradigm shift, and as everyone who has read the tech press knows, there is nothing like HTML5 for fixing the Internet. Sprinkle some HTML5 into your code, and your websites will be faster and fancier -- it'll make your teeth white, too. But the reality of what HTML5 can do for those seeking native-app performance on the Web falls short of the hype.

If you are among the fading majority, you'll be reading this story in a cavernous desktop browser with screen real estate that goes on and on like the Montana sky. If you're from the future, you're pinching and sliding your fingers over a smartphone screen that seems tiny until you stick it in a belt holster and curse because it's not small enough to fit comfortably in your pocket. The mobile Web browser may not be as easy on the eyes, but hey, you might be reading it while swinging on a hammock over a beautiful beach while drinking fancy beverages.

Many cynical users assume Web browsers do little more than dutifully render HTML. The content is the most important part, they say, so it makes little difference which browser you use.