Re: java serialization alternative
Endre Stølsvik <[email protected]> Fri, 4 Apr 2008 10:50:58 +0200
| Newsgroups | gmane.comp.windows.devel.java.advanced |
|---|---|
| Message-ID | <[email protected]> |
Ted Neward wrote: > Db4o. www.db4objects.com > > It's dual-licensed, a la MySQL (and others). Ah, you mean the "try before you buy" GPLing that's become so popular recently? The "everyone works for us for free!" approach to "Open Source" software? Using the GPL in this way is close to disgusting IMO. And I just can't envision that this is really what Stallman wants out of his GPL - although he does seem to want as much software as possible to be GPLed, at any "cost", so maybe he is happy with it..! MySQL really tricked their commercial user base by initially, and for a long time, having the client library as LGPL, and the server GPL. This seemed very genuine, and everybody thought they knew where they had MySQL, building up commercial products using them. But suddenly them swedes changed the client license to GPL-only, stating that they felt that people were taking advantage of them blah blah blah BS BS BS - now demanding a per-installation style fee for commercial licenses. This happened pretty much at the same time they got a new CEO. But one may wonder: they had, AFAIU, all the time made you sign over your code to them, so that they always _could_ do the commercial thing. Not as with Linux, where each coder still owns his own code, and hence it is impossible to actually commercialize the code base - it is pretty much guaranteed to forever stay in the fully open. It was a clever ploy of MySQL - getting lots of developers "scratching their itches" for them - and they got quite a nice cash-out (aka 1B$) from it just this other day! GPL should be used for end applications, operating systems and servers (the "runs on" don't infect). GPL+Classpath approach to Sun's JDK is fine enough. LGPL for libraries. When a piece of code that's supposed to be used to build something else, typically a library, is claiming to be Open Source, and the license is GPL, there's something fishy. Like "stay away - it's the plague!"-style fishy. .. or just use BSD/Apache, if you really want your software to be used. db4objects at least to seem slightly honest about it: "Download a free version of db4o under the GPL license and start your free evaluation now!" They pretty much state "Come try before you buy!".. What do others think about these issues? Endre. =================================== This list is hosted by DevelopMentor® http://www.develop.com View archives and manage your subscription(s) at http://discuss.develop.com