30 years of QNX: Celebrating a decade of Eclipse

Correct me if I'm wrong, but until Eclipse came along, the software industry didn't have a standard platform for developing applications in C and C++. This was certainly true in the embedded market, where almost every OS vendor offered their own proprietary development environment.

As a wise man once said, what a dumb approach. Vendors wasted time reinventing the wheel, when they could have focused on innovative tools that offered real value. Meanwhile, developers had to learn a new toolset every time they worked with a different OS. Doh!

Folks at QNX knew this situation had to change. Which explains why Dan Dodge, the company's CEO, became a founding steward of Eclipse.org, the consortium responsible for creating the Eclipse open-source tooling platform. It also explains why Sebastien Marineau, the company's VP of engineering, became the first project lead of CDT, the C and C++ development environment for Eclipse.

QNX's contribution didn't stop there. The company also donated a large amount of source code and developer time to the CDT project. As a result of these and other community efforts, Eclipse CDT subsequently became the C/C++ platform of choice for IBM, Ericsson, Texas Instruments, and other multi-billion dollar organizations.

Eclipse CDT also formed the basis of a major new QNX product, the QNX Momentics Tool Suite. More importantly, the platform gave QNX more freedom to innovate, particularly when it came to tools for debugging and optimizing multi-core systems. In fact, these multi-core tools garnered several awards, including:

• Eclipse community awards, best developer tool, 2007
• EDN China innovation award, 2007
• Embedded World embedded AWARD, 2006

Here, for example, is a screen capture of the system profiler for the QNX Momentics Suite. The profiler is displaying CPU activity for the 4 cores of a quad-core processor:



Eclipse is ten years old this month. If you're interested in its history, or in crashing an Eclipse birthday party, check out out the Eclipse website.
 

Linux is huge, scary, bloated: Torvalds

You've got to hand it to Linus Torvalds, he's never been afraid to speak his mind. Even when it comes to his own baby.

Speaking yesterday at LinuxCon, he stated that the Linux kernel has become "huge and scary" and that it isn't "the streamlined, hyper-efficient kernel I envisioned when I started writing Linux."

Asked whether a solution was in the works, he commented, "I'd love to say we have a plan."

You gotta admit, the guy is honest.

Predictably, his comments have ignited discussions on several forums, including Slashdot, CNET, and OSNews.

QNX 6.4.2 development has started. So what are you going to do about it?

QNX Software Systems has started development on version 6.4.2 of the QNX Neutrino RTOS and QNX Momentics Tool Suite. The planned feature set includes ARM Cortex A9 support, faster interrupt-to-thread latency on Power processors, and PPS.

But you know, folks, this isn't the old days, when you had to wait and see what the final product contained. You can now follow QNX product development in real time. In fact, you can participate in the development process. And you can start by visiting the 6.4.2 OS features wiki page.

Mother Nature’s Debugger

The Goldenrod crab spider is a nasty piece of goods. A master of camouflage, it can mimic the color of its surroundings, rendering itself invisible to prey. Basically, it catches bugs by means of obscurity.

Check out the accompanying photo, which I took in my front garden. It tells the whole story: a yellow flower, a yellow crab spider, and an unfortunate fly that couldn’t tell the difference.



Obscurity is good for the spider, but not so good for humans. In business and politics, for example, hidden practices often, if not always, lead to corruption. Transparency is usually the cure, which is why a global organization dedicated to fighting corrupt practices calls itself Transparency International.

Mind you, transparency isn’t just good for CEOs and politicians; it’s also good for software developers. Vendors who publish their source code and develop their software products out in the open benefit from having more eyes inspecting their code — and the more eyes you have, the easier it is to catch bugs. (Spiders figured this out long ago.) Customers, for their part, can study the code and learn how to make best use of it. They can also use it to improve their own debugging efforts — which means even fewer bugs.

Basically, transparency is good for both the vendor and the software user. And there’s nothing obscure about that.


Using more eyes to catch more bugs.
 

The Dragonflies of Eden

I don’t know about you, but dragonflies creep me out. They’re the hawks of the insect world: fast, voracious, and capable of catching their dinner on the fly — literally. In fact, long before birds showed up on this planet, giant dragonflies ruled the skies, with wingspans of two-and-a-half feet.

Imagine one of those suckers landing in your hair.

I found this dragonfly basking out in the open, just down the street from QNX headquarters. It’s much smaller than its Paleozoic ancestors, yet it performs a great service, by preying on mosquitos. Given that mosquitos in North America can spread West Nile virus, this is a good thing.



Moral: The thing that looks scary at first often turns out to be the best thing for you.

For example, at QNX Software Systems, we provided a closed source operating system for over 25 years. We could have taken the easy route and kept it closed. After all, why publish your source code or open up your development process when business is good? Better to play it safe, right?

We came to realize, however, that “opening the kimono” was nothing to fear. The more we thought about it, the more we understood that embracing a transparent and collaborative approach to software development was, in fact, healthy — both for QNX and for the people who use our technology. And the result was the hybrid software model.

As for me, I’m not ready to embrace dragonflies just yet. But I’m growing more open to the idea.

Tags: open source, QNX

The Ballad of Billy and Pat

In his poem, The Collected Works of Billy the Kid, Michael Ondaatje tells us that Billy the Kid was a bad man with some good in him, and that Pat Garrett, Billy’s nemesis, was a good man with some bad in him.

Like many people, you may equate proprietary software with Billy the Kid (bad, but not completely), and open-source software with Pat Garrett (good, but with drawbacks). Unless, of course, you’re one of the many people who think the exact opposite.

The point is, almost no one believes that either proprietary or open source is the solution for everything. Both approaches have their merits — and tradeoffs.

All fine and good, but choosing between the two can be difficult. In the proprietary corner, you can leverage your vendor’s professional support services and quality management process. In most cases, you also get better development tools. In the open corner, on the other hand, you get faster bug fixes, greater self-sufficiency, and the power to bend and shape the software to your purposes.

It’s no wonder, then, that software vendors like QNX are moving to a middle ground that gives developers benefits of both approaches. At QNX, we call our approach the “hybrid software model,” and I recommend that you read Lawrence Rosen’s whitepaper on the topic. Rosen is the former legal counsel to the Open Source Initiative (INI) and he does a great job of explaining what the hybrid software model is and isn’t.

Billy the Kid on a bad hair day, and Pat Garrett on a good one.

Tags: open source, QNX