There I'll be able to not only blog on Java, but on other things that might not
be of interest to all the Java geek
Back in the late 70's, I was working in England for International
Computers Limited on mainframes and programming in a high-level
assembly language (no, that's not a contradiction in terms) on a
financial programming language called PROSPER.
At this time I also started working with my first mentor, Arthur Richards.
Arthur was a very interesting person.
Here are a few comments and thoughts on various aspects of
doing a new release of an open source project. They might
not all apply to each project. They might all be obvious.
I'm just throwing them out there. Some of these are rules
that I've been applying to my open source projects for the
last 19 years.
Quite often an open source project is started because somebody
wanted some functionality that didn't already exist (or that
they weren't aware of). A small project is released and it
will either flourish or languish depending upon whether others
find it useful or not.
I've seen small one time hacks even become released products
from commercial companies.
I'm an avid book reader. Anything from fiction through to
Recently I've been trying to get various open source applications
running on Solaris on x86 machines. These were mostly GNOME
applications, but some of them were dependant upon underlying
libraries that come from the Linux world. I've been having some
trouble with some of these software distributions because the
author(s) have only ever been concerned with GNOME and Linux.