Happy Day! Novell prevails over SCO

SCO has been saying for years that they wanted to plead their case before a jury, and today the jury in the SCO versus Novell trial affirmed that SCO never acquired the UNIX copyrights from Novell.  This eliminates most of SCO’s lawsuit against IBM.  For more details I direct you to Groklaw, the best resource for the SCO lawsuits and other free and open source software legal news.

Why I do not trust Microsoft

This post is for those who have not programmed for very long and as a refresher for those who have.  Microsoft has made many product and technology announcements and commitments over the years.  For some, Microsoft is like any other company: sometimes things are harder to implement than expected.  But for others, it is amazing how fast things change when Microsoft realizes that consumers and developers will benefit more than they will.  Here is a list of the highlights (lowlights?) that I am most familiar with, in no particular order: Continue reading

What will I do with 48 cores?

AMD is holding a contest, looking for the best answer to “What Would You Do With 48 Cores?”  I must admit it: I prefer AMD CPUs.  I have been an AMD customer for years, starting with a 486 overdrive CPU based on an AMD DX5-133 CPU.  Friends could not believe I had a 486 and not a Pentium 75! For the last 10 years my home has been Intel free except for an old laptop.  My children all have AMD based PCs, and whenever family or friends ask me what type of home PC to buy I make sure to add “…and look for an AMD CPU because you will get more performance for your money. “  And I have been promoting Opteron CPUs for servers and workstations since that line came out.  I will be very proud to win this contest, and I can assure you that, if I do, you will get to read all about it right here, in full detail. Now, here is what I will do with 48 cores: Continue reading

Who is your audience, really?

Writing classes tell you that for writing to be most effective you must know who your audience is and write directly to them.  That is great advice, and much of the time it is easy to know who your audience is.  For example, if I am writing a programming article I can reasonably assume my audience is composed of programmers interested in the subject, and I can be fairly free with some technical jargon.  On the other hand, if I am writing user instructions for some software marketed to general PC users then I had better be VERY careful about using any technical terms, and if it is REALLY necessary I had better explain those terms within the text.

However, sometimes you just THINK you know who your audience is. Continue reading