Older blog entries for methodMatthew (starting at number 1)

This entry is in reference to the recent GPL freedom or power post. It becomes apparent just how important choice of licensing is after browsing the internet searching for sites that accept free software posting. Most of these sites state clearly that they will accept only certain free software licenses. NOT ALL. This is extended by many developer's opinions as well. If you look closely you will notice that this is an environment for monopoly. Imagine that GPL did get the upper hand and became the only free license. In effect this would influence the whole environment shutting out many potential free software developer's who do not wish to publish under the GPL. There is another factor to observe in the free software sector. People who contribute to the free software. People are not clones. Not all people follow laws. In general people are unpredictable. This brings up an issue of even if you do publish it free under the GPL there is no guarantee it will stay that way. Now lets take a look at what two different licenses accomplish. The GPL and the BSD. The above taken into account the GPL affectively cuts off a large limb of the free software tree of developers. This effectively divides and conquers the free software community, or at least severely impedes it. What does the GPL offer in return? No copyright. This severs the developer from any claim over the software. THIS PREVENTS THE DEVELOPER WHO WISHES THE SOFTWARE TO BE FREE FROM STATING "I WANT THIS SOFTWARE TO BE FREE". The community says "Who are you?" because there is no copyright and thus the developer is not known. People might say "That is why you can use dual licensing." This brings me back to the issue of a GPL monopoly which would prevent dual licensing. Next we can look at the BSD. Generally speaking the BSD is the same as the GPL with one exception (One very big exception). FREEDOM. ALL free software developer's may take part in contributions to software under this license. This includes the die hard free software users who create nothing but free software and part time free software developers who write propriety software as well. Many stead fast GPL developers attempt to argue that free developers must be all or nothing. However that is not the case. Whether you like it or not there are talented developers who do not agree with the GPL. Most free software developers have a goal. That goal is to make free software a standard. Chopping off all not GPL developers would be cutting progress in half. Lets put this into perspective. People are people and software is software. You can not call a person "propriety person" you can only call the software he/she writes propriety. What I am getting at is that a person can write propriety software then write free software or the other way around or both at the same time. Free software is free to reject this is to run in place. Lets face it there are many developers out there who need a license that provides freedom and freedom is power. Everyone has their own opinion of what freedom and power is. I believe that the BSD is the perfect license for free software because it excludes no one. This does not mean that GPL developers aren't writing good free software and helping the free software community thrive. What I do not like is the segregation that SOME GPL users would like to inflict on the community by attempting to shut the door on non-GPL free software developers.

Recently I read the article about chewing up leaders
and spitting them out so to speak. I am not familiar
with these particular developers who have decided to
exit the community. However I find it distressing
that the dedication that they once held to the community
is forgotten in the blink of an eye. That out of the
way I will now brief the community with my current
situation and a few beliefs that have guided me.
I am twenty years old with 0 income attempting
to earn a name for myself in the software engineering
community. Those who would agree with me might say
I am a determined perfectionist(those who would not
would prefer to call me a stubborn mule).
My goal is to create mass production in society
through use of flexible easy to use GUI's providing
distributed environments to computer users ranging
from the personal to the corporation level.
In these efforts I hope to gain returns in any or
all of the following:
Wide Scale Recognition of my Skills
Research Contacts
Revenue for Continuation of Research(this can take many
  forms. Cost of living, or scholarship receival from
  an educational institution.)
Some of my requests may be critized, but the work
that developing requires is not easy especially
for someone with financial pressure such as mine.
If you have managed to stick with this entry to
this point even if you do not agree with all of
my proposals then I will divulge some of the features
that my completed OODBMS displays.

Written in java(used relative file names and took into account all platform dependant barriers although it is still untested on most platforms) Event Queue capable of processing events in the background. Also has the ability of turning on a cache which stores event instructions until the user desires to flush the queue and thus execute the events. Easy to navigate tree hierarchy used to navigate catalogs, templates, and tables contained in the database. Customizable templates allowing flexibility of columns, automatic image column, and partitioning of data contained within tables. Multiple table searches depending on data contained in columns. SQL mapping of add update delete(across the TCP). Copy and paste items from one table to another. Multiple tables initialized at the same time. Dynamic spreadsheets(Associations) with portions of the calculation equation comming from multiple tables(configuration is persistant). Store up to 20 static spreadsheets. Print tables, Associations, and automatic image displayer. Create HTML tables cloned from database tables(uses some javascript for displaying images). Partitioned or Full saving of tables. Create server sockets for receiving data into a certain table and client sockets for exporting data out of certain tables(TCP). Error logging.

Thankyou for your interest

New Advogato Features

New HTML Parser: The long-awaited libxml2 based HTML parser code is live. It needs further work but already handles most markup better than the original parser.

Keep up with the latest Advogato features by reading the Advogato status blog.

If you're a C programmer with some spare time, take a look at the mod_virgule project page and help us with one of the tasks on the ToDo list!