Due to a flood of comment spam I've had to turn off comments.

Paul Murphy has written a blog entry entitled Microsoft to buy Red Hat? Say it ain’t so. Ignoring the blatent speculation in that post, there are so many factual errors and obvious mistakes in the analysis that it appears he knows absolutly nothing about what he is talking about.

Consider this gem:

The biggest threat Red Hat faces right now is that IBM could settle with SCO and then release its own Linux along with workstations and servers based on the Cell processor.

Consider the way the SCO case is currently positioned. It looks like IBM will win, probably be awarded damages and SCO will probably be delisted and (I suspect) wound up as a company since their entire business model rest on winning that case. Why exactly would IBM consider settling the case now if they didn't earlier?

Then there is this:

With SuSe essentially out of the picture, Linspire in a world by itself, and Debian not getting the press it deserves, such a move by IBM would leave Red Hat with nowhere to go except a suicidal head-to-head competition with Microsoft in the x86 marketplace.Given that Cell outperforms x86 by an order of magnitude and doesn’t have the security weaknesses built into the x86, this would leave them fighting to hold an ever decreasing share of a shrinking market.

Geeze – Intel & AMD had better give up now! They have no hope against the magic of the Cell processor! Of course, there is the small problem of the Cell requiring entirely new programming techniques to get the best out of it – but I'm guessing Murphy didn't understand that.

Finally there is this bit of logic:

Getting acquired therefore makes sense as Red Hat’s Plan B -but Microsoft’s Plan B has traditionally been Plan A delayed a few years and I can see no reasonable business scenario under which the acquisition makes sense for them.

If I understand that bit of logic correctly, I think he's giving himself an excuse to use when Microsoft doesn't buy Red Hat. I think that might be the smartest bit of work he did in that piece…

I believe that a high quality open source Java implementation is important for many reasons, but there is one that overrides all others. I think that having a Java runtime deeply integrated into the Linux application stack both guarantees the future of Java on the desktop and is the only reasonable way for the Linux desktop environment to compete long term with Windows and Mac OS.

The alternative approach (Mono) is a nice technical platform. Politically it just doesn't make sense, though, because it ties Linux's future to that of its biggest competitor. Java, on the other hand is controlled by a company who is a long-term major contributor to open source projects and has committed both programmers to work on them and patent portfolios to help defend them. It is true that Sun could help by open sourcing its class libraries, but not doing that is a commerical mistake Sun has the right to make.

(Note that only neither IBM nor BEA nor any other Java vendor can solve the problem by open sourcing their JVMs, because they all sub-licence the class libaries from Sun and thus do not have the rights to open source them)

Anyway (as though I aren't already overcommitted with “projects on the side”): The Unofficial Apache Harmony Blog is something I plan to keep updated with regular status reports for those of you who don't want to deal with the mailing list traffic.

Searchscapes Manhattan is a pretty cool search visualisation that reminds me of Snowcrash.

It's Shockwave, but almost worth the installation just to play with it.

Apparently I'm a “local software developers who works with open-source solutions” (Also on Builder.au).

Seriously, though – it's good that the Australian government is trying to encourage open source, but that licence is pretty extreme. For example, this clause is what made me say I wouldn't touch it in any circumstances:

You must Notify Squiz.Net within 30 days of making any Modifications even if You do not intend to distribute those Modifications. Notify is defined in Clause 4.2 below. If Your Modifications are incomplete, You must still Notify Squiz of the status of your progress not less frequently than once every 30 days.

In theory I'd prefer to just pay than put up with having to deal with crap like that – although I suspect in practice I'd just use something else.

This blog will introduce you to Transactional NTFS, why we're so excited about this technology, and how you can use it in your own applications.

http://blogs.msdn.com/because_we_can/archive/2005/04/21/410628.aspx

It might not be WinFS, but a transactional filesystem would be pretty useful…

Google Search History is cool and all, but it requires to to be logged into google to use it. The problem with that is that it requires you to leave your GMail account logged in, too.

Sorry, Google, that's no good to me. Yahoo does it much better – it identifies you and your search history, but requires you to enter your password again when accessing Yahoo mail.

Argos Release 0.1

Announcing the inital release of Argos: A Search Engine API.

This 0.1 release should be regarded as an Alpha release. The API may change
during later releases and this release may contains bugs.

About Argos

Argos is an open source (Apache licenced) Java library for accessing the search
APIs provided by internet search engines. It provides a consistent, extensible
and easy to use API, while supporting advanced features such as a paged request
model and a simultaneous search across multiple engines.

Argos currently supports the following search engines:

• Blogdigger
• Del.icio.us
• Feedster
• Google
• Google Desktop Search
• MSN Search
• Technorati
• Yahoo

For more information and downloads please vist http://argos.dev.java.net/

Paul Graham is a good writer, but many of his essays annoy me because they assume his experience is the only valid way to program. That's why I loved it when Maciej Ceglowski (who can both paint and program) called him on his Hackers and Painters essay.

I am not qualified to call bullshit on Paul Graham when he writes about programming, history, starting a business, or even growing up as a social pariah, but I do know enough about art to see when someone is just making shit up.

From Dabblers and Blowhards

Looks like Tim Bray has discovered JXTA (or at least that what I'd put money on).

While he's looking at that perhaps he could explain why Sun have two very similar technologies (Jini & JXTA), both of which are hard to get started with and neither of which has seen the adoption they deserve.

Speaking of Java P2P packages that are hard to use – it's a pity that Bamboo-DHT has gone SO overboard in its use of JDK1.5 features, in particular static imports. “Gee look Mom – now I can simulate global functions. Yay!”. Plus, it requires make and Perl to build. Oh the humanity!