Path: csiph.com!newsfeed.hal-mli.net!feeder3.hal-mli.net!newsfeed.hal-mli.net!feeder1.hal-mli.net!weretis.net!feeder1.news.weretis.net!feeder4.news.weretis.net!usenet.ukfsn.org!not-for-mail From: Martin Gregorie Newsgroups: comp.lang.java.programmer Subject: Re: Java servlet on browsers: dying or kicking ? Date: Tue, 1 Jan 2013 01:46:17 +0000 (UTC) Organization: UK Free Software Network Lines: 40 Message-ID: References: <50d892e5$0$282$14726298@news.sunsite.dk> <50dbf6d1$0$80176$742ec2ed@news.sonic.net> <50dcfecc$0$292$14726298@news.sunsite.dk> <50dd5b51$0$80184$742ec2ed@news.sonic.net> <50de2260$0$293$14726298@news.sunsite.dk> <50df9c4b$0$284$14726298@news.sunsite.dk> <50e22df7$0$293$14726298@news.sunsite.dk> NNTP-Posting-Host: 84.45.235.129 Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-Trace: localhost.localdomain 1357004777 4511 84.45.235.129 (1 Jan 2013 01:46:17 GMT) X-Complaints-To: usenet@localhost.localdomain NNTP-Posting-Date: Tue, 1 Jan 2013 01:46:17 +0000 (UTC) User-Agent: Pan/0.139 (Sexual Chocolate; GIT bf56508 git://git.gnome.org/pan2) Xref: csiph.com comp.lang.java.programmer:20842 On Mon, 31 Dec 2012 19:29:41 -0500, Arne Vajhøj wrote: > > The biggest drawback is the vendor lock-in (unless it is an open source > database, which the SP based solutions rarely are - it is almost always > Oracle/Microsoft/Sybase). > I was following, and agreeing with you, until this point. However now I don't understand why you make the OSS vs proprietary distinction. IMO moving a schema and data between PostgreSQL and MySQL would be no easier than moving between Oracle and Sybase. I don't see much inherent difference in stability within a DBMS either: granted that PostgreSQL specs change relatively little between versions, but the underlying low- level structure changes are often big enough to require the DB to be unloaded from the old version and reloaded into the new one. How is this different from, say, Oracle upgrades? Worse, some OSS stuff has insufficient attention paid to feature migration across versions. Leaving aside my bete noir (the egregious 'who cares what the user wants: this is what WE want' attitude shown by the Gnome team), I've bitten twice by the failure of PostgreSQL's pgdumpall utility to prevent confusion between valid data and string delimiters (delimiter characters, which are chosen by pgdumpall, appearing in data and not being recoded as hex to prevent confusion). I bugged it once, got it fixed, and then bugger me, it reappeared two versions later. I expect bugs of this type to get added to regression tests and hence to never reappear. If I can do this, so can any OSS project. The nub of the problem is that, at least with commercial code you generally get notice taken and the bug fixed or documented as a feature but sadly, there are OSS projects out there that just blow you off if their ideas have changed and/or they can't be arsed to do proper regression testing (WINE, I'm looking at you!). -- martin@ | Martin Gregorie gregorie. | Essex, UK org |