Alledged Code Copying in Apache Geronimo spurs JBoss response

JBoss has alleging that Apache Geromino has copied code from JBoss’ server read more.

I don’t think the open source movement needs this sort of problems. After many recent articles about the open source software being buggy, Linux not ready for the desktop, and now lawsuits within the ranks. This can only hurt the open source movement. It also helps Microsoft’s case about “closed source”. It’s hard to copy source that is not available.

Linux IDEs where?

I think one of the things that has made Windows more popular for corporate users than Linux is the availability of good development tools. I’d like to see an IDE to develop GNOME applications. If one exists please let me know.

Update:I guess there are some. Take a look at Anjuta

Fedora (Linux pet peeve)

As much as I like Linux, there are still some things I find annoying. The default GNOME menu is ugly and cluttered. I applaud the distribution coming with so many applications giving a user choice, but sometimes choice is a bad thing.

And why isn’t there a Terminal icon in the GNOME Panel?

Fedora Core 1 Review

The installation was fairly uneventful. This was a clean install to an 18.4GB SCSI drive. The drive previously had a Windows partition which I used Disk Druid to delete and repartition for LInux. This was probably the only snafu I hit because I kept getting an error, but it was just user error. After the third try I got the partitions straightened out.

The biggest mistake I made was placing GRUB on the master boot record (MBR) instead of on /dev/sdb1, since it wiped out my current install of AiRBoot and OS boot loaded that works great with OS/2.

First Reboot
Upon reboot I expected problems, just being pessimistic I guess, but the reboot went great. I was surprised by a wonderful graphical boot screen which is nice and simple. I love the show/hide detail button since I like to see what’s going on during booting especially the first time.

I ran into only one problem where smartd failed to start. I don’t much care since I have no idea what this is for 🙂 yet.

Welcome Screen
The to be expected Welcome Screen appeared and the user setup was flawless and simple. Nice touch.

Hardware detection
This impressed me the most since Fedora found all of my hardware, though I really don’t have anything that’s rare since my system used to run OS/2 Warp 4 which is extremely picky with hardware.

Printer horrors
Now I continue to struggle with the printer on Linux. I have a Canon S750 which is shared via Samba from another Linux (Red Hat 8). I installed the Turbo Print driver for it on that machine. So Windows prints just fine to the raw queue, but I don’t get all the nice feature on my Fedora install unless I purchase a driver for it. I found the S600 driver works, but it’s not the same. So if I were rating Fedora on printer drivers, I’d give it a 4 out of 10.

All in all. I found Fedora much more polished than Red Hat Linux 9. I’m going to try a Personal Desktop install on my other drive just to see how that installation goes. But I think I’ll leave Windows again and hang out with Fedora for a while.

Going interface heavy

Recently it was decided that we move towards an interface heavy design to allow more flexibility in our software. I believe interfaces have their place but do not agree that every class in a system should be an implementation of an interface. I find it more useful to use interfaces as the connectors between different parts of a software system to facilitate enhancements, but some portions are just fine being concrete classes or abstract classes.

For instance, if I am passing in a class to a method from one part of a system to another, an interface would be a much better parameter type. This way if I choose to create another implemenation of that interface it will work without changing the recipient method. I recently found this to be of value when I designed a method to take in an interface. When the requirements changed, I simply created a new implementation and passed it into the aforementioned method. It was a great feeling not to have to rework both sides of the code.

But making a system interface heavy doesn’t mean to make “everything an interface”. To me it means to rely on interfaces to loosely couple different of a system, but still use patterns, abstract, and concrete classes when needed. I’d like to hear others views on this, so feel free to comment.


It’s 6AM EST, I sit here holding Marco trying to give Liz some time to sleep. In about half-an-hour Adán will get up.