| September 2002 | ||||||
| Sun | Mon | Tue | Wed | Thu | Fri | Sat |
| 1 | 2 | 3 | 4 | 5 | 6 | 7 |
| 8 | 9 | 10 | 11 | 12 | 13 | 14 |
| 15 | 16 | 17 | 18 | 19 | 20 | 21 |
| 22 | 23 | 24 | 25 | 26 | 27 | 28 |
| 29 | 30 | |||||
| Aug Oct | ||||||
This site is no longer maintained.
My current weblog.
Sunday, September 01, 2002I've had conflicting opinions about the merits of going open source for my liveTopics program. Before I make a final decision I want to really understand what I am doing either way and what I am, potentially, giving up.
Matt has been openly struggling with using the GPL for liveTopics, and how that decision will affect any future commercial efforts on his part.
I don't care for the GPL, mostly because it is horribly complex and non-intuitive. In the context of Radio/Frontier, it seems that the GPL did not envision complex interpreted environments and frameworks that stretch the concept of "linking" and inherently co-mingle code. Consider the following GPL FAQ entries, how they apply to a GPL'd tool in Radio, and how they might affect a non-GPL'd Radio tool accessing functionality exposed by a GPL'd tool:
A GPL'd Radio tool probably needs a slew of exceptions in order to be used in Radio and by non-GPL'd Radio tools. The LGPL might address this, but I find it equally difficult to understand.
