Despite the growing popularity of open source software, there's still the issue of how to make money with it. No easy task, warns Miguel de Icaza, Vice President of Novell, who also heads up the firm's open source Mono project.

"If your livelihood depends on the product that you're selling, until you can figure how you're going to make money on that thing, I say, keep it proprietary," de Icaza said.

The VP went on to say that it's "incredibly difficult" making an open source business. His remarks were in response to an audience member at the Microsoft PDC (Professional Developers Conference), who raised the question of making money via open source. The issue of making money by selling support also came up.

"You need to take those steps carefully in my opinion," de Icaza said. "And support, by the way, is a horrible business. I want to be writing code, and I want to be paid to write code."

The VP did note that if you're a young developer without a lot of obligations, like a family and tuition, then it's far easier to consider doing open source projects.

Does open-source software do more to hurt the industry or help? You might guess the latter: we certainly did. But as it turns out, open-source software can actually be the bane of smaller software developers. After all, what does one do when one's primary meal-ticket gets taken over by the open-source community? For most developers, that's a lights-out proposition. But is this a reflection of where software development is expected to head in the future? Will it be a free for all?

The current sea of web browsers is awash in promises, but what makes Firefox better then Internet Explorer? And is Google’s Chrome really any faster or better at rendering web pages then Safari? Neowin.net was looking to answer this very question when it authored an excellent roundup of browser rendering engines. The report helps to break down which browsers and applications make use of each of the four most prominent technologies: Trident (Microsoft), Gecko (Mozilla), Webkit (Apple/Google), and Presto(Opera). While both Trident and Presto are both closed source projects, Gecko and Webkit remain open source and are likely to be the basis of any future browsers entering the market. It is an excellent reference for users looking to switch browsers and is a reminder that we should pay attention more to the underlying engine being used then the name of the browser itself. Market share of the various engines is a very telling indicator of general compatibility on the web. It will also help you the next time a Mac head goes on rant over how much better Safari is than Chrome. You now have the tools you need to put him in his place.