Slashdot Mirror


Why Oracle Can't Easily Kill PostgreSQL

ruphus13 writes "Claiming that 'PostgreSQL is a FOSS alternative to MySQL and hence Oracle should be allowed to pursue MySQL' is a specious argument, according to Monty Widenius. He fears that Oracle, or someone else, can easily squash PostgreSQL by just 'buying out' the top 20 developers. The Postgre community has fired back, calling that claim ridiculous. According to the article, 'PostgreSQL as a project is pretty healthy, and shows how vulnerable projects like MySQL are to the winds of change. PostgreSQL could die tomorrow, if a huge group of its contributors dropped out for one reason or another and the remainder of the community didn't take up the slack. But that's exceedingly unlikely. The existing model for PostgreSQL development ensures that no single entity can control it, it can't be purchased, and if someone decides to fork the project, the odds are that the remaining community would be strong enough to continue without a serious glitch.'"

279 comments

  1. Firebird by Carewolf · · Score: 1

    And if postgresql fails there is still firebird, and all the other open source database that kick ass but are less known than mysql and postgresql.

    1. Re:Firebird by gmack · · Score: 4, Informative

      You forgot SQLite. It's small and good enough for most of what MySQL gets used for: simple web forms, stat counters etc.

    2. Re:Firebird by davecb · · Score: 3, Insightful

      He's just pushing a straw-man argument, having unwisely made it for MySQL, and after embaressingly being caught twisting RMS's words (see groklaw, http://www.groklaw.net/article.php?story=20100108114314405).

      I fear he's strictly in this for himself and his friends, a certain well-know monopolist with a "Codeplex" Foundation...

      Bother! I wanted this to be over months ago, so I could get more consulting from Sun's (Now Oracle's) customers.

      --dave

      --
      davecb@spamcop.net
    3. Re:Firebird by Anonymous Coward · · Score: 1, Interesting

      Yep, I don't know why people forget about it.

      It has lots of features like pg and has a free license like pg but is better performing like MySQL and easier to embed than even MySQL. Firebird beats all the others.

    4. Re: Firebird by Anonymous Coward · · Score: 0

      Exactly. It's not like Facebook or Twitter or Wikipedia are using MySQL....

    5. Re:Firebird by Elektroschock · · Score: 1

      Monty is the next SCOop.

      Get the poor billionaire (who sold MySQL) his open source project back, as dual licensing because the GPL is crap. Sign here.

    6. Re:Firebird by hairyfeet · · Score: 0, Troll

      That is why I never understood this whole "ZOMG! MySQL is gonna fall to teh evils Oracle!!!" bullshit. Once of the nice things about FOSS is there are many ways to do the same job. Some of them are more user friendly, some more designed for power users, but it isn't like there is only one way to do things.

      And if /. is gonna run bullshit articles like this, could they PLEASE put a disclaimer at the top that says "WARNING: Monty used to own MySQL and now wants it back for free!" okay? Monty is a douchebag who sold his product for an assload o' cash and now wants to whine and demand his app back, while not giving back one dime he took for it.

      If Monty wants MySQL back so bad, give back the money! I'm sure as much as Sun is hurting Oracle will be more than happy to take back that assload o' cash and hand him MySQL. But all this "Waaah they won't give back MySQL!" bullshit needs to stop, or at least have a disclaimer for those that don't know who Monty really is. If he wanted control he shouldn't have accepted the $$$, but he did so he should STFU and don't let the door hit him on the way out. What a douche.

      --
      ACs don't waste your time replying, your posts are never seen by me.
    7. Re:Firebird by hairyfeet · · Score: 1

      How exactly is this a troll? How many outside of database geeks know that Monty Widenius owned MySQl, sold it, and now is crying poor me because he can't lock it up behind a BSD style license and resell it?

      Hell the guy has put up false claims to drive petition signings (Saying RMS was on his side when he's not) has spread more FUD than SCO, and has done everything possible to block the Oracle/Sun merger, most likely hoping that Sun will end up DOA and sold for scraps on the auction block so he can get MySQL back for cheap. Am I lying? Tell me I'm wrong!

      You can't because I'm not. Monty is a grade A douche who wants to sell his company and keep it too. And I don't care if he got 16Mil or 16Bil, it was still his company, he still sold it, and now wants to raise a stink after cashing in hoping to cash in AGAIN by having MySQL released under a BSD license (so he can lock it back up with his own proprietary version).

      So why anyone on /., which is usually against hypocrites and asshattery, and usually pro libertarian, be for Monty is beyond me. He had a choice, he sold out, and now wants to whine to mommy EU to give his toys back to him. Sorry Monty, but you cashed the check, so please don't let the door hit you on your way out.

      --
      ACs don't waste your time replying, your posts are never seen by me.
    8. Re:Firebird by shutdown+-p+now · · Score: 2, Informative

      I've last used Firebird about two years ago, so this may not be true anymore... but anyway. I've had two major problems with it.

      First is documentation. There's no single place to go for it. Effectively you end up with the original Interbase manual, and then various bits and pieces which explain what was added/removed/changed, and you have to piece it all together by yourself (and there's no way to tell if you even have all the pieces in the first place). This applies to admin docs, SQL reference, and language API references.

      Speaking of which, we come to the second point: API bindings are rather messy (the C one, at least). Much more so than SQLite API, for example. Among other things, I recall it requiring things like (char*) casts back and forth to reinterpret data of appropriate types, and it seems to make a lot of assumptions about sizes of various C types, so its portability to more exotic architectures would be rather suspect.

      It also doesn't seem to be nearly as feature-rich as PostgreSQL. The core is solid, but e.g. standard function set is rather minimalist, and you end up rolling out your own for many occasions.

      That said, Firebird/Embedded is a very nice database specifically for embedding, small and yet full-featured. If you ever missed things such as stored procedures in SQLite (and they actually make quite a lot of sense specifically for embedded DBs, where DB is tightly coupled to the application anyway), I would advise to look at FB/E.

    9. Re:Firebird by toby · · Score: 1

      API bindings are rather messy

      For C apps, libdbi supports Firebird, and many other RDBMS with a single API.

      --
      you had me at #!
    10. Re:Firebird by dave87656 · · Score: 1

      What about JavaDB (Derby)? It is supposed to have good performance. I understand most, but not all, standard features are implemented.

  2. Widenius please move on... by Bill_the_Engineer · · Score: 5, Insightful

    You got your money and now you want MySQL (or at least the spotlight) back.

    By your argument, PostgreSQL is fragile because the top 20 developers could be bought out by Oracle. If you think that's a buyout target that can be easily squashed, just think what a SQL DB with only one copyright owner can be? Oh wait, that was MySQL and we already know what you did....

    --
    These comments are my own and do not necessarily reflect the views or opinions of my employer or colleagues...
    1. Re:Widenius please move on... by mangu · · Score: 4, Informative

      PostgreSQL is fragile because the top 20 developers could be bought out by Oracle

      His argument is "I was bought, therefore anybody else can be bought".

      If Oracle is willing to buy 20 developers at $1 billion each, then he may be right.

    2. Re:Widenius please move on... by Anonymous Coward · · Score: 5, Insightful

      ...PostgreSQL is fragile because the top 20 developers could be bought out by Oracle...

      Sort of like how Monty's been trying to buy all the top MySQL devs away from Sun...

    3. Re:Widenius please move on... by TheRaven64 · · Score: 4, Interesting

      Well, it was $1bn for the company, not just $1bn for Monty. $1bn for Postgres would be $50m for the 20 developers. Still quite a lot. Of course, there is a big problem here. Because Postgres would still be BSD licensed, there's nothing stopping these developers from giving $1m of this to pay for someone else to work full time on the project...

      --
      I am TheRaven on Soylent News
    4. Re:Widenius please move on... by thetoadwarrior · · Score: 2, Interesting

      I agree, In my opinion the guy is a jackass. I'm half tempted to quit using MySQL myself purely because it originated from him.

    5. Re:Widenius please move on... by Migala77 · · Score: 2, Insightful

      His argument is "I was bought, therefore anybody else can be bought".

      If Oracle is willing to buy 20 developers at $1 billion each, then he may be right.

      That would only lead to 20 million developers starting to learn the PostgreSQL code base, hoping to get a billion dollars as well. Developers can be replaced (not easily, but they can be).

      Sun bought MySQL (and Oracle Sun) for the control, via the assigned copyright, of the sourcecode, and of the support structure. MySQL the company has always done everything it can to keep control over the MySQL product, making the GPL license just a part of a distribution model. A lot needs to be rebuild in organizing the development process, in building a support structure, etc, to make one of the forks a relevant choice commercially. It's not impossible, but the advantages MySQL the company had over competitors in this are what made it worth $1 billion. The developers are a part of this, but far from the whole picture.

    6. Re:Widenius please move on... by maxume · · Score: 1

      People using MySQL under the GPL are mostly O.k., they just have to figure out how they are going to patch bugs and such, and then they have time to decide if the ongoing development of the GPL version is going to work for them.

      People using it under a proprietary license are really worried that Oracle isn't going to play ball. I'm sure many of them are looking at alternatives, and comparing the costs of transitioning to the problems of ongoing uncertainty about the attitude of the owner of the codebase.

      --
      Nerd rage is the funniest rage.
    7. Re:Widenius please move on... by BigGerman · · Score: 1

      I think his statement is sort of Freudian admission that Oracle already did the same to MySQL (acting via Sun as proxy)

    8. Re:Widenius please move on... by Anonymous Coward · · Score: 0

      I stopped using MySQL years ago because of his attitude (continually putting off subselects, foreign keys, etc.)

    9. Re:Widenius please move on... by Anonymous Coward · · Score: 0

      And don't forget the crappy implementation of stored procedures. Sure is great to be able to find out that you've had an error somewhere in a proc, but don't have any way of finding out what the problem is.

    10. Re:Widenius please move on... by jadavis · · Score: 1

      By your argument, PostgreSQL is fragile because the top 20 developers could be bought out by Oracle.

      One thing about PostgreSQL is that the leadership have developed a lot of policies, standards, traditions, practices, style, tools, and other organized structures. In the recent past this has been much more conscious -- for instance the commit-fests are a great way for new developers to join in by submitting patches and reviewing others' patches.

      This makes it easier for newer developers and leaders to step up to the plate even without a long history in the project. Is this patch good enough? Well, has it been reviewed by two people (reviewer and committer) as required by the commitfest policy?

      Of course hiring developers away will slow down development. But it won't be a death blow, because new people can always get involved and they know what to do. They know what roles need to be filled, they know what constitutes a good patch, they know how to make a release, and they know the general principles to maintain high quality. They also know what to do when a random patch hits the list by an unknown developer, so they can make progress and rebuild the community.

      --
      Social scientists are inspired by theories; scientists are humbled by facts.
    11. Re:Widenius please move on... by unix_geek_512 · · Score: 2, Interesting

      Ladies and Gents please stop unfairly attacking Widenius, as TheRaven64 already mentioned, he absolutely positively did not get $1 billion for mysql he got about $16.6 million in 2008 which is nowhere near $1 billion. [ source wikipedia with 2 other sources providing confirmation ]

      The whole company was bought for $1 billion and a very small portion, reportedly about 12% or less of that went to Widenius and the other mysql founder.

      And keep in mind transactions like this are rarely done in cash and there are many strings attached to any stock they may have received in the deal.

      Because of this Widenius cannot buy mysql back from Sun or Oracle for $1 billion because he never got $1 billion and it is highly unlikely he could raise $1 billion to buy it back.

      It is obvious that the sale of mysql to Oracle would have major anti-trust implications no matter what side of the argument you're on.

      You may dislike Widenius and mysql and you're free to dislike them all you want but the fact is the entire community would be affected by the purchase if it goes through.

      Oracle could turn mysql into crippleware, they may go after all the users, they could kill it or do any number of things which would not be good for the community. Even if you forked mysql Oracle could shut you down any time since they already own all kinds of patents and the underlying engine.

      Like it or not, millions of websites and users depend on mysql one way or the other and migrating them all to prostgresql or any other DB would be a huge undertaking, especially if it's a forced migration.

      If the purchase goes through I would like to see mysql sold to an independent 3rd party or spun off so that Oracle does not end up with a virtual monopoly in that sector.

      A monopoly is not good for anyone.

      Note that I'm in no way advocating mysql should be given back to Widenius or anyone else, just that it become completely independent and receive a fair and reasonable license to use Oracle's engine and mutually cross-license the patents and other IP to resolve the justified anti-trust and monopoly concerns.

      That's pretty fair don't you think?

    12. Re:Widenius please move on... by Anonymous Coward · · Score: 0

      Correction: He was not bought, he was the seller. If you own something it is up to you if you want to sell it or not.

    13. Re:Widenius please move on... by Elektroschock · · Score: 1

      Ah, and different stock option scheme when it is sold within 4 years...

      I see I see

    14. Re:Widenius please move on... by Anonymous Coward · · Score: 0

      Then what's stopping you? The other half, which doesn't want to pay for Oracle or SQL Server which will keep on using MySQL since it's free, regardless of "principle"?

    15. Re:Widenius please move on... by HiThere · · Score: 1

      You don't understand what's going on. He wants MySQL to be under a BSD or equivalent license because since it's under GPL he can't make a new proprietary version.

      BSD licenses have different dynamics, though not necessarily better ones. This would be like someone paying a Postgres developer to not work on it, and after he takes the money he wants to work on it anyway. ... Well, not really. There is no exact comparison. But that's the flavor.

      Anyway, MySql will be available under GPL. But now Sun, or Oracle, will be the only company allowed to make proprietary extensions. And unless the community puts together a project, it's not clear that the GPL version will get more development. (It's also not clear that it won't. We don't know what Sun/Oracle intends.)

      --

      I think we've pushed this "anyone can grow up to be president" thing too far.
    16. Re:Widenius please move on... by turbidostato · · Score: 3, Insightful

      "there's nothing stopping these developers from giving $1m of this to pay for someone else to work full time on the project..."

      Except the non-competing clause in their contracts, of course.

      And of course too, Widenius has a point, a moot point but a point: buying out everyone that happens to compete with you is a tried and true strategy to get away competitors. It's only it is not a long time strategy against a strong and open market, it doesn't scale and it happens that open source projects with an open community backing them up (say, KDE, Debian... PostgreSQL) are the most resistant against such strategy.

      So yes, Monty has a point... whatever.

    17. Re:Widenius please move on... by thetoadwarrior · · Score: 1

      Mainly because I'm still using shared hosting so I'm stuck with what they have but I've found this host http://rimuhosting.com/ which I think I'll be going with in about 6 months. Then I'll use what I want.

    18. Re:Widenius please move on... by Dragonslicer · · Score: 1

      he absolutely positively did not get $1 billion for mysql he got about $16.6 million... The whole company was bought for $1 billion and a very small portion, reportedly about 12% or less of that went to Widenius and the other mysql founder.

      Well, 12% of $1 billion would be $120 million, so if Widenius only got $16.6 million, the other founder must have gotten approximately $100 million, right?

      Even if you are correct, I don't see why receiving "only" $16 million should make a difference in people's criticism.

    19. Re:Widenius please move on... by koiransuklaa · · Score: 2, Informative

      None of your points are relevant...

      Of course Monty doesn't have the money to buy MySQL. It doesn't change the fact that he stayed completely silent on this until he got his millions. Maybe he only understood the problems of Oracle ownership then?

      If Oracle has patents they can use to kill MySQL, why on earth did they need to buy it first, and how would the situation improve if they were forced to sell it? That is an absurd idea.

      Of course monopoly is not good for the public. However, there is no monopoly here.

      Websites that were built on (non-gpl) mysql could be in trouble if Oracle wants to fuck them. That was the risk those websites took when they decided to go with a proprietary vendor. That would suck for them, but that's how proprietary software works.

      Users of GPL MySQL could be sightly inconvenienced: In the end a new community would still form around one of the forks. Again, for smart users selecting MySQL was a calculated risk of relying on a project with only one major developer.

      Did I forget anything?

    20. Re:Widenius please move on... by Briareos · · Score: 0, Offtopic

      That reminds me of that old C-64 game, "Auf Wiedersehen Monty"...

      --

      "I'm not anti-anything, I'm anti-everything, it fits better." - Sole

    21. Re:Widenius please move on... by Anonymous Coward · · Score: 0

      Mainly because I'm still using shared hosting so I'm stuck with what they have but I've found this host http://rimuhosting.com/ which I think I'll be going with in about 6 months. Then I'll use what I want.

      Did you look at eapps at all? Basic hosting starts at $9.90/month for a Linux VPS. They offer MySQL and PostgreSQL, or you can always install whatever else you want on it.

    22. Re:Widenius please move on... by LordAndrewSama · · Score: 1

      Have a look at linode.com too if it's the VPS options you're going for. they're now in london too, so unless you want the australian datacenter of that rimuhosting you mentioned they might be worth considering. :)

    23. Re:Widenius please move on... by ThePhilips · · Score: 2, Insightful

      Of course Monty doesn't have the money to buy MySQL. It doesn't change the fact that he stayed completely silent on this until he got his millions. Maybe he only understood the problems of Oracle ownership then?

      He understood the problem long before. And he made an agreement with first investors (long before Sun deal) that MySQL, if sold, would be sold to a company which has more reasons to continue MySQL development than reasons to kill it. That's why Sun deal hadn't provoked his attention (and at the time he was only a member of MySQL board, not employed by MysQL AB anymore).

      After ownership of MySQL went to Sun, obviously the investors changed too. Initial investors understood the value of MySQL and to whom it can/not be sold. Now to Sun investors it's peanuts and they do not care. So they sold Sun to Oracle.

      And Monty, as responsible parent, had to speak up...

      With all the over-religious F/LOSS rhetoric, people forget that everybody needs a job. And, sorry, having Oracle as your main competitor, isn't very inspiring - good luck explaining to investors how you are NOT going to be squashed by Oracle aggressive sales department. I think many people do underestimate what Monty/etc did with MySQL and how much they have created - all that thanks to the proprietary fork of MySQL - while at the same time maintaining GPL fork too - to the extent now that MySQL blocks Sun-Oracle deal.

      Websites that were built on (non-gpl) mysql could be in trouble if Oracle wants to fuck them. That was the risk those websites took when they decided to go with a proprietary vendor. That would suck for them, but that's how proprietary software works.

      Not at all. Companies which supply 3rd party modules to MySQL are fucked - users are not affected by a slightest. (Commercial users can upgrade to GPL version anytime.)

      Oracle can't kill users - Oracle can kill all MySQL ISVs. Thanks to the fact that MySQL client libraries are covered by GPL (what apparently was a part of how Monty attracted first investors).

      Did I forget anything?

      Yes, you forgot to RTFA and also Monty blog. Knowing why other side does and says what it does and says is important. Unless of course you simply want to troll.

      --
      All hope abandon ye who enter here.
    24. Re:Widenius please move on... by ThePhilips · · Score: 1

      Stop this non-sense. Monty wasn't owner of MySQL AB in times of Sun deal. He is only one of the founders and creators of MySQL.

      --
      All hope abandon ye who enter here.
    25. Re:Widenius please move on... by tehcyder · · Score: 1

      $50m for the 20 developers. Still quite a lot

      On the planet where I live $50m is an absolutely fucking huge amount for an individual, not "quite a lot".

      Have I strayed onto billionaire.org or something?

      --
      To have a right to do a thing is not at all the same as to be right in doing it
  3. someone is trying to sell this idea to Oracle. by Anonymous Coward · · Score: 1, Interesting

    someone is trying to sell this idea to Oracle. It is as simple as that.

    1. Re:someone is trying to sell this idea to Oracle. by leuk_he · · Score: 1

      to be more exact. 19 millions of an idea. The question is if larry will buy an other 200 million yacht or buy the top 20 postgres dev to let them make the next generation of database.

  4. Err... by Enry · · Score: 4, Insightful

    While buying out the top 20 developers (and I find it unlikely they could in the first place) wouldn't necessarily kill PostgreSQL, it would hamper development until the next 20 developers get up to speed with the code. Imagine what would happen if Microsoft were to buy out the top 20 Linux kernel developers - Linux wouldn't be dead, but it certainly would be stagnant for a while. There's also the real possibility of major changes, since the next group of developers would have a different way of doing things and different goals for the project.

    1. Re:Err... by jbwiv · · Score: 3, Insightful

      Um....there's over 70 committers to PostgreSQL. And even the top 20 work for a wide range of companies. Buying them out would be virtually impossible. PostgreSQL is an open source database done right, both technically and politically. You MySQL apologists simply refuse to acknowledge that you hitched your wagon to the wrong horse, even when your horse may be put down soon.

    2. Re:Err... by dfetter · · Score: 5, Insightful

      If somebody were willing to come up with a billion dollars in cash, they could buy the top 100 people in the PostgreSQL project, and that would cramp it severely for a couple of years.

      That said, Monty took VC money, which is basically legalized loan sharking. Taking VC money results, in the overwhelming majority of cases, in the complete screwing of the borrower. Monty was one of the lucky few who managed to get a fortune out of that situation, which makes his whining utterly unseemly.

      --
      What part of "A well regulated militia" do you not understand?
    3. Re:Err... by Kjella · · Score: 5, Insightful

      Um....there's over 70 committers to PostgreSQL. And even the top 20 work for a wide range of companies. Buying them out would be virtually impossible.

      And the whole concept seems to assume that there's a fixed pool of people. I'm guessing that if any of those companies lost their PostgreSQL guy, they'd be looking to hire another one and if it's anything like most open source software there's plenty unpaid or poorly paid people who'd love to take the position. Or with 10% unemployment, there would be soon enough if people knew they lacked developers. For that matter, I think it'd be hard to bury MySQL if just the entire community gathered on one fork and not a dozen.

      --
      Live today, because you never know what tomorrow brings
    4. Re:Err... by TheRaven64 · · Score: 4, Insightful

      Sun spent $1bn on MySQL. Spending the same amount of money on PostgreSQL would involve paying the top 20 developers $50m each not to work on PostgreSQL anymore (or to work on a proprietary fork of it). If I were offered that much not to work on a particular open source project, then I'd consider it quite seriously. For one thing I could pay someone else to work on the project full time while I did other things...

      The argument doesn't really make sense, because Oracle is vulnerable to the same tactic. What would happen if IBM offered even $1m to each of Oracle's top database programmers to quit? Would Oracle be able to survive? They'd have to hire a completely new team, but they'd probably manage it. The same is true of PostgreSQL (and other big hippyware projects). Most of the people who work on it are employed by companies which benefit from the project existing. If they all quit then these companies would hire other people to replace them. You'd see a little drop in productivity, but nothing permanent.

      --
      I am TheRaven on Soylent News
    5. Re:Err... by fast+turtle · · Score: 1

      In regards to IBM pulling the same against Oracle you forget one of the biggest reasons against it. Federal Action and Lawsuits. This would fall squarely under Anti-Competitive actions, thus the Feds (DOJ/Regulators) would all jump in and Oracle would have a Damn near ironclad suit against IBM for Lots more then 100M dollars. Even though the Nazgul would be out in droves, they still couldn't keep the ring bearer away from Mount Doom as the Armies of the 7 lands would be fighting them at the same time.

      --
      Mod me up/Mod me down: I wont frown as I've no crown
    6. Re:Err... by Anonymous Coward · · Score: 0

      There are 70 committers, but Bruce, Tom, and Peter contribute the lion's share of code, by far.

      Truth is, PostgreSQL could be bought rather easily, unless the primary contributers stood on principle and said "no way".

      The best way for anyone developing a free software project to demonstrate that they could never be bought would be to assign copyright to the FSF. It's a sure bet the FSF could not be bought - they are very clear about their primary objective: promoting free software. Have you seen a signed written document from any PostgreSQL developer that says "I will never contribute code to PostgreSQL unless such code is released under a free software license."? I think not.

      I'm not questioning the integrity or motivations of the PostgreSQL developers at all. I use PostgreSQL heavily. The community support for PostgreSQL is the best I've seen for any project anywhere. These guys are not only amazing coders, they are also great people - I know this from personal experience. But a billion dollars, to an individual, is a lot of money. You'd have to be Mother Theresa to turn down that kind of payday. Just sayin'.

    7. Re:Err... by RR · · Score: 1

      Monty took VC money, which is basically legalized loan sharking. Taking VC money results, in the overwhelming majority of cases, in the complete screwing of the borrower. Monty was one of the lucky few who managed to get a fortune out of that situation, which makes his whining utterly unseemly.

      I think, for Monty, the issue goes beyond just money. MySQL is his life work, his opus magnum, and I think it hurts him that his life work can be used in a way that he did not intend.

      Not to say that I agree with him, no. He still thinks of MySQL as proprietary software. He's not really thinking about it as free software.

      --
      Have a nice time.
    8. Re:Err... by Elektroschock · · Score: 1

      PostgreSQL just works fine. Probably PostgreSQL does not need so many developer.

    9. Re:Err... by jadavis · · Score: 3, Interesting

      The argument doesn't really make sense, because Oracle is vulnerable to the same tactic. What would happen if IBM offered even $1m to each of Oracle's top database programmers to quit?

      That would cause a problem for any organization, of course. But both Oracle and PostgreSQL have established policies and lots of historical precedent that guide new developers and project leaders while they are getting up to speed and filling empty roles. For instance, what happens when a significant patch hits the pgsql-hackers list that implements a new feature? Discussion begins, and then it goes on a public commit-fest page (http://commitfest.postgresql.org). When the commitfest begins, everyone stops work on their own patches, reviewers get assigned to patches, and after it passes review then a committer reviews it again and potentially commits it.

      With policies like that in place, as a few developers are hired away it's much easier for new developers to take their place. You don't get lopsided efforts. How does postgresql find enough reviewers? Reviewing is that much fun? No. If you don't review at commit fest time, then your patch is either ignored or at the back of the line.

      What happens when a patch hits the mysql list from a random contributor? Well, we don't really know, because MySQL isn't really a community project. They only know how to get patches committed and releases out the door from within MySQL AB (and that could obviously be questioned as well, seeing how long they went without a release, and the problems that happened when they did release, like Monty saying it wasn't ready).

      It's much easier to cause major damage to a disorganized project like MySQL.

      I believe MariaDB and Drizzle are both attempting to establish a real community project (notice I didn't say "re-establish"). I hope they succeed for the sake of MySQL users. But new users would be wise to count on a real organization like the PostgreSQL Global Development Group and it's established policies (or Oracle, for that matter).

      --
      Social scientists are inspired by theories; scientists are humbled by facts.
    10. Re:Err... by Anonymous Coward · · Score: 0

      Umm, assigning the copyright to a single entity is even riskier. Besides, PSQL's license is a lot better than anything FSF can ever hope to come up with. Even more, it looks like FSF has already sold out... What a novel concept: "assign the copyright to me cuz I'm soooo goooood." Boy, am I tired of this silliness.

    11. Re:Err... by Anonymous Coward · · Score: 0

      MariaDB? No thanks. We already know how Monty does it. Fool me once... but no more. Monty is forgotten history and so is everything he does.

    12. Re:Err... by ultranova · · Score: 2, Insightful

      If somebody were willing to come up with a billion dollars in cash, they could buy the top 100 people in the PostgreSQL project, and that would cramp it severely for a couple of years.

      If someone is willing to use a billion dollars in cash just to slow the development of a database program, they're unlikely to have a billion dollars to begin with.

      --

      Forget magic. Any technology distinguishable from divine power is insufficiently advanced.

    13. Re:Err... by Anonymous Coward · · Score: 0

      The FSF sold out to who?

      I'm not going to bite your BSD license troll bait.

    14. Re:Err... by HiThere · · Score: 1

      Having watched the judicial process in action... I doubt it. IBM would just buy a few legislators and the judges would find for IBM. Look what one company has been able to accomplish through just hiring the son of Orin Hatch. They also hired a few lawyers, admittedly. It's true the company is going to end dismembered, but they were headed that way before they started playing legal games. Without them they'd probably have been gone years ago.

      So don't depend on the courts for justice. They don't have any to offer.

      --

      I think we've pushed this "anyone can grow up to be president" thing too far.
    15. Re:Err... by jadavis · · Score: 1

      Well, for existing MySQL users, they have the following options:

      1. Rely on Oracle to support MySQL
      2. Rely on a MySQL community to develop outside of Oracle
      3. Jump to another DBMS, like PostgreSQL

      If the cost for #3 is reasonable, that's probably the wisest choice. If not, #2 is probably the wise choice. And Monty will be an important player in #2 because he is a leader, whether you like it or not.

      That's not to say that he won't join Drizzle (good leaders can follow and lead at the same time), for instance. I think that might very well happen, because trying to launch two DBMS communities from scratch seems unlikely to succeed.

      --
      Social scientists are inspired by theories; scientists are humbled by facts.
    16. Re:Err... by h4rm0ny · · Score: 1


      Just to add even more to your good points, a company like Oracle has contractual protections in place for their most valued developers. Well, I don't actually know this, but I'm sure it must be so. Say Mr. Top Developer is on three month's notice. He announces he's been hired away by IBM. No doubt he or she would immediately be assigned the task of training up some very savvy developers for those remaining three months.

      --

      Aide-toi, le Ciel t'aidera - Jeanne D'Arc.
    17. Re:Err... by Briareos · · Score: 1

      If somebody were willing to come up with a billion dollars in cash, they could buy the top 100 people in the PostgreSQL project, and that would cramp it severely for a couple of years.

      If "they" had a billion dollars, wouldn't hiring hitmen for those 100 people allow them to keep a huge part of that sum?

      --

      "I'm not anti-anything, I'm anti-everything, it fits better." - Sole

    18. Re:Err... by nurb432 · · Score: 1

      Then they buy the next 20... then the next. While it may not kill a project, if it doesn't move forward it might as well be dead.

      --
      ---- Booth was a patriot ----
  5. Stop quoting Monty by Anonymous Coward · · Score: 4, Insightful

    Please stop quoting Monty in slashdot stories, you're giving him a bigger platform for his comments than he deserves. He sold MySQL to Sun and then left Sun. That should be the end of the story. Now he's making sounds like a regular cry baby. Someone please tell him to get some balls and grow up.

    1. Re:Stop quoting Monty by thetoadwarrior · · Score: 1

      This guy speaks the truth. Please, no more stories about the cry baby.

    2. Re:Stop quoting Monty by sproketboy · · Score: 1

      Well this is giving a lot of space to PostgreSQL which is a superior DB so I don't mind so much.

  6. Let me say this as a developer, contributor, by unity100 · · Score: 1

    webmaster, publisher, community leader, administrator.

    if anything 'bad' happens to mysql, heads will roll.

    1. Re:Let me say this as a developer, contributor, by Bill_the_Engineer · · Score: 5, Insightful

      if anything 'bad' happens to mysql, heads will roll.

      Probably yours...

      Widenius is only using scare tactics to try to get MySQL back after enjoying the profits from selling it in the first place.

      His constant whining will morph into a cautionary tale about using open source programs in a production environment.

      Phrases like "You don't get fired for buying from Oracle, Microsoft, or IBM" will return to the IT workplace and all the work open source developers did to enter the workplace will be set back several years.

      --
      These comments are my own and do not necessarily reflect the views or opinions of my employer or colleagues...
    2. Re:Let me say this as a developer, contributor, by atomic777 · · Score: 1

      Heads need not roll. Anyone with a large exposure to mysql should be at least getting a sense of how painful it would be to migrate to postgresql, and ideally have been doing some of this research for at least the past year when it was clear mysql was headed for trouble.

      But even in the worst case, mysql would turn into a type of legacy application, with support and bug fixes provided by 3rd parties. This would be not nearly as bad as the suffering of companies back in the day dealing with legacy systems where they can't even figure out who might even know where the original source is, let alone someone to fix or enhance something for you.

    3. Re:Let me say this as a developer, contributor, by Anonymous Coward · · Score: 3, Interesting

      That is a very good point indeed. mysql was the cat's meow in the internet's early days; everybody was doing a web portal and mysql is fast as hell with simple lookups. Just the ticket. Now even databases that were supposed to stay simple are morphing into who knows what. mysql's engine still can't even do transactions and they own nobody whose plugin can. Even if they're not a target they'll always be weak in their market no matter how popular they are. Postgresql (for example) has always kicked mysql's butt in real database work, and now that it has pretty much closed the speed gap in the simple things there's no need to chase mysql anymore. They're after bigger game: Full SQL compliance and Oracle. And there's other OS DBs out there doing fabulous work as well.

      Personally, mysql served me well back in the day but I've moved on to new tools for new needs. Unless thay can actually own a modern engine rather than begging one I think mysql should remain as it is; sort of a bug in the amber of simpler times.

    4. Re:Let me say this as a developer, contributor, by Anonymous Coward · · Score: 0

      PostgreSQL has excellent license, contributors and community. It's not a hack job of a whiner like MySQL is. There is a big difference between the two. In a few short years PostgresQL will be everywhere and no one will remember MySQL or Monty for that matter.

  7. It would do fine by vanilla_face · · Score: 4, Interesting

    Postgres has a diverse group of contributors so it will be absolutely nothing like Oracle acquiring MySQL. Sure it would be temporarily damaging to the project if Oracle did go out and buy the leading contributors but I can't imagine that Oracle would get away with such predatory actions. FTR I believe that Oracle genuinely wants to use MySQL as s competitor to SQL Server in the bottom of the market.

    1. Re:It would do fine by Anonymous Coward · · Score: 0

      You are joking. If Oracle wants to survive it has to put Oracle on every device, not MySQL or PostgreSQL, that's what MS is doing with the different flavors of SQL Server,not Access or FoxPro. With the following Nehalem MP processors Windows 2K8R2 will be face to face with UNIX, and the position of SQL Server in the big market will be very different than is today with the poor Itanium.

    2. Re:It would do fine by Anonymous Coward · · Score: 1, Interesting

      So we should expect Microsoft to ditch Access and start selling SQL Server to MS Office users? Unless you're the one who's joking?

  8. Postgresql probably more vulnerable to patent... by Anonymous Coward · · Score: 0

    attacks. Oracle has got to have enough in their patent portfolio to scare off
    commercial PostgreSQL users.

  9. Why trust Sun? by argent · · Score: 5, Insightful

    This is precisely why people were concerned about letting ANY single company own it.

    Any company can be bought out.

    If a product can't be effectively forked, it's not completely open source.

    If a GPL fork of MySQL isn't good enough, then whose fault is that? And what does that mean for other dual-licensed GPL+Proprietary products?

    1. Re:Why trust Sun? by OverlordQ · · Score: 2, Interesting

      Any company can be bought out..

      No, not really. As pointed out one of those 'top 20' works at NTT. Lets compare revenues.

      NTT: $106.289 billion (2009)
      Oracle: $ 23.252 billion (2009)

      I think the buying out would go the other way.

      --
      Your hair look like poop, Bob! - Wanker.
    2. Re:Why trust Sun? by atomic777 · · Score: 1

      But Oracle would not need to buy out companies, just key people.

      Oracle could just offer that one NTT employee, say, a "consulting" position at Oracle, for, oh, 50x his current salary. There would be some tiny little clause in his contract stating something along the lines of "you shall remain 50 yards from any computer that contains the source code for the postgresql database"

      I'm not suggesting that Oracle can or should do this (see my other comment) but that the comparison between NTT and Oracle is not meaningful.

    3. Re:Why trust Sun? by greg1104 · · Score: 3, Interesting

      At which point NTT would promptly hire/promote someone else into the same position with the same level of resources necessary to be effective. For example, in addition to committer Itagaki Takahiro, they also have some major work on replication being led by Masao Fujii. The point of having a big company like NTT involved is that you can't just make their need for PostgreSQL to be successful go away so easily. There's not just "that one NTT employee"--he's one of a whole team there doing PostgreSQL related work.

    4. Re:Why trust Sun? by _Sprocket_ · · Score: 1

      If a product can't be effectively forked, it's not completely open source.

      If a GPL fork of MySQL isn't good enough, then whose fault is that? And what does that mean for other dual-licensed GPL+Proprietary products?

      The only one that seems to be having trouble with this is Monty Widenius. And it seems his issue is being unable to re-create a proprietary fork. So if your goal is to maintain a proprietary product, and you don't own the copyright to the code, then big surprise... the GPL is an issue. But then, that's kind of the point of the GPL.

    5. Re:Why trust Sun? by argent · · Score: 1

      Fair enough. That'd be as freaky as Compaq buying DEC.

    6. Re:Why trust Sun? by argent · · Score: 1

      OK, any company can shut down a project. Or sell it, or whatever. The point is that MySQL was dual-licensed proprietary+GPL and once it was sold to Sun the fate of the proprietary license was the fate of Sun.

      PostgreSQL is BSD licensed. So it doesn't need a dual license strategy to allow it to be used in the ways that MySQL's proprietary license let it be used. Which means it's at less risk because you *can't* own it the way Sun could own MySQL.

      In any case, doesn't Oracle pretty much already own MySQL's balls because they own InnoDB?

    7. Re:Why trust Sun? by atomic777 · · Score: 1

      Of course, I didn't mean to suggest that Oracle could be successful with such a strategy. The best they can hope for is to sabotage or try to slow the adoption and development of pgsql, but as long as there are companies like NTT that are willing to put resources into its development, it will be a losing battle.

  10. And Monty Widenius knows about being bought! by Anonymous Coward · · Score: 5, Insightful

    no text necessary!

  11. Not even Oracle is evil enough to try this by atomic777 · · Score: 5, Insightful

    While he is technically correct that Oracle could just bribe the key developers to abandon pgsql, this would likely backfire.

    First, it assumes that the pgsql developers of importance can be bought. Our world is decadent, but not everyone has a price tag

    Second, seems Monty has been dealing with mysql code for too long. The pgsql code base (at least the parts I've seen) is significantly more pleasant to work with than MySQL's, and the sheer number of projects building off of it, commercial or OSS (due to BSD licence) are a testament to how accessible it is. Even if all of the current developers were to be bribed and stopped working on postgresql, there would be a significant incentive for other parties to step in and pick up the slack, given that postgresql has a sizable user base, and especially since it is now widely seen as the heir-apparent to mysql as the open-source rdbms of choice for your run-of-the-mill applications.

    Add on top of that the bad press from a failed attempt to use such questionable tactics, and I think not even Oracle is greedy or dumb enough to try anything.

    1. Re:Not even Oracle is evil enough to try this by Hurricane78 · · Score: 4, Insightful

      I agree. Hell, even PostgreSQL’s documentation is literally fun to read. It’s clean, it’s complete, it’s concise. Other projects should learn from them.

      --
      Any sufficiently advanced intelligence is indistinguishable from stupidity.
    2. Re:Not even Oracle is evil enough to try this by Anonymous Coward · · Score: 2, Insightful

      > First, it assumes that the pgsql developers of importance can be bought.

      No, first it assumes that Oracle has an interest in aquiring or stopping postgresql at all.

    3. Re:Not even Oracle is evil enough to try this by Florian+Weimer · · Score: 1

      I agree. Hell, even PostgreSQL’s documentation is literally fun to read. It’s clean, it’s complete, it’s concise. Other projects should learn from them.

      Contrast this with the sad fact that most (all?) the MySQL forks lack almost all documentation because MySQL AB never received the documentation under a free license.

    4. Re:Not even Oracle is evil enough to try this by dkleinsc · · Score: 1

      First, it assumes that the pgsql developers of importance can be bought. Our world is decadent, but not everyone has a price tag.

      Really? To quote Tom Lehrer:
      "It's so nice to have integrity, I'll tell you why:
      'Cause if you really have integrity, that means your price is very high."

      While I'd probably be resistant to being bought out, if the price were high enough I would at least consider it. If I were in that position, I'd think about taking the big bucks, retiring from my day job, and working on and donating to other open source projects (and probably some other worthy causes as well) while enjoying my comfortable retirement.

      And the wonderful thing about open source licenses is that it would be very easy for someone else to take up my hard work, so as far as I was concerned somebody just paid me big bucks for nothing at all.

      --
      I am officially gone from /. Long live http://www.soylentnews.com/
    5. Re:Not even Oracle is evil enough to try this by Blakey+Rat · · Score: 2, Insightful

      First, it assumes that the pgsql developers of importance can be bought.

      The biggest assumption is that Oracle wants to do this in the first place. Microsoft has SQL Server and IBM has DB2, neither of them have tried to buy out PostGRE... Sun's been around for decades and they've never tried it before...

      It's just fear-mongoring from Monty.

    6. Re:Not even Oracle is evil enough to try this by sdiz · · Score: 1

      PostgreSQL have a policy, all feature-changing commit must have the documentation included.

    7. Re:Not even Oracle is evil enough to try this by nurb432 · · Score: 1

      While he is technically correct that Oracle could just bribe the key developers to abandon pgsql, this would likely backfire.

      First, it assumes that the pgsql developers of importance can be bought. Our world is decadent, but not everyone has a price tag

      No, everyone does have a price. The question is if that price is too high to be feasible. And who says hiring them is a bribe? If you get hired away to work on other projects, its called getting another job, not being bribed. Happens every day.

      --
      ---- Booth was a patriot ----
  12. A billion bucks... by RicardoGCE · · Score: 4, Funny

    ...sure makes some people whiny.

    1. Re:A billion bucks... by tehcyder · · Score: 1

      But, sadly, being whiny doesn't make you a billion bucks.

      --
      To have a right to do a thing is not at all the same as to be right in doing it
  13. Please... Monty by Anonymous Coward · · Score: 0

    Monty: Please go away.

  14. Please name names by bogaboga · · Score: 3, Informative

    I would like to have a list of serious companies using PostgreSQL for serious stuff...and what stuff it is PostgreSQL is doing. In my world, all you hear is "...MySQL...MySQL...", even in cases where the back-end is being handled by PostgreSQL.

    Our three major DBs have about 13.4 million records combined, with enormous amounts of data about clients. PostgreSQL has never failed us. I work in the insurance business.

    1. Re:Please name names by greg1104 · · Score: 5, Informative

      I would like to have a list of serious companies using PostgreSQL for serious stuff

      PostgreSQL Featured Users; Quotes has additional detail about the scope of some of those. Most people are probably familiar with names like Skype and Cisco on there, but less well known companies like NTT are huge too--and they even sponsor a good chunk of PostgreSQL development because it's so heavily used there.

      And those are just the public record. Because of its BSD license, PostgreSQL also gets used in plenty of places that don't talk about what they're doing with it. For example, I've worked with financial companies that are cutting loose Oracle for PostgreSQL whenever feasible, and with some US defense companies that use PostGIS for geographic databases. (looks out window) I may have already said too much.

    2. Re:Please name names by Lemming+Mark · · Score: 1

      Not a serious company but thought I'd note that OpenStreetmap (http://openstreetmap.org) uses PostgreSQL to store data for their Mapnik rendering engine and PostGIS to query it. They're rendering user-contributed map data for the entire world, so that's a fairly serious operation.

    3. Re:Please name names by gbjbaanb · · Score: 4, Interesting

      It'll be difficult to say who's using it because they download it, try it, run it.. all quietly without fuss. No-one at PostgreSQL website can say who's using the downloads because there's no licensing or even a 'email to get your registration' type stuff going on.

      I can tell you that 3 large UK emergency service centres (the 911 callcentres) use PostgreSQL for handling the incoming 999 calls. Its been used for some time now and we've not had a major failure (I don't think we've had a single failure of any type come to that).

      Taking calls for the emergency services is as serious as you can get. It's even more serious if you're the one who wants an ambulance!

    4. Re:Please name names by maroberts · · Score: 2, Informative

      I'm working for a major European bank; we use PostgresSQL for most of our data aggregation and analysis. I'm really a long term MySQL user, but haven't found any problems doing the same stuff with a different database

      --

      Donte Alistair Anderson Roberts - hi son!
      Karma: Chameleon

    5. Re:Please name names by Toze · · Score: 3, Informative

      For them as don't RTFL, the Featured Users include IMDB.com, SourceForge, Safeway, and Skype.

      --
      No OS on the planet can protect itself from a user with the admin password. - Yvan256
    6. Re:Please name names by jimicus · · Score: 1

      PostgreSQL users tend to shut up and get on with it quietly and efficiently.

      MySQL users tend to indulge in all sorts of public willy-waving.

      Much like the databases they use, in fact.

    7. Re:Please name names by mcrbids · · Score: 4, Informative

      It'll be difficult to say who's using it because they download it, try it, run it.. all quietly without fuss. No-one at PostgreSQL website can say who's using the downloads because there's no licensing or even a 'email to get your registration' type stuff going on.

      We started with yum -y install postgresql-server and now, hundreds of busy clients later and a few updates later, Postgresql is still going stronger than ever...

      And seriously, Postgres is the overachieving underdog of the database world. It has it all - replication, data integrity, legendarily stunning stability, MVCC, foreign keys, triggers, PLPGSQL, subselects, indexes, query scheduling, parameterized statements, DDBC, metatables, cross-database joins... I could go on, and on, and on. It holds up very nicely when Its security
      model is excellent. Its organizational model is stable. It holds up well under very demanding loads and just basically doesn't crash. (In a decade of using it every single business day, I've NEVER HAD an instance of Postgres corrupt running on a RedHat/CentOS server) It costs nothing, it's available by default on any RedHat install CD, and most other distros.

      If Oracle is scared, they should be scared of PostgreSQL, and if you're looking to database something, you should strongly consider Postgres!

      --
      I have no problem with your religion until you decide it's reason to deprive others of the truth.
    8. Re:Please name names by Anonymous Coward · · Score: 0
      PostgreSQL is used by the Indian Air Force, Indian Navy, DAE (Department of Atomic Energy), ISRO amongst other government departments in India. They just do not like to talk about it, and each of these organizations has enough budget to fork from the current code base (in case PostgreSQL is 'posioned' by Oracle), hire developers and continue development.

      Mysql people need to stop bitching about PostgreSQL because there beloved DB is getting eviscrated. PostgreSQL always adhered to standards, has rock solid reliability and with the latest releases is as fast as MySQL. If you are so "concerned" about Oracle, quit whining, migrate to PostgreSQL and join the development teams to make it even better.

      A theif thinks all other people are also theifs, that is the best that can be said about MySQL people.

    9. Re:Please name names by walterbyrd · · Score: 1

      MXLogic uses PostgreSQL as their major production database. I know of some other luggage company in Denver that uses PostgreSQL, but I forget the name of the company.

    10. Re:Please name names by gbjbaanb · · Score: 1

      There's one thing it doesn't have - the developer mindshare. When someone's writing their PHP webapp, the first thing they think is "install MySql", not "install PostgreSQL".

      Perhaps now they'll start to update the code and we'll get a LAPP stack instead of LAMP.

    11. Re:Please name names by TeknoHog · · Score: 1

      IIRC, distributed.net uses Postgres, but their statistics server is down at the moment, so I cannot confirm it...

      --
      Escher was the first MC and Giger invented the HR department.
    12. Re:Please name names by rasherbuyer · · Score: 1

      Nicely put

    13. Re:Please name names by rasherbuyer · · Score: 1

      But web developers don't actually need 'real' databases 90% of the MySQL web databases I've seen are just used to store text and maybe a few other things in one or maybe two tables.

      PostgreSQL is a competitor to Oracle with features that real database developers use. MySQL is not.

    14. Re:Please name names by slick_rick · · Score: 5, Funny

      I happen to know that right after the Columbia accident, all the telemetry data was loaded into a PG database and that is what was used for analysis. At one point tracking the entire .org domain was done with PG as well. I've always thought of MySQL as a racehorse, no other horses can compete for speed when running around a short track (IE read-mostly website). PG is more of a draft horse, able to plow the fields, or pull the wagon, or do a million other things that MySQL is not appropriate for. Oracle would be an Elephant, too huge and expensive to maintain for most things while SQL Server would be a mule, a hopefully sterile off-breed of a horse (Sybase) and a donkey (Windows).

      --
      apt-get install redhat please god - Me (take it easy, I love Debian)
    15. Re:Please name names by Anonymous Coward · · Score: 0

      Hi, I've worked for MySQL (and now Sun) Engineering for the last several years. I don't speak in any official capacity, but I thought you might like to know a few things...

      PostgreSQL is used by the Indian Air Force, Indian Navy, DAE (Department of Atomic Energy), ISRO amongst other government departments in India.

      Great! We're glad they have a product that works for them. We're well aware that people have choices. Choices are good. Obviously, we love it when people choose MySQL, but we believe that competition is good for users, and good for MySQL. Those were core values at MySQL AB, and they're core values at Sun.

      Mysql people need to stop bitching about PostgreSQL because there beloved DB is getting eviscrated. PostgreSQL always adhered to standards, has rock solid reliability and with the latest releases is as fast as MySQL. If you are so "concerned" about Oracle, quit whining, migrate to PostgreSQL and join the development teams to make it even better.

      They do? I thought we were busy creating a product and supporting it. In fact, my experience is that it's all too often the Postgres supporters who get defensive, appearing in droves and trolling whenever MySQL is mentioned on this site (and others), but the reverse seldom if ever happens.

      Such behaviour is extremely unprofessional and unbecoming. If anything there's a few Postgres supporters who could learn a thing or two about how to conduct themselves from the example set by my colleagues, who strive to promote a positive and professional attitude on and off the job. It's one of the reason I'm damned proud to work with these people.

      A theif thinks all other people are also theifs, that is the best that can be said about MySQL people.

      In any case, may I remind you:

      1. Monty no longer works for MySQL. Perhaps you hadn't noticed, but he has his own company now.

      2. Monty does not speak for MySQL. How can he speak for something he is -- by his own choice; I might add -- no longer a part of?

      So please do not attribute any statements from Monty as being "from MySQL people" because he is in absolutely no position to speak for either the company nor its employees.

      Thank you!

    16. Re:Please name names by sakdoctor · · Score: 1

      You should register the /. name EquineAnaologyGuy if you're planning to do that often.

    17. Re:Please name names by bbtom · · Score: 1

      LAMP = Linux, Apache, MySQL, PHP

      Naah. PHP is old. Get with the times. Ruby, man. If only because you can use the following stack abbreviations:

      LAMR = Linux, Apache, MySQL, Ruby

      LARP = Linux, Apache, Ruby, PostgreSQL*

      Don't be a LAMR (because everyone hates lamers) or a LAMPpost (dogs will pee on you) - be a LARPer instead! You get to fight people with polystyrene swords and wear a cape! And then come home and use a good RDBMS and a nice programming language!

      * Justification for reversing the database and programming language: you can build an application quite easily that has no database backing. Flat-file or just in-memory storage or whatever. If you wrote an application that simply read an XML file from the filesystem, you would not feel the need to include the IO library or the XML parsing library in the stack diagram. So, therefore, the database and the programming language are really not depdendent on one another. The order of the letters in the abbreviation have little actual meaning, so the strategy of ordering them so that the abbreviation sounds cool and makes a nerdy reference is just a valid strategy as any other. Sort of.

      --
      catch (HumourFailureException e) { e.user.send("You, sir, are a humourless idiot."); }
    18. Re:Please name names by greg1104 · · Score: 1

      At one point tracking the entire .org domain was done with PG as well

      Still is; even more than that actually, .info too. See Afilias Global Registry for a full list. Afilias sponsors quite a bit of PostgreSQL related work, including employing some of the major contributors to Slony, one of the most popular PostgreSQL replication solutions.

    19. Re:Please name names by Anonymous Coward · · Score: 0

      My company runs a ~1 TB PostgreSQL database. It's been a champ for years. We treat it badly in terms of some old, nasty queries that we haven't had the resources to track down and replace, and the performance has been excellent, all things considered.

    20. Re:Please name names by Evro · · Score: 1

      I've used Postgres for years but this is the first I've heard of cross-database joins. When was that added?

      --
      rooooar
    21. Re:Please name names by LizardKing · · Score: 1

      I would like to have a list of serious companies using PostgreSQL for serious stuff

      PostgreSQL is widely used by the different government bodies that run London (in addition to the one I work for, they include Transport for London and City Hall). I'm not aware of anyone in the bodies that we deal with who use MySQL, although Oracle and SQL Server are.

    22. Re:Please name names by shutdown+-p+now · · Score: 2, Insightful

      It does have developer mindshare, it just doesn't have PHP developer mindshare.

      Then again, PHP and MySQL are a match made in heaven - both underfeatured and broadly outdated, but immensely popular because of (often misleading) marketing, and mostly just being in the right place at the right time.

      They're also alike in that, if we could get rid of both, and have, say, Linux+Apache+Python+Postgres, that would make the lives of many developers and admins easier, and the world just a little bit better.

    23. Re:Please name names by mcrbids · · Score: 1

      In case you see this, it's called dblink and there's some installation required. (it's very easy)

      --
      I have no problem with your religion until you decide it's reason to deprive others of the truth.
    24. Re:Please name names by deniable · · Score: 1

      Trend Micro bundles it with some of their gateways. Nortel uses it in its Telephony Manager. I've seen it bundled with other systems. It's taken off with the native Windows build.

    25. Re:Please name names by shish · · Score: 1

      MySQL as a racehorse, no other horses can compete for speed when running around a short track (IE read-mostly website)

      <anecdote>My read-mostly website started out on mysql, and ground to a halt around 500 users; after adding loads of ugly mysql-specific hacks it just about managed 800 -- then I switched to postgres with the original simple elegant queries, and it's run fine, recently breaking 2000 users with the same hardware</anecdote>

      --
      I mod down anyone who says "I will be modded down for this", regardless of the rest of their comment
  15. Sour grapes? by rasherbuyer · · Score: 0, Flamebait

    because PostgreSQL kicks MySQL's ass in everything except market share whichever way you look at it

    1. Re:Sour grapes? by Anonymous Coward · · Score: 0

      Nope... one major thing PostgreSQL sucks at is replication. You have to buy a commercial add on to get a decent implementation.

    2. Re:Sour grapes? by nitehawk214 · · Score: 1

      Nope... one major thing PostgreSQL sucks at is replication. You have to buy a commercial add on to get a decent implementation.

      I would rather pay for replication then transactions.

      --
      I'm a good cook. I'm a fantastic eater. - Steven Brust
    3. Re:Sour grapes? by thePowerOfGrayskull · · Score: 1

      Nope... one major thing PostgreSQL sucks at is replication. You have to buy a commercial add on to get a decent implementation.

      I would rather pay for replication then transactions.

      Ah, quick... witty... and about 7 years out of date.

    4. Re:Sour grapes? by Anonymous Coward · · Score: 0

      the exact point being that innodb isn't gpl, and was actually bought by oracle independently
      of the deal with sun
       

    5. Re:Sour grapes? by siDDis · · Score: 4, Informative

      What? The open source replication alternatives are good enough

      You have:
              * PGCluster
              * Slony-I
              * DBBalancer
              * pgpool
              * PostgreSQL table comparator
              * SkyTools
              * Sequoia
              * Bucardo
              * Mammoth Replicator
              * Cybercluster
              * GridSQL (shared-nothing)

      All are open source and some even offer additional commercial support.

    6. Re:Sour grapes? by Anonymous Coward · · Score: 0

      InnoDB (and BDB) was bought up by Oracle. They didn't kill it which kind of disproves monty's argument, not that there was any substance behind it in the first place.

    7. Re:Sour grapes? by xtracto · · Score: 1

      Is there any reason to pay replication before transactions?

      --
      Ubuntu is an African word meaning 'I can't configure Debian'
    8. Re:Sour grapes? by HiThere · · Score: 1

      Sorry, that doesn't disprove the argument. Oracle could just be very patient.

      OTOH, my guesstimate is that Oracle intends to be to databases what Google is to information access...trying to index everything on the planet. (Google's goal seems the more practical, because immutable copies count as equivalents. So, e.g., Bing indexing something doesn't interfere with Google's also indexing it.)

      --

      I think we've pushed this "anyone can grow up to be president" thing too far.
    9. Re:Sour grapes? by Anonymous Coward · · Score: 0

      I have used Postgres for over a decade. We developed a complete webmail system with 100k users on it. At the time we compared MySQL and Postgres and actually found the latter to be significantly better in the performance department. We looked into doing replication and unfortunately after evaluating nearly every of the products you list we found they were mostly incomplete or not entirely compatible. A complete ground-up replication service is needed with good integration into the core services of the database. Not surprising that this implementation needs to come from a part of the close-nit group of core developers rather than some hobbyists who may or may not entirely understand all the needed technical criteria.

    10. Re:Sour grapes? by shish · · Score: 1

      You have:

      11 projects which are pain in the ass to individually try out, fail to make work, and move on to the next is not better than one project that works out of the box; the developers themselves have finally realised this, hence making "a simple replication system that covers 90% of users out of the box" a release goal for 8.5 (though it was also a top goal for 8.4, and 8.3...)

      --
      I mod down anyone who says "I will be modded down for this", regardless of the rest of their comment
    11. Re:Sour grapes? by thePowerOfGrayskull · · Score: 1

      InnoDB (and BDB) was bought up by Oracle. They didn't kill it which kind of disproves monty's argument, not that there was any substance behind it in the first place.

      It was bought up, but it's also still dual licensed - which means Oracle can't kill it.

    12. Re:Sour grapes? by thePowerOfGrayskull · · Score: 1

      the exact point being that innodb isn't gpl, and was actually bought by oracle independently of the deal with sun

      Actually InnoDB is released dual-license - GPL and proprietary.

  16. Because it's open source and they can't control it by Hurricane78 · · Score: 0

    DUH!

    Some people don't do it for the money. You can't buy them. Ever.

    For me it's like that: I have a goal that I see as the point of my existence. Big money does not help that goal. So no money in the world can change my goal. And nothing can stop me from pursuing it. Because that would be the end of existence. If I don't want to chew bubble gum, not even a million will change that. (One guy tried that on me, but with $1000 on the table. Just to chew one strip of gum. I said no, and I'm proud of it. It drove him and his tiny mind crazy that evening. :)
    If money can trump your principles, you've got no principles but are a lying bastard. (Yes I know that this goes completely against the “official” US philosophy. But we don’ have to agree, have we? :)

    --
    Any sufficiently advanced intelligence is indistinguishable from stupidity.
  17. There's another angle by Trailer+Trash · · Score: 1

    Even if all the pgsql developers quit today and nobody came in to continue, it would still be a better product than mysql will ever be.

  18. Obviously, there is one thing Oracle did by smchris · · Score: 1

    They released free version XE for the department/small business server. If nothing else, that demonstrates the power of PostgreSQL to give the consumer a break in the marketplace. Up there with Apache and OO.org as one of the premiere open source display projects. I hope that excellence keeps them committed.

    1. Re:Obviously, there is one thing Oracle did by ascari · · Score: 1
      Not apples to apples: Oracle XE has severe limitations that affects scalability/usability: Max 4GB of data, max 1 CPU, max 1GB of RAM usage, only 1 running instance etc. etc.

      More important to a corporate user is that XE is unsupported, closed source software whereas PostgresQL has corporate support and is open source. "Free" as in no cost is not the big issue here.

  19. Sod Off Monty by segedunum · · Score: 3, Interesting

    I'm getting fed up to the back teeth with this guy. He must have got himself into some mental issues he can't get out of. He had a dual licensed database server in MySQL that brought in good money and had a side-effect of making it the standard database as the web expanded, which he then sold to Sun for a very tidy sum and he still now expects to be able to control MySQL's future?

    Before Sun bought MySQL Sun was heavily involved with Postgres (still is in many ways) and they could have quite easily tried to take that project over as opposed to buying MySQL. They didn't, and they would have found that very difficult because there are a lot of different interests in Postgres now.

  20. It is not a ridiculous claim by Anonymous Coward · · Score: 0

    The sad truth is that most FOSS projects rely on one, or a handful of key people. If those people leave or are bought out - or more subtly, influenced - the project could be killed or undergo a significant change of direction. There is no guarantee that others will step in with sufficient knowledge or expertise to take their place.

    Postgesql languished for years before it was picked up again. There is nothing to suggest that couldn't happen again if the top developers were bought out. Very few people aren't susceptible to a nice pay check, especially when it is paid to them for what they are doing already.

    The BSD license allows the wholesale privatisation of all software development produced under its writ. That is what it was originally intended for, to privatise government funded software produced by educational institutions.

    The BSD licence is only 'more free' in the double speak sense that you are free to restrict the freedom of others to access your additional code. No unlike the greater democracy of Hitler's Germany where the people were even free to vote away their democratic rights - which they promptly did.

    1. Re:It is not a ridiculous claim by AlexLibman · · Score: 1, Insightful

      The slave morality of MySQL freeloaders is mind-boggling here! People who choose to devote their time and talent to developing free software are not your slaves! They have rights too, including the right to do what's in their own personal interest. Free / open source software is a natural consequence of free market competition, not government force!

      BSD is the most restrictive license a freedom-loving person should ever want to use. GPL is even more dependent on government force than proprietary software is, but usually doesn't come close to it in terms of quality or convenience.

    2. Re:It is not a ridiculous claim by Anonymous Coward · · Score: 0

      There is no "double speak" in the BSD license. You must be a Linux sapper shill airdropped from the hovering bazaar. That or you just don't understand the language. Linux people like to confuse the distinction between "open" and "free" all the time because it suits their current politics and their social ur-agenda. The various GPL licenses (which one is the cool one this week?) enforce openness. The BSD license allows freedom; even the freedom to do things that tick others off. That's the real world buddy boy. People sometimes piss you off because they're free entities too. It actually makes the big blue room a more interesting place.

      Finally, nobody is forcing the BSD license on anyone so it is impossible for someone to "restrict the freedom of others to access your additional code." (Emphasis mine.) Your addition of the hitler tag is not germane here and is beneath contempt. Nice work.

    3. Re:It is not a ridiculous claim by jocknerd · · Score: 2, Interesting

      PostgreSQL languished from 1993-1996. Then the developers who looked at the code decided it was best to rewrite everything from scratch. This slowdown in development is why MySQL became more popular in the late 1990's. Plus, it was the database used in almost PHP book published. PostgreSQL in the late 1990's through early 2000's had a very solid codebase but very little work had been done on it from a performance perspective. Work throughout the 2000's has improved the performance tremendously and now the core team is focusing on bring replication to it natively.

    4. Re:It is not a ridiculous claim by Anonymous Coward · · Score: 0

      Godwins law, bsd vs. gpl trolling, and open source vs. closed source trolling all in one post? I'm impressed.

    5. Re:It is not a ridiculous claim by Anonymous Coward · · Score: 0

      If your earlier post didn't prove that you're a moron, this one certainly does. FOAD already.

    6. Re:It is not a ridiculous claim by stox · · Score: 2, Informative

      PostgreSQL did not exist in 1993-1995. It was Postgres, and Postgres95 in that timeframe. It had its own query language. It was re-written to use SQL, and then became PostgreSQL.

      --
      "To those who are overly cautious, everything is impossible. "
    7. Re:It is not a ridiculous claim by turbidostato · · Score: 1

      "GPL is even more dependent on government force than proprietary software is"

      Half true; GPL is not more government dependant than propietary software is and probably a bit less... but even this is utterly irrelevant since GPL's government dependency only needs to last for as long as government's support for proprietary software it works against.

    8. Re:It is not a ridiculous claim by ducomputergeek · · Score: 1

      Mod parent up. He's hit it on the head when it comes to the history of PostgreSQL. What is missing is that fact that PostgreSQL had table/row locking and other ACID compliant features way before MySQL. And even with MySQL, they had to import the features using other DB engines such as Berkley or InnoDB. While native replication has been missing there are a number of 3rd party clustering tools that work extremely well. I've used pgpool, Slony, and GridSQL myself. So what if they are 3rd party tools? They are solid and I have a choice of tools to match the right one for the job instead of one-size-fits all.

      Furthermore, PostgreSQL modelled itself around Oracle and DB2. If you developed something that worked well on PostgreSQL it was usually relatively painless to convert to DB2 or Oracle and the system would scream. But today, unless your dealing with databases in the Terabyte range, performance is good enough in PostgreSQL.

      The early versions of our product ran on MySQL because that was what was available on the servers at the time and we were on a shoestring budget and had to use what was there. As our product grew, we encountered problems with data corruption on MySQL, found that MySQL's DBCLUSTER engine was horribly buggy, and started to look towards alternatives when I suggested PostgreSQL. When it was announced Sun would buy MySQL, we made the switch that day. Since we were using abstraction to begin with, it just took a couple days to port the tables and then import the data from MySQL and we were done. Our plan was to use PostgreSQL until we could afford DB2 or Teradata.

      However, PostgreSQL has yet to crash or corrupt any data in 18 months. With GridSQL we have HA with shared nothing architechure and it seems to be able to handle hundreds to a couple thousand concurrent connections on $12k in hardware without a hiccup. In fact I have to remind our guys to do the routine maintence and preform checks otherwise we'd almost forget about it.

      --
      "The problem with socialism is eventually you run out of other people's money" - Thatcher.
    9. Re:It is not a ridiculous claim by _Sprocket_ · · Score: 1

      The slave morality of MySQL freeloaders is mind-boggling here! People who choose to devote their time and talent to developing free software are not your slaves! They have rights too, including the right to do what's in their own personal interest. Free / open source software is a natural consequence of free market competition, not government force!

      BSD is the most restrictive license a freedom-loving person should ever want to use. GPL is even more dependent on government force than proprietary software is, but usually doesn't come close to it in terms of quality or convenience.

      At first, I was in general agreement with what you were saying. Developers are affected by market forces and are free to take actions that benefit themselves as they desire. But then you dove right in to this freedom-is-tyranny anti-GPL litany. The mental gymnastics involved are what's mind-boggling here. It's rather amusing how BSD fanatics are using this case to push an agenda.

    10. Re:It is not a ridiculous claim by deniable · · Score: 1

      The other biggie was that MySQL had a native Windows version early, so that any aspiring web dev could practice on WAMP and then move to hosting which was usually LAMP. The hosting providers also played their part. Combine that with a lot of literature on MySQL, PHP etc. and you have the reason it succeeded for so long.

    11. Re:It is not a ridiculous claim by _Sprocket_ · · Score: 1

      It is the Copyleft movement's position that freedom (to fork open source code and do with it whatever you see fit) is "tyranny". This implies that me closed-sourcing my own work (and only my own work, since the upstream code I've copied from remains open-sourced) is somehow an act of aggression, which clearly it isn't. I am not your slave, and GPL is not a legitimate contract that can dictate what I can or cannot do with my own computer and my own ability to write software!

      You have the copyright of your own work. You are free to do with it what you want. You are not, however, free to do whatever you want with other people's work. Slave morality indeed.

      Copyleft is utterly impossible without government force, without which all Copyleft code would be simply liberated into the public domain - this is why you see people like RMS so fiercely opposed to (semi)libertarian movements like the Pirate Party. And, returning to the topic at hand, here we see the violence inherent in Copyleft philosophy surface once again, attempting to get in the way of what millions of Sun and Oracle shareholders want to do with their own property!

      Actually, RMS has stated that he generally supports movements like the Pirate Party. However, he cautions that such movements should level the ground for both Free Software and Proprietary Software, seeing the current activities of the Pirate Party tearing down the few restrictions of Free Software while leaving many additional restrictions of the Proprietary world intact. While I'm not a big fan of RMS himself, what you're portraying is misleading. You may not like the Free Software ideology but at least you can be accurate in your criticisms.

      Along those lines, I fail to see how you've managed to return to the topic at hand. There is no Copyleft philosophy getting in the way of Sun and Oracle. The GPL has little to do with Monty's fear mongering. But that doesn't stop BSD fanatics such as yourself from using his noise as a platform.

    12. Re:It is not a ridiculous claim by _Sprocket_ · · Score: 1

      RMS is a skilled manipulator. I guess you've read the same gnu.org page that I have read, but failed to see through the nuanced BS and recognize it for what it is: a defense "intellectual property" laws!

      I see where you're going with this, but sorry... I can't follow you. You're too keen to jump to your own conclusions and misrepresent what others have said.

      This isn't really about GPL vs BSD (I actually prefer public domain), this is about government force.

      No, this is about one man and a project he started. BSD fanatics have tacked on their agenda. And now you're tacking on your agenda.

      If you want to debate this further then please go to a more libertarian / Anarcho-Capitalist forum instead, where dissenting views are likely to be treated more substantively, and not stifled as they are here.

      Sorry - I have no interest in following you down that rabbit hole. While we may agree on some general principles, I find that you take far too many leaps for me to ultimately agree with anything I've seen you write to date. You'll have to be the martyr on your own time.

  21. Re:Because it's open source and they can't control by Anonymous Coward · · Score: 0

    For me it's like that: I have a goal that I see as the point of my existence. Big money does not help that goal. So no money in the world can change my goal. And nothing can stop me from pursuing it. Because that would be the end of existence.

    But they could buy you a prostitute.

  22. Join! by Goglu · · Score: 4, Funny

    Maybe, just to ensure that this can't happen, he should join the PostgreSQL project and become a top contributor...

    1. Re:Join! by BuGless · · Score: 1

      God forbid! The only thing putting my mind at ease here is that he'd probably never be able to achieve the code-quality standards that would allow him to contribute to PostgreSQL.

  23. Re:Because it's open source and they can't control by maxume · · Score: 0, Offtopic

    Do you mean to say that you do not chew gum on principle?

    And you claim that passing over $1,000 for this 'principle' was a good idea?

    Really?

    --
    Nerd rage is the funniest rage.
  24. EnterpriseDB by ascari · · Score: 2, Informative

    EnterpriseDB is a company that offers commercial support for PostgresQL. They have salaried people on staff that contribute to the project, much like IBM, RedHat etc. contribute to the Linux kernel. So I would say Monty's scenario is about as likely as Linux going away by Microsoft or Apple paying off the to 20 kernel developers. Some people just don't get how open source works.

  25. Yeah....right... by Jorl17 · · Score: 0

    ...and I'd be the the fallen madonna with the big boobies.

    --
    Have you heard about SoylentNews?
  26. I hope Oracle tries by Anonymous Coward · · Score: 1, Insightful

    If the top 20 developers are bought out for a good chunk of money, that will be a huge incentive for at least another 20000 developers to try to get the same amount... by developing PostgreSQL further. I hope Oracle does it. The development of PSQL will skyrocket overnight. BTW, MySQL is being forked too, but PSQL has a better license. MySQL is junk, always has been...

    My 2 cents on this non-story

    1. Re:I hope Oracle tries by turbidostato · · Score: 1

      "but PSQL has a better license."

      No, it hasn't. It has a better community model backing it up (an open one) which is what puts it in a better position despite its worse license.

      In other words: try to do KDE or Debian what was done to MySQL and see what happens.

    2. Re:I hope Oracle tries by timmarhy · · Score: 1

      wtf, how is the BSD license "worse"?

      --
      If you mod me down, I will become more powerful than you can imagine....
    3. Re:I hope Oracle tries by turbidostato · · Score: 1

      "wtf, how is the BSD license "worse"?"

      In exactly the same ways the parent post said it was "better".

    4. Re:I hope Oracle tries by ThePhilips · · Score: 2, Interesting

      Because it allows people behind pg to -on one side- give you for free a half-baked RDBMS but -on another side- ask money for the tools/etc to make it usable.

      That what BSD license allows. And in past it was practiced by PostgreSQL core team most of whom were employed by the company which was offering all the extras to PosgreSQL.

      But that is not per se BSD license weakness - it was pg business model in the past. It kind of feels f***ed up when somebody offers a patch but it gets rejected by pg core because it competes with their commercial offering.

      That is btw explanation why pg has much lower visibility compared to MySQL. MySQL was much more open and Monty/etc were investing their time to reimplement -instead of rejecting- into their proprietary fork what OSS community was contributing to GPL'ed MySQL.

      --
      All hope abandon ye who enter here.
    5. Re:I hope Oracle tries by turbidostato · · Score: 1

      "But that is not per se BSD license weakness"

      Quite to the point. Licenses are nothing but legal means to enforce an agenda. You can say how good is the license by how well it manages to push that given agenda. *If* your agenda is pushing for a community effort, both GPL and BSD allow for it *but* both of them have "holes" to counter such agenda.

      The "hole" in the GPL is the one Monty saw: instead of a community effort, let's control all development (open source with closed community): that way we'll be able to double-license (now that Monty doesn't control MySQL intellectual property he whines about how he is able to double license no more).

      The same goes with BSD, only it's even more obvious: you can get the codebase for free and use it as an starting point for your proprietary development (thus it can take years for PostgreSQL to get working replication out-of-the-box while there exists proprietary extensions for such a feature). This can obviously be exacerbated on a "closed community" environment where it's not only that the asked for feature is not developed but even rejected by the gurus.

      Two more things:

      1) The first "if" is a big one: in fact I don't think serious BSD adopters will accept it -they shouldn't choose such a license if they were in fact interested on an "open community" effort.

      2) GPL is more resistant towards the "open community" model: at the start BSD and GPL are in reality quite the same (look at the ton of "solo show" developments on, say, freshmeat, even under the GPL) but for succedding projects a point arises where like in a snowball rolling down a hill benefits become so great that even companies find compelling to "lend" a bit of their code in order to get the massive amount of codebase they earn in exchange (Linux kernel being the paramount example) where BSD doesn't have such a "breaking point".

      "MySQL was much more open and Monty/etc were investing their time to reimplement -instead of rejecting- into their proprietary fork what OSS community was contributing to GPL'ed MySQL."

      Not that I'm aware of an example of this. To my knowledge proprietary licensed MySQL has to-date not a single code line that it is not on the GPL'ed version. But they certainly asked for copyright cesion or wouldn't accept a third party patch. But if they found the feature to be of interest they certainly would reimplement it and make it avaliable under double license if only because it's easier to mantain the code base that way while, at the same time, it wouldn't degrade their bussiness case (companies looking for licensed products don't do it because of the codebase itself but for other bussiness -not technical, reasons). Again, BSD doesn't favour (while not impedes) such behaviour.

  27. PostgreSQL: a better (O)RDBMS w/ a better license by AlexLibman · · Score: 0

    And Monty Widenius is trying so hard to win the "communist software troll of the decade" award even Richard M. Stalinman would blush!

    What he's advocating is government tyranny against millions of Sun's and Oracle's shareholders, employees, customers, and other stakeholders, not to mention the European tax-victims who'll end up paying for a socialist software industry once they entirely succeed in destroying free market enterprise on that economically and demographically shrinking continent!

    Those people have a right to manage their property however they see fit - they are not the serfs of their government overlords, nor are they the slaves of MySQL freeloaders. Life doesn't owe anyone a free ride! Free / open source software should come about as the natural result of market competition, not government force!

    (More about libertarian / Anarcho-Capitalist software philosophy here.)

  28. Re:Signature trolling by Anonymous Coward · · Score: 0

    -1, Offtopic

    -1, Wrong

    STFU

  29. Monty Needs To STFU by Anonymous Coward · · Score: 0

    Monty. You seriously need to take your money you made from us and just Shut The Fuck Up.

  30. Mexico City vehicle database by mapuche · · Score: 1

    Back in 1998 we developed a system to manage the vehicle and drivers license database for Mexico City, all done with Perl, TK and PostgreSQL. We faced the problem with the 2GB limit size of tables, can't remember the solution.

    1. Re:Mexico City vehicle database by Pathwalker · · Score: 1

      The solution was to just keep writing data; the 2GB limit was on a single table file. When the amount of data exceeded 2GB, it would just create another file.

  31. Re:Because it's open source and they can't control by icebraining · · Score: 1

    If not chewing gum is one of your principles, you've got some issues.

  32. The strategic effect by Anonymous Coward · · Score: 0

    I wouldn't exactly feel discouraged to contribute to PostgreSQL if I know that Oracle kept paying the top 20 developers, especially if I knew that they payed enough to keep me away forever.

  33. Wrong by microbox · · Score: 1, Informative

    He sold MySQL to Sun and then left Sun.

    That is factually inaccurate. He was informed that the sale had taken place once it was done. The mistake Monty made was to sell MySQL to shareholders years ago. It probably wasn't a mistake either, although there should have been a clause in the shareholder agreement about the resale of MySQL.

    --

    Like all pain, suffering is a signal that something isn't right
    1. Re:Wrong by Ebbesen · · Score: 1

      Exactly how many shareholders/VCs would be interested in buying stock in a company, if there's a clause that prohibit them from selling to the highest bidder whenever they see fit?

    2. Re:Wrong by StubNewellsFarm · · Score: 1

      It is not at all unusual for a minority shareholder (especially a founder of the company) to retain approval over sales, even after VC investment.

    3. Re:Wrong by TooMuchToDo · · Score: 1

      Note how many folks own Google stock, yet they're buying class B shares with no rights, while all the top folks have class A shares with voting power. Not that I think there's anything wrong with that, I'm just saying it happens all the time.

    4. Re:Wrong by HornWumpus · · Score: 1

      Right of first refusal is not the same as approval.

      Right of first refusal is not unusual, it is unusual for the founder to have the funds to buy the shares.

      Approval of sales would drive away investments unless it was for a very short time frame.

      --
      John McAfee 'It was like that time I hired that Bangkok prostitute; to do my taxes, while I fucked my accountant'
  34. All 20 ? by daveime · · Score: 1

    according to Monty Widenius. He fears that Oracle, or someone else, can easily squash PostgreSQL by just 'buying out' the top 20 developers

    Or in MySQL's case, just one ... right, Monty ?

  35. Open offer to Oracle by ClosedSource · · Score: 1

    For $1 billion I'll become a PostgreSQL developer and then agree to stop developing for it.

    1. Re:Open offer to Oracle by Stratoukos · · Score: 1

      $1 billion?? Give my 100 bucks and I'm your man.

      --
      It may be 7 digits, but at least it's a semiprime
  36. Re:Signature trolling by Anonymous Coward · · Score: 0

    Yes - by all means, we should just cow down to tyranny. That's what everyone's done in the past and it worked out well. There's no such thing as a successful revolt in history. Also - gun rights are directly linked to foreign policy.

    Thanks for clearing those things up for us.

  37. Stallman also challenges Widenius by toby · · Score: 4, Informative

    Richard Stallman has clarified that he believes the GPL is necessary and sufficient protection for MySQL, in direct contradiction to Widenius' call that the license should be changed and copyrights rest in some entity other than Oracle.

    Stallman: One thing that makes no sense at all is the idea of changing the license of MySQL to something non-copyleft. That would eliminate the possibility of selling exceptions, but allow all sorts of proprietary modified versions. Wherever MySQL should go, it isn't there.

    Eben Moglen and the Software Freedom Law Center defend the GPL even more strongly:

    "The GPL was designed specifically to ensure the permanent freedom of software, and the ability of everyone to improve and share their improvements to the program, no matter who acquires the copyrights to the code," Moglen said of the argument he presented to the Commission. "The whole point of GPL as a copyright license is to deal with every contingency that could result in hobbling or destroying the freedom of code shared under it. The drafters of GPL versions 2 and 3 considered scenarios very similar to the ones that the Commission is concerned about now. The design of the license, and the experience we have had using it, show that it can be counted upon to operate as intended in situations like this one."

    Programs released under the GPL, including Linux, Samba, and the GNU Compiler Collection, have continually proven to be resistant to anti-competitive conduct in the marketplace. "GPL’d programs competing effectively against offerings of the richest and most powerful monopoly in the history of information technology have resisted the efforts of the monopolist to find a chink in its armor," Moglen writes.

    --
    you had me at #!
  38. Some people don't do money for the money by weston · · Score: 4, Insightful

    Some people don't do it for the money. You can't buy them. Ever.

    I don't know. I mean, I know what you're talking about: I've turned down a well-paying job with equity that would have set me up pretty good because I felt there was something more important than the money.

    But here's the thing: at a certain level, once people offer you enough money (the mark starts somewhere around a million bucks) they're not just offering you money anymore, they're offering you freedom to do whatever you'd like to with your time. If the top 20 Postgres devs would rather do nothing else than work on Postgres, then you're right, this wouldn't happen. But if enough of them have other interests, then it's entirely possible someone could buy their non-participation -- with the ability to spend all the time they like on something else.

    1. Re:Some people don't do money for the money by TooMuchToDo · · Score: 1

      I think I'm going to turn that into a quote. "Anything below a million bucks is money. Anything above a million bucks is freedom."

  39. SQLite is for local storage by toby · · Score: 4, Informative

    It's not a multiuser database.

    A web site is a classic multiuser scenario for an RDBMS; you have to have concurrency issues completely nailed down (ideally with row level locking and ACID).

    It's also MySQL's sweet spot.

    --
    you had me at #!
    1. Re:SQLite is for local storage by Anonymous Coward · · Score: 1, Insightful

      I'm not sure that's such a problem. Trac use SQLite as the default database, so it must work well enough for them or they wouldn't do it.

    2. Re:SQLite is for local storage by Anonymous Coward · · Score: 0

      It might be MySQL's sweet spot if MySQL scaled well with large numbers of users. But it doesn't.

    3. Re:SQLite is for local storage by toby · · Score: 2, Informative

      Trac also allows other RDBMS back-ends. If you had a highly loaded site (for example, a popular public project) you would not pick SQLite for the reasons I mentioned. In particular, it does not implement MVCC or row locking. Locking is coarse grained (like MyISAM) which soon limits scalability.

      Yes, SQLite's basic locking is good enough for light demands (say internal company intranet), and I am happy to use Trac+SQLite myself in these situations. I suppose if you know your site won't ever be popular, and assuming you don't need any of the other features offered by the major systems, you could get away with it for the basic stuff gmack mentioned :)

      --
      you had me at #!
    4. Re:SQLite is for local storage by TheRaven64 · · Score: 3, Interesting

      SQLite is not a multi-user database, but a web app is a single user. It does support arbitrary numbers of concurrent reads and in relatively recent versions supports concurrent writes, although the locking is not quite row granularity. Most web apps are very read-heavy, and this is where SQLite shines. Consider something like Slashdot. Loading this page required me to read over a hundred comments from the db. Each of the times I expand a hidden comment, an AJAX request handler performs another db read. I only need to write to the db when I post something (well, there may be some logging stuff, but I'm still reading a lot more than I'm writing).

      For a lot of web sites, concurrent read speed is the bottleneck, and SQLite performs better than MySQL for concurrent reads by quite a large margin.

      --
      I am TheRaven on Soylent News
    5. Re:SQLite is for local storage by hey! · · Score: 1

      I suspect that's a case of shrewed analysis of their target market, not a technical endorsement of SQLite as an enterprise platform.

      Of course, you can architect around *anything*; ultimately when you build a reliably concurrent system it's on top of hardware which doesn't guarantee any logical consistency for your data when it manipulated concurrently. It's a matter of where in the software stack you make that magic happen. The database layer is very important, but there's more than one way to do it and they don't work equally well in every case. What works for a handful of developers posting a dozen or so updates to a bug database a day isn't going to work for a high volume, low latency commodities trading system.

      Choosing SQLite as a default makes lots of sense for a product like Trac because the vast majority of installations are probably small, low volume affairs without a lot of IT support bandwidth. Making them configure something like Oracle (which is on the other end of the feature and complexity scale) just to use Trac would more than double the effort needed to bring the system up. Many projects probably don't even have anybody who knows more than the most rudimentary thing about databases, and few have any real expertise in database administration.

      On the other end of the scale might be a project that has real need of high performance, ACID compliant database for their bug tracking. If there is such a project, they would have to hire a database admin anyway, who will be perfectly capable of configuring Trac to use whatever meets their needs -- if they are supporting an RDBMS in their product, it'd probably be whatever that is.

      So in the end, everyone can be happy with this choice of default, even people who don't use it. the majority of installations are spared the inconvenience of dealing with a platform that is overkill for their needs. The few installations that need more than that are free to use whatever they're familiar and comfortable with, knowing that the Trac folks are focused on making their product better, not support thousands of users who are over their heads with database administration.

      --
      Post may contain irony: discontinue use if experiencing mood swings, nausea or elevated blood pressure.
    6. Re:SQLite is for local storage by Anonymous Coward · · Score: 0

      At this time, SQLite is at least as multi-user as MyISAM. It certainly falls a long way behind InnoDB, but for most websites that's not a problem. With a read-mostly scenario like Slashdot/Wordpress/etc., you'll run into other problems long before you hit concurrency issues with SQLite.

    7. Re:SQLite is for local storage by Anonymous Coward · · Score: 0

      Consider something like Slashdot. Loading this page required me to read over a hundred comments from the db.

      Most likely the comments you see were loaded from cache since querying a database and generating the html for every request would require an insane amount of processing for a site like /.

    8. Re:SQLite is for local storage by Anonymous Coward · · Score: 0

      > SQLite is not a multi-user database, but a web app is a single user

      A TRIVIAL web app is single-writer. You could run a single blog on sqlite, you could not run slashdot or even reddit on it.

    9. Re:SQLite is for local storage by PCM2 · · Score: 0, Flamebait

      It might be MySQL's sweet spot if MySQL scaled well with large numbers of users. But it doesn't.

      Are you posting AC so nobody can see your seven-digit \. id?

      --
      Breakfast served all day!
    10. Re:SQLite is for local storage by r7 · · Score: 1

      It's not a multiuser database

      Nor do a large percentage of websites currently back-ended by relational dbs need to be. For sites that don't need persistence SQlite is a better choice.

      A web site is a classic multiuser scenario for an RDBMS

      When you're a hammer everything looks like a nail. Such is the rational for much bloated code and many unnecessarily dependency-laden systems and applications.

      It's also MySQL's sweet spot.

      And Postgres', and Oracle's, and ... One thing I like about MySQL is being able to pick and choose among different table types. Of course the downside is the default myisam's locking, and ability to become corrupt ("repair table" and "truncate table" are the MySQL admin's friends). But then innodb tables don't offer anything over PgSQL... So, if you like clean code and good documentation Postgres tends to be in the sweet spot. Also helps that it has far and away the best resistance to vendor lock-in.

    11. Re:SQLite is for local storage by leenks · · Score: 1

      That post wasn't me, but I don't get the fascination with ID numbers. I've been reading Slashdot almost since the beginning, but I didn't register for an account for several years. Why? I just wanted to read - I didn't see the point in me posting. If I'd registered back then I'd have an ID almost as low as yours, but as it is I'm stuck with this one.

      Anyway, why is a high user id considered "lame"?

    12. Re:SQLite is for local storage by PCM2 · · Score: 2, Interesting

      I don't know, but that also wasn't my point. My point was that he was claiming MySQL doesn't scale to a lot of users. Last I heard, Slashdot had a lot of users -- and it runs on MySQL.

      --
      Breakfast served all day!
    13. Re:SQLite is for local storage by greg1104 · · Score: 2, Insightful

      you have to have concurrency issues completely nailed down (ideally with row level locking and ACID).

      Even row-level locking ends up being a scalability issue eventually. This is why PostgreSQL uses MVCC for transaction isolation by default instead, which is one of the reasons it can scale upward well for some types of workloads.

    14. Re:SQLite is for local storage by dkf · · Score: 1

      SQLite is not a multi-user database, but a web app is a single user

      A TRIVIAL web app is single-writer. You could run a single blog on sqlite, you could not run slashdot or even reddit on it.

      [citation needed]

      Seriously, do you have any evidence for that assertion? In our testing we've found SQLite to be very fast indeed, and it's much easier to configure than a full DB server. (I also happen to know someone who's used it to replace Oracle in a production deployment; he just wrote the network wrappers to turn it into a remote-accessible database server. I think this guy is a little crazy, but it's definitely amusing that it was possible at all.)

      --
      "Little does he know, but there is no 'I' in 'Idiot'!"
    15. Re:SQLite is for local storage by jadavis · · Score: 1

      Most web apps are very read-heavy, and this is where SQLite shines.

      Saying that SQLite is good at reads is misleading. It may be good at very narrow read cases, such as fetching a record given the primary key, but beyond that it can't do much. For instance, it can't even do a hash join or merge join (it doesn't have a planner, so how would it know when to do it?), so it's going to be much slower for a lot of queries. To be fair though, MySQL can't, either.

      --
      Social scientists are inspired by theories; scientists are humbled by facts.
    16. Re:SQLite is for local storage by gmack · · Score: 1

      It's also MySQL's sweet spot.

      And Postgres', and Oracle's, and ... One thing I like about MySQL is being able to pick and choose among different table types. Of course the downside is the default myisam's locking, and ability to become corrupt ("repair table" and "truncate table" are the MySQL admin's friends). But then innodb tables don't offer anything over PgSQL... So, if you like clean code and good documentation Postgres tends to be in the sweet spot. Also helps that it has far and away the best resistance to vendor lock-in.

      It is MySQL's sweet spot because that's what MySQL did better than anyone else: Fast reads.
      It did reads faster than pretty much everyone out there including PostgreSQL and Oracle.

      Mind you things have changed in the past decade.

    17. Re:SQLite is for local storage by dave87656 · · Score: 1

      The MySQL site references that fact. They also mention that InnoDB has been very useful to /. but the don't actually claim to be using it for the high load stuff. (http://www.mysql.com/news-and-events/generate-article.php?type=ss&id=slashdot).

      I'm guessing /. uses MyISAM tables and table level locking. Does anyone have more information on this?

  40. I had the privilege... by Toze · · Score: 5, Insightful
    of speaking with Monty on freenode's mysql channel, when he responded to my suggestion that he needed a helmet and a big cup of STFU. I asked him about forking and MariaDB, and he had pretty much the same response as in the blog linked above. The way he talked about open source, though, it was like he thought it was impossible for a large open-source project to succeed without a strong leader. He expressed little trust in the community, and no faith that an abandoned project could be picked up again. When I asked him about developers scratching itches, and solutions drawing users and more developers, he didn't seem to think it was a feasible solution. He kept defending his posts about Oracle as being about "for the users," and his motivation being to maintain choices.

    I think the problem is less about Monty wailing about Oracle's calumny, and more about Monty's view of how FOSS works. He seems to think it needs heroes, and that the rest of us plebes need someone to follow before we can get anything useful done. I'll agree with him that projects need leadership, but like comments above have said, there's a difference between project leadership and making yourself indispensable. If Monty was indispensable when he left MySQL, then he was the one that killed it, not Sun, and not Oracle.

    --
    No OS on the planet can protect itself from a user with the admin password. - Yvan256
    1. Re:I had the privilege... by WindBourne · · Score: 1

      I note that you say privilege, not pleasure.

      Monty needs that cup.

      --
      I prefer the "u" in honour as it seems to be missing these days.
    2. Re:I had the privilege... by bill_mcgonigle · · Score: 1

      He seems to think it needs heroes, and that the rest of us plebes need someone to follow before we can get anything useful done.

      Ah, and so if he filed that role in early MySQL, then he's a hero.

      Interesting insight - I guess some people need to have something to delude their time after they've sold out.

      Folks like Woz spend it volunteering at schools, perhaps others should magnanimously follow suit.

      --
      My God, it's Full of Source!
      OUTSIDE_IP=$(dig +short my.ip @outsideip.net)
    3. Re:I had the privilege... by Jorl17 · · Score: 0
      It is true to some degree that a large open-source project cannot be held without a leader. Because the purpose of a leader is not only that of motivating, but also that of guiding the members of the group. If there is no Leader, and I'm talking about a good leader with decent leadership skills (be those whatever you wish), there can be no direction to follow. This leads to:
      1. Excessive group "conformism". That is: people will always be in agreement because they will most likely create internal and implicit leaders, yet being afraid to expose their opinions, even if done unconsciously -- this is common in group development, and it may be surpassed later on.
      2. An elevated degree of entropy, meaning that everyone will have different opinions and will not find a way to work towards a goal together, thus failing to produce any important outcome.

      Sure, like I mentioned, there are *implicit* leaders, but without the sense of a hierarchy. But we need hierarchy, to create different types of authority, so that we can moderate our behaviour and even sacrifice ourselves for the well-being of the group as a whole. Sure we can also do that to cover our ass and prevent getting thrown out of a project/job, but that is effectively positive for the group.
      Look at most big open-source projects, they rely on a well-defined leader, or set of leaders disposed in a hierarchical way. Heck, dump open-source projects and look at the real world, they fail without proper leadership, because a leader must motivate, direct towards a goal, sort out problems, among other things.

      This does not mean that we need this particular leader!

      --
      Have you heard about SoylentNews?
  41. Re:Signature trolling by Anonymous Coward · · Score: 0

    Ha, it even says "trolling" in the subject and slashtards are so goddamn stupid they bite on it anyway.

  42. I doubt that oracle will do that by WindBourne · · Score: 2, Interesting

    If so, I suspect that the psql team will nullify a number of those patents with prior art. Long before Oracle 9/10's move into OO, Postgres was there.

    Also, once Oracle creates that kind of ill will, how fast will MS move MS-SQL to Linux/Unix? It would happen within 3 months. They would KILL to have all those OSS coders switch DBs.

    Finally, Oracle will not go after Postgres with patents. Right now, postgres has many similarities to Oracle. As such, it is increasingly being used for lower end work, and then projects move to Oracle. Basically, Oracle sees it as a feeder project. Personally, I would stick with Postgres for all bu the top demand projects.

    --
    I prefer the "u" in honour as it seems to be missing these days.
    1. Re:I doubt that oracle will do that by Lonewolf666 · · Score: 1

      Also, once Oracle creates that kind of ill will, how fast will MS move MS-SQL to Linux/Unix? It would happen within 3 months. They would KILL to have all those OSS coders switch DBs.

      I have my doubts about that, because it would also make it easier for MS-SQL users to switch to Linux.
      My impression of Microsoft is that they really want to keep their customers on the combination of Windows/MS Office/SQL Server. Anything that makes it easier to "unbundle" those is probably seen as a threat by MS.

      --
      C - the footgun of programming languages
  43. differences by brennz · · Score: 1

    Postgresql has a more robust, decentralized community of ISVs and developers than did MysqlAB. The BSD license contributes to this loose federation of collective developers because no one company runs the show.

    Furthermore, the folks in #postgresql on irc.freenode.net are superb. David Fetter is the man!

    1. Re:differences by slick_rick · · Score: 1

      The postgres community definitely rocks, both on IRC and the mailing lists. That is the major reason my company uses it pretty much exclusively anymore, because we feel confident that whatever problems we run into we can work through.

      BTW, David Fetter is in this thread, just look for dfetter with the four digit /. ID with the highly rated post...

      --
      apt-get install redhat please god - Me (take it easy, I love Debian)
  44. Monty: Biased and not open for reason by Anonymous Coward · · Score: 0

    Ever since this Monty thing started a lot of people started to bash all of his efforts with a mere comment "You sold out and now you want the glory back". I for one think thats a pretty lame comment which is probably only fed with envy. Note that I'm stating that it would be untrue or anything; just unfair since its the most obvious and easiest comment to make.

    I've been spammed by Monty last year when he started his "Save MySQL" rampage and the one thing I consider highly dubious are the reactions he seemingly gets to his efforts. Note how almost any comment on his blog is positive about the way things are going and how people welcome to see him put some effort into all this? Only one reaction shows a small sign of certain doubts but thats it.

    Well, I think that is something you can take into account. When I got his e-mail on my company e-mail address (which I've used to respond to a MySQL mailinglist years ago) I looked over the website, read his blog and then wrote a comment that I didn't agree with the way he handled his action, that I didn't like to be spammed in the way he did and quite frankly that it sounded odd coming from someone who set the whole thing into motion in the first place.

    Not talking about money, fame and fortune here mind you. If he wanted some kind of security or insurance for the future of MySQL he should have included that right into the negotiations when he sold MySQL to Sun. Something in the likes of "In case of bankruptcy or take over the rights go back to the original owner", I don't know.. Point being: he should have thought about all this before he sold out to Sun.

    So IMO this whole action of his only shows us how utterly narrow minded and clueless he is. Do we really want someone like that to re-gain control over how MySQL is going ?

    This isn't about money or fame or envy. Its a question about (lack of) integrity, insights, honesty and some simple common sense. I think you'll find those qualifications lacking with Monty, and thats the only thing I'll hold against him. Not "he sold out". Who cares? Can you honestly say you wouldn't have done so? I don't.. The only thing I can say is that I'd have done it differently.

    So... Can we now please move on and simply ignore whatever else is coming out of Monty's mouth?

    1. Re:Monty: Biased and not open for reason by NormalVisual · · Score: 2, Insightful

      From my perspective, it's not about "selling out". Given the offer of that kind of money, I'd have had tar'd the repo up and personally delivered it to Sun within the hour in a set of gilded DVD cases, and I won't begrudge anyone that same choice either. What *is* annoying is the whole "I want to eat my cake and have it too" whining that Monty has been expressing through this whole thing.

      --
      Please stand clear of the doors, por favor mantenganse alejado de las puertas
  45. Monty's just a greedy troll ... by tomhudson · · Score: 2, Insightful

    can easily squash PostgreSQL by just 'buying out' the top 20 developers

    ... like Sun quashed MySQL when Monty "sold out" ... oh, wait, it's still around ...

    what a troll - and that was lying about what Stallman said

    Can we get him put on some terr'rist list or something?

  46. What Monty should do by Anonymous Coward · · Score: 0

    Monty can cry all he wants about Mysql, he is never getting back control of it. He should sponsor a fork of Postgre, which has a BSD license and would let him resell or modify it to his liking. He could even make another dual source license I'm guessing. He could probably start this tomorrow if he wished, it seems the real problem for him would be gaining the trust of open source developers after the Mysql situation.

  47. What I don't understand is... by pngwen · · Score: 1

    ...why this is such an issue. I know that MySQL is distributed (at least to some) under the terms of the GPL. I have received it only under GPL2, and never under their proprietary license.

    The GPL has been applied to the MySQL code, and it cannot under any circumstances be removed. Sure Oracle could absorb whatever code they wanted into any proprietary product, but I still have GPL code, we all still have the original.

    Development could continue in the community, we can still enjoy the benefit of the MySQL database with or without oracle's blessing. In short, this a non-issue because we will always have the database code as it is now.

    The fact that Monty is a prick and a sellout makes no difference either. PostgreSQL won't be sold out, and even if it was, we would still have the GPL'd versions to fork from. That's what the GPL is supposed to do. It is there to protect us from the Monty Wideniuses of the world!

    --
    I am the penguin that codes in the night.
    1. Re:What I don't understand is... by mark-t · · Score: 1

      PostgreSQL isn't GPL, it's BSD.

    2. Re:What I don't understand is... by Anonymous Coward · · Score: 0

      Ignore him, not all the Koolaid drinkers have Macs.

    3. Re:What I don't understand is... by pngwen · · Score: 1

      Whoops, you are correct. Still the fact remains, PostgreSQL can be sold, but there is still the BSD version of the code sitting out there.

      --
      I am the penguin that codes in the night.
    4. Re:What I don't understand is... by Anonymous Coward · · Score: 0

      FYI, Pgsql is BSD licensed.

  48. Re:Because it's open source and they can't control by Ant+P. · · Score: 1

    He'll just have to kick ass instead.

  49. Truth is that Postgress Rocks, dual licenses sucks by viraltus · · Score: 1

    That's the problem dual licensing has; you never know what to expect from the onwer, and that is why is has to be avoided when truly free projects are out there... same goes to KDE/Qt.

    --
    Dear /. CENSORS that set people's Karma to Neutral when you disagree with them: FUCK YOU!!
  50. The PostgreSQL project already ran that gauntlet by EbNo · · Score: 5, Interesting

    I once worked for a company called Great Bridge, which attempted to make money selling a boxed version of PostgreSQL. We employed/contracted with several key PostgreSQL developers, and I distinctly remember discussions with management and at least one of those developers about this very topic. The developers had agreed amongst themselves and with Great Bridge management to limit the number of key committers who took money from Great Bridge in order to ensure the company didn't exert too much control over the project (I'm sure we would have been happy to have every one of them on the payroll). History proves Monty wrong on this one.

  51. Oh yeah... by Sfing_ter · · Score: 1

    Yeah... keep telling yourself that...

    --
    A computer once beat me at chess, but it was no match for me at kick boxing. Emo Philips
  52. rather uninformed, you are. by unity100 · · Score: 1

    that bug in the ambler of simpler times is powering millions of sites servicing hundreds of millions of internet users worldwide. ranging from forums to portals, shopping sites to collaboration sites.

    for hosting market LAMP hosting with cpanel is THE way to go. it is expected default server config. even the big players are offering lamp packages foremost, because request for other packages are nil, the only exception being a very tiny percentage of asp and mssql hosting. its to the extent that new startups are not even bothering with offering anything aside LAMP.

  53. Widenius - What is his game? by walterbyrd · · Score: 1

    Why is he all in a wad over this? He alleged concerns make no sense when his past actions are taken into account - unless he has some hidden agenda. He sees no problem with selling mysql to Sun, and then has a hissy fit about mysql being sold to oracle. Something is not adding up.

    Some have suggested that he wants to double-dip. How would he do this? And why would mysql being sold to oracle make any difference?

    His present hysteria about the future of postgresql does not make sense to me either. Is there not always the possibility of top FOSS developers being bought out, regardless of who owns mysql? I mean if you want to get all hysterical about improbable "what if" scenarios, then what if some company bought the top postgresql developers, and top mysql developers?

    I'm just trying to understand this.

  54. Desperate campaign by Anonymous Coward · · Score: 0

    Monty is a joke, fraudster or desperate, and we should not let people like him get too much space. Look at what he writes:

    "Q: Are MySQL and Oracle really competing products? A: Yes. To be fair, they don't compete for all applications and it's in many cases prohibitively expensive, risky and time-consuming to migrate an old Oracle application to work on MySQL.[...]"

    I would say that this is the understatement of the year (and it is just the beginning of January). To be REALLY fair, they don't compete for MANY applications at all, considering the whole spectrum of applications relying on a (R)DBMs. His comparing MySQL to Oracle is plain stupidity and shows that he either is ignorant, uneducated or just trying to fool gullible people. He should feel ashamed. It puts his whole campaign in ridicule to people that knows more than the masses he so desperately tries to control.

    I had to suppress my laughter when I read his claim that PostgreSQL isn't an alternative to MySQL (but apparently Oracle was!). The three reasons were 1) different feature sets and support from various applications 2) no single strong company backing it, and 3) the PostgreSQL market is also dominated by Enterprise DB

    The first part of claim one (feature sets) are pure bs. PostgreSQL is closer to Oracle RDBMs that any current incarnation of MySQL. Thus if he considers MySQL and Oracle in the same league, by his method reasoning, PostgreSQL is too (I disagree, I consider Oracle to be in an entirely different playground). Claim 2 and 3 clashes somewhat and claim 2 is also plain stupid.

    HOW MANY users actually USES the support and backing of the commercial MySQL (not given away freely) and how many turn to the community for free support (something PostgreSQL also provides through its community). I am willing to bet huge on that the vast majority of MySQL installations out there NEVER has been in contact with the commercial MySQL-support and never will... ever. Period.

    So I call on Montys claims and say that it is a lot of FUD from someone playing people for his own personal agenda. He has delusions of grandeur and wants to make himself more important than he is.

    I would be sorry if Oracle killed off MySQL since I use it in some projects where I am prohibited from using a more competent DBMs. But hearing these biased rants week after week makes me want to start a counter-campaign to Montys just for the sake of it.

    1. Re:Desperate campaign by Anonymous Coward · · Score: 0

      So I call on Montys claims and say that it is a lot of FUD from someone playing people for his own personal agenda. He has delusions of grandeur and wants to make himself more important than he was.

      Fixed that for you.

  55. This is like bad chess. by hey! · · Score: 1

    You know, the kind that plans gambits with the assumption the opposition isn't paying attention to what you're up to.

    Suppose Oracle decides to kill PostGres by hiring *all* of the top developers. Getting 40% or 50% of them is probably feasible at a reasonable price, but not the nail-in-the-coffin Evil Ellison is looking for. He needs 100% of the key developers or as-near-as-dammit. The closer you need to get to 100%, the higher the cost goes, and it's not linear.

    It'd be easy to hire four or five of the top 20, but to get sixteen or seventeen you'd have to make the offer so amazingly good that only a fool would refuse. How much would that cost? A cool million apiece?

    Here's the flaw. Let's say I'm a competitor, and I see that Oracle has just dropped twenty or thirty million to get these exact persons on the team. But there are lots of good programmers in the world. I could hire some darn good ones with a hiring bonus of, say, a hundred thousand plus a good salary and a chance to work on an interesting, high profile project. So after Oracle spends its twenty, I spend two million and replace the lost talent with equally good talent.

    Why?

    Because it's a serious setback Oracle's plan to become the de facto owner of database technology. Well worth it, to me, even if I compete *myself* against Postgres. Also, because it socks Oracle where it lives -- in the cash flow. That could hurt it in other ways. We could have management turnover, maybe even a purge at Oracle for doing something so stupid with twenty million bucks. Cue the "Mwa-ha-ha-ha" in my boardroom. And once Oracle gives up, I *still* have these twenty top notch systems programmers I can use on any mf my projects.

    --
    Post may contain irony: discontinue use if experiencing mood swings, nausea or elevated blood pressure.
  56. I see his point re buy-out by stimpleton · · Score: 1

    The 2nd Iraq invasion changed my view about the world.

    As we know, the initial success of the invasion wasn't due to military excellence such as the African Desert Tank Battles between General Mongomery and the German Panzer Divisions.

    It was due to middle ranked officers - tank commander, platoon leaders being paid money by the US Govt, CIA. When they didnt show up to work on the specified day, the ordinary soldier fled.

    In this case Monty is right, its not hard, for orgs with the know-how and resources to de-rail something. Money talks.

    --

    In post Patriot Act America, the library books scan you.
  57. doesn't ACID cost money in mysql? by bigtrike · · Score: 1

    Aren't you supposed to buy a license for InnoDB in order to get ACID in MySQL? Last time I checked, ACID was mutually exclusive with fulltext indexing as well. Postgresql is far better for a medium sized to large website, as it doesn't have any of these issues and also supports MVCC, which results in much less waiting than with row level locks.

    1. Re:doesn't ACID cost money in mysql? by Anonymous Coward · · Score: 0

      License for InnoDB? It comes in the default install.

    2. Re:doesn't ACID cost money in mysql? by tepples · · Score: 1

      Last time I checked, ACID was mutually exclusive with fulltext indexing as well.

      For a lot of applications, you don't need ACID for the index. That's why you index a periodic snapshot.

  58. shark alert by rp · · Score: 1

    IMO /. has justed the shark with this "story". Thank you for no longer wasting my time.

  59. Re: Yep, I don't know why people forget about it. by HiThere · · Score: 3, Interesting

    Every time I've gone looking for information on how to use FireBird with my favourite language (which changes frequently) I've come away unsatisfied. So I've gone with something that was easier to figure out how to use.

    That's a part of why FireBird gets ignored. It was sort of like what Linux was in the late 90's. Probably quite capable, but the documentation seemed to assume that you knew someone to coach you over the undocumented spots. Or that you were familiar with something sufficiently similar. Over the last decade Linux has backfilled, but FireBird hasn't. In fact it seems to have retrogressed, just based upon the last time I considered using it. (I didn't want to use SQLite because I wanted a system that let me use integer keys, and the SQLite interface to the language I was then using didn't. But I wanted a DB that would allow me to pick the file I was using as my database and store it locally with the program. FireBird would seem to have been ideal...but I couldn't easily figure out hot to use it, so I used something else. [I think that time I packed the integers into byte strings with each byte using only 7 bits.])

    --

    I think we've pushed this "anyone can grow up to be president" thing too far.
  60. Whatever! by Blakey+Rat · · Score: 2, Funny

    Whatever!

    The point is received gobs of money and now he's whining like a toddler. I think everybody's fucking sick of it by now.

    If he signed a bad deal, THAT IS HIS FAULT AND HE SHOULD FUCKING COPE WITH IT LIKE AN ADULT! And stop spamming up this, and other, forums with his bullshit whining.

  61. Re:Because it's open source and they can't control by jeremyp · · Score: 1

    DUH!

    Some people don't do it for the money. You can't buy them. Ever.

    For me it's like that: I have a goal that I see as the point of my existence.

    Yes, well these people would be being paid to give up working on a database server. If your goal in life is to work on a database server, you probably need to get out more.

    --
    All I want is a secure system where it's easy to do anything I want. Is that too much to ask ~~ Randall Munroe
  62. a web *site* is multi-user. by toby · · Score: 1

    Do you have actual benchmarks showing SQLite outperforming MyISAM on reads? This might be surprising news to the sites which are using MySQL at large scale. I would repeat: SQLite won't scale.

    (Benchmarks against InnoDB wouldn't be relevant of course, as InnoDB is an ACID, MVCC engine.)

    --
    you had me at #!
  63. Re:Truth is that Postgress Rocks, dual licenses su by ultrabot · · Score: 1

    KDE & QT are under LGPL, which, unlike GPL, avoid this vulnerability. The only reason for getting a commercial license for otherwise LGPL'd software is that either 1) you need static linking or 2) you need to make secret modifications to the library.

    --
    Save your wrists today - switch to Dvorak
  64. My guess is by toby · · Score: 1

    Mr Widenius wants to be the EnterpriseDB in the MySQL milieu. He already has salaried developers working on MariaDB, for Monty Program AB. If his wish for MySQL to be relicensed under "a more permissive Open Source license" were granted, he's promised that MPAB would only add "BSD" code to MariaDB, but he could have other companies on the side doing closed enhancement too. In fact he has not explained any other way that MPAB can stay in business.

    --
    you had me at #!
  65. Access + SQL Server Express by tepples · · Score: 1

    Access is a front-end to Microsoft SQL Server Express and Microsoft SQL Server. In a lot of cases, SQL Server Express ($0) is more than enough to run a business and is a nice step up from the Jet engine built into Access.

  66. I wonder why MySQL is even considered by melted · · Score: 1

    I wonder why MySQL is even considered as an option these days. Honest question -- I don't have much experience with it. I just tried to port my DB schema a couple of years back to it (from MS SQL) and run a couple of queries and it showed ridiculously poor performance on complex joins, so I went with Postgres instead. Postgres has been great.

    Is there a good technical reason why people choose MySQL over Postgres?

    1. Re:I wonder why MySQL is even considered by Anonymous Coward · · Score: 0

      no

  67. new developers by Anonymous Coward · · Score: 0

    10 PRINT "A big payout encourages the next 20 top developers to get up to speed quickly in the hope of yet another payout"
    20 PRINT "Big corp buys out developers"
    30 GOTO 10

    I miss my TRS-80 and the cassette recorder.....

  68. postgresql = awesomeness by timmarhy · · Score: 1
    even though i now work with sql server, i did work with postgresql for 2 years solid prior. it's a kick arse DB, containing so many features it was ms sql's equal even back then. while not as speedy out of the box as sql server or oracle in some instances, it wasn't far behind either and the price was certainly right with a great support community.

    monty's just an idiot, he sold mysql and now whinges about it.

    --
    If you mod me down, I will become more powerful than you can imagine....
  69. Obligatory Krusty the Clown quote: by Anonymous Coward · · Score: 0

    Hey, they backed a dump truck full of money up to my house! I'm not made of stone!

  70. I would switch to postgresSQL in a heartbeat by Hohlraum · · Score: 1

    if it was as easy to setup and maintain as MySQL. I have too much other stuff to do already. :/ From what I can see MySQL has much better maint tools as well.

    1. Re:I would switch to postgresSQL in a heartbeat by MadCat · · Score: 2, Informative

      It is in fact easy to set up and maintain -- it just requires a bit more thinking, mostly to get the authentication and such things working right, but that's a matter of editing a config file. Maintenance wise, PostgreSQL doesn't need much of that, the occasional vacuum and that's it. With auto-vacuum enabled, even that is taken care of.

      I used MySQL a lot in the past, and ended up going to PostgreSQL around version 7.3, because I needed the triggers and the views. Never looked back to MySQL, PG might be slower at certain things, but at least I don't end up getting a call at 3am in the morning in the weekend informing me the database crapped itself up again, only to have to wait for myisamchk to go through near 20Gb of data.

      Give it a shot and you will be enlightened :)

      --
      There is no sig...
    2. Re:I would switch to postgresSQL in a heartbeat by Anonymous Coward · · Score: 0

      PostgreSQL's bigegst criticism was that it is slower than Mysql. This is no longer true, the most recent release (8.4.2) was faster than latest MySQL in our test, by a small 5% margin. There is no reason to use mysql anymore if you ask me. Anyone starting a fresh project should use Postgresql. Great database, very reliable. Haven't had an issue since it was set up, and will probably not have any issue for many years.

  71. Due to the magic of shareholding, by toby · · Score: 1

    "all of the original founders of MySQL got collectively less than 12 % of the Sun deal". This meant EUR 16 million to Widenius personally last year according to his Wikipedia page. So buying it back is out of the question (even if the owner wanted to sell it) - and no billionaires were made in the deal.

    --
    you had me at #!
    1. Re:Due to the magic of shareholding, by hairyfeet · · Score: 1

      So that gives him the right to whine to mommy government (The EU) to give him his toys back? What happened to /. being a libertarian haven? I personally don't care if he sold his company for a dollar. It was his company, he built it, he sold it, and that is where his say should end.

      To use a Slashdot car analogy, I don't get to sell my car to you, make a nice profit, then go screaming to mommy government because you decided to sell the car because "Wahhh I wanted to turn it into a taxi for free! Wahhh!".

      The ONLY reason why Monty wants the EU to step in and force Oracle to release MySQL under a "more liberal" (his words) BSD license is so HE can lock it back up in a nice proprietary package with his new product, MariaDB, which he can't do now because he doesn't have the right under the GPL to wall it back up like he did when he had MySQL dual licensed. So I'm sorry Monty fans, but the guy is just acting like a complete ass.

      --
      ACs don't waste your time replying, your posts are never seen by me.
    2. Re:Due to the magic of shareholding, by toby · · Score: 1

      that gives him the right to whine to mommy government (The EU) to give him his toys back

      I don't think so. While not a libertarian, I don't see that this outcome is either within the EU's power or within the bounds of probability.

      From the irrational tenacity with which Widenius has stuck to his contrarian position, one could easily infer greed - as many observers have done, projecting their own materialism - but I would prefer to blame it on an emotional cocktail:

      • shock/surprise at the Sun sale to Oracle
      • regret over past decisions including a sense of having betrayed his lieutenants (some of whom are now the core MPAB team)
      • FUD over the product's future (such fears being externalised and made contagious by the blog, petition, and campaign)
      • inability to reorganise/regroup and imagine a future without controlling the product
      • delusive manifestation of the above in handwringing concern for the "community". (Such concern, not to mention lack of faith, is flatly contradicted by his licensing position.)

      Some of these seem to be long-held personal positions (fear/distrust/competiveness with Oracle, dislike/distrust of GPL) which are now getting a comprehensive platform in the campaign.

      --
      you had me at #!
    3. Re:Due to the magic of shareholding, by hairyfeet · · Score: 1

      Actually I think ultimately it comes down to something even more basic than greed: control. Monty liked being able to play "GPL" while still being able to lock up MySQL with a dual license scheme, and now he actually has to play by the same rules the rest of us do! The horror! If you read any of his posts you'll see him slip "newspeak" trying to make it sound like he is "for the community" while at the same time pushing for a BSD license, which we all know is mainly advantageous for those that want to lock up free code in a proprietary app.

      When he owned MySQL thanks to dual licensing Monty could have his cake and eat it too, and now he can't. He has to follow the GPL just like any other company and he HATES it! But I'm sorry Monty, but you gave up that right when you cashed the check from Sun. If he wants that kind of power again he is gonna have to start a new DB project and hope he can con folks into donating code to it like they did MySQL. Frankly I don't think it will work, and Monty is finding out he burned too many bridges when he sold MySQL to pull it off again, hence the whining to mommy EU. And while I agree that ultimately the EU can't do squat, Sun was losing...what? 100 million a day or something while the deal was held up? So even if the EU shuts up the damage has already been done, and from what I have seen a lot of the FUD being spewed comes back to old Monty.

      So I'm sorry to say this to the Monty fans out there, but he is an ass. if he didn't want to give up control he shouldn't have cashed the check, and now he is just stirring up FUD and costing Sun money for what in the end will be nothing. Stupid, wasteful, and pointless.

      --
      ACs don't waste your time replying, your posts are never seen by me.
    4. Re:Due to the magic of shareholding, by toby · · Score: 1

      Yes, control was my fourth point, but I agree it is probably the most important.

      Monty Program AB requires a contributor agreement essentially the same as Sun's SCA. Since MySQL developers have either already made peace with the SCA, are part of the MPAB camp, or simply trust Widenius implicitly (he does, after all, have fame and money, which some people find automatically persuasive), I don't think copyright assignment will be a major sticking point.

      People tend to fall into one of the "OMG the sky is falling, stand behind Widenius", or "copyright assignment/dual licensing is broken" camps.

      But why put effort into MariaDB, or stake one's job security on it, when Widenius openly argues it is not sustainable? (At a claimed burn rate of EUR 100,000 per month, his windfall isn't going to last long.) He may have to face the fact that it is wishful thinking to feed a family of developers forever who produce only "BSD code".

      On this point, perhaps we have to agree; as an outsider, he may not be able to continue without sponsorship. But this has been true since Sun's takeover. It seems as if he looks at MPAB's bleak future and concludes the community has no future either. I can see why developers such as Paul McCullagh (PBXT) might be persuaded here. Yet the case is far from cut and dried: PBXT is a significant value add to MySQL, no matter who owns the copyrights, and it's not a given that Oracle will simply ignore these significant projects.

      In any case Widenius seems to need a third way: Letting go, abandoning his cherished business model, eating ramen for a while while he designs a new "MySQL killer" (yeah, I know, there's Drizzle already), or hiring a great salesman to solicit the necessary corporate sponsorship of his ready-made MariaDB development dream team, GPL notwithstanding. MPAB has attracted a terrific bundle of ex-MySQL talent.

      I'm no MBA or businessman, but waiting for the EU to drop a BSD-ish license in his lap seems like a weak gamble for everyone involved.

      --
      you had me at #!
  72. Who are you? by anti-NAT · · Score: 1

    And why do you think you wield such power to make heads role? What "community" do you lead? Why are you hiding behind a pseudonym of "unity100" when you're supposedly well known?

    --
    The Internet's nature is peer to peer - 20050301_cs_profs.pdf
  73. Re: Yep, I don't know why people forget about it. by Anonymous Coward · · Score: 1, Informative

    Anything that supports Interbase supports Firebird, which is pretty much everything. I don't think you tried very hard.

    Firebird is actually way better at the things people typically use SQLite for. It can be embedded about as easily (even statically like SQLite) and works in a similar fashion with a single database file if that's what you want, etc. It performs way better than SQLite though. On par with MySQL's performance or better (but has a much better/freer license than MySQL). Plus it supports features like stored procedures and such like PostgreSQL.

    It really is worth the effort.

  74. Re:Postgres is not Free! Don't be scammed! by Anonymous Coward · · Score: 0

    That "special" license is BSD, which is an open source compatible license, and completely compatible with GPL software. Idiot.

  75. Postgres + SQL = PostgreSQL by Anonymous Coward · · Score: 0

    learn that already!
    it's not postgre, it's postgres!

  76. Re:Truth is that Postgress Rocks, dual licenses su by viraltus · · Score: 1

    So why should anyone favor a free project where there exist reasons to apply for a commercial license when there are others where you don't even need to think about it?

    --
    Dear /. CENSORS that set people's Karma to Neutral when you disagree with them: FUCK YOU!!
  77. Go ahead, buy us! by Anonymous Coward · · Score: 0

    If companies started "buying out" top contributors of open-source software projects, it would be the best thing to happen to OSS. Thousands of new developers would join in their place, hoping to be the next buy-out targets. It's the same logic that fuels terrorism: each "martyr" creates 20 new wannabe-martyrs.

  78. Re: Yep, I don't know why people forget about it. by HiThere · · Score: 1

    You are correct. I *didn't* try very hard. I did a once over pass to select something to investigate more closely. Firebird made the first cut, i.e., I'd heard of it and what I'd heard seemed vaguely appropriate. It failed the second cut (which had only one winner) of being the easiest to figure out how to test. The one that passed that was the one I eventually used.

    I don't defend this process as a way of finding the best choice, except in the sense that it minimized the time involved in searching. But the question was "Why isn't FireBird better known?"

    P.S.: I am not now and never have been an Interbase user, so referring to Interbase doesn't help me at all. (Yes, I know that some of the Firebird documentation is Interbase documentation. This doesn't help me either in feeling confident that it's current or in knowning what to do. It's also no great hinderance, as I presume that if the Firebird site is pointing to it as documentation, then it's what they are recommending as documentation. But that's the way I counted it during my evaluation.)

    P.S.: I didn't need a really powerful DB. One of the choices I considered was Kirbybase. I think I ended up using BerkeleyDB (once from SleepyCat). I was probably using Python at the time (which would mean that the Firebird interface I considered was kinterbase).

    --

    I think we've pushed this "anyone can grow up to be president" thing too far.
  79. MySQL's InnoDB has row locking, MVCC & ACID, by toby · · Score: 1

    as do some other storage engines available for MySQL (such as PBXT).

    MyISAM does not, of course; it is more comparable to SQLite, although the latter does have transactions.

    --
    you had me at #!
  80. IMDB was traditionally a MySQL shop. by toby · · Score: 1

    Did they convert?

    --
    you had me at #!
    1. Re:IMDB was traditionally a MySQL shop. by Toze · · Score: 1

      No idea. A quick Google does confirm they hire for postgres devs, though.

      --
      No OS on the planet can protect itself from a user with the admin password. - Yvan256
    2. Re:IMDB was traditionally a MySQL shop. by toby · · Score: 1

      This presentation on IMDB architecture, written some time post-2006, only mentions MySQL.

      It's not surprising that a large scale site would use more than one RBMS though, in some role. Many Oracle shops - especially web sites - also run MySQL in some role. That may be a strategic factor in Oracle's purchase.

      --
      you had me at #!
  81. Re:Truth is that Postgress Rocks, dual licenses su by Hognoxious · · Score: 1

    If those reasons aren't relevant to you then why should it bother you? Given the example of making secret modifications mentioned by GP, I'd guess probably 1% of users would be interested in that. The other 99% wouldn't care. But it's nice that the choice is there for those who want it.

    --
    Confucius say, "Find worm in apple - bad. Find half a worm - worse."
  82. Let's be real by Anonymous Coward · · Score: 0

    We're very optimistic about free software. It can survive without funding. It can survive alongside superior competition. It is very resilient in every way, especially if as popular as this project is. But one thing it cannot do - is survive without the developers. Sure you can fork it, but as the guy up there says, if it had only 20 high-profile devs before there's little chance it'll gather 20 more of the same profile as those it lost. It is a real threat. The only two foreseeable solutions would be that "low-profile" devs start working harder, and those who left still try to contribute as best as they can. Unfortunately, the second one can be countered by the 'all your code is belong to us' clause in their contracts (bear in mind however, that they would have to accept it). In short, we should all look into projects where we can help (if not us, who will breathe new life into free software projects? *Someone* needs to develop them, you know?). There's plenty of learning opportunity, and we can help. We must admit most of us don't do it very often. And that's the real cause of this threat - that is, besides the fact that there's no universal commercial model which would directly fund developers. If we had the latter, the former would be eradicated immediately.

  83. This comment is not about PostgreSQL. by argent · · Score: 1

    I really think you're missing my original point, which was about MySQL... since MySQL was owned by a specific company and was licensed in such a way that it actually mattered who owned it, that company was a vulnerability. PostgreSQL is not exposed this way because the license doesn't give the copyright owner the ability to restrict the fork in any meaningful way.

    This is a problem with dual licensing, one that (for example) Qt avoided because Trolltech gave the Free Qt foundation the right to release Qt under the BSD license if Trolltech stopped its development. Monty could have given MySQL an escape clause like that, but either he didn't think of it or he thought it was giving up too much control.

  84. Re:just another asshole with a gun. by Anonymous Coward · · Score: 0

    I agree with you regarding reproductive freedom, freedom of speech, and freedom of (and from) religion - including freedom from the religion you're currently trying to impose. Freedom of speech does not include the freedom to take away other people's property, even if that property intimidates you. Please do try to read a book and understand what Natural Rights are before you go around imposing your wishful thinking on others.

    That's exactly what the people writing books on natural rights are doing.

  85. Re:just another asshole with a gun. by Anonymous Coward · · Score: 0

    No, libertarians who write books on Natural Rights apply econometric formulas to empirically identify which societal rulesets are necessary for a civilized society.

    Quoting my recent post from another socialist-leaning software forum:

    In reality, Natural Rights come from the principle of competitive advantage: a society that violates Natural Rights the least would have an empirically-observable materialistic advantage over other societies that violate them more. It's almost as clear-cut as penicillin, except of course you can't observe human societies through a microscope, and the lenses of history are blurred by pro-government bias that funds and controls most knowledge-related institutions.

    A society that tolerates murder has never made it out of the hunter-gatherer phase of human development. A society that tolerates theft is very unlikely to build a successful and stable economy. A society that believes in a false construct called "animal rights" (which violates actual Natural Rights of humans) wouldn't advance as well scientifically, due to the necessity of using animals for lab experiments. A society that believes in various false constructs called "positive rights" (ex. right to free food, health-care, unicorns, etc) will discourage economic productivity, experience flight of brains and capital, higher taxes, and it will eventually simply run out of competent people to tax (read Ayn Rand). Etc.

    No society with a complete monopoly on force in the hands of the government has ever prospered for more than a generation or two. Just compare gun-controlled Weimar Republic that lead to the rise of Hitler to Switzerland - which Hitler actually wanted to invade, but it simply wasn't cost-effective for him to do so, because of its armed populace being ready for an active campaign of disobedience. If the Jews in Germany were as well armed as the Swiss, then Hitler's rise to power would have been simply impossible! Gun control has cost hundreds of millions of lives in the 20th century alone, while the side-effects of gun control are minuscule in comparison!

    Furthermore, it is inevitable that avoidance of liabilities in the free market (cost of insurance, risk externalities, tort, perfectly legitimate local gun control by private property owners, etc) would inevitably lead to proliferation of "less lethal" self-defense technologies, and concentrate more firepower in the hands of qualified professionals. It is the government that's creating economic pressure for more lethal technologies, and it most certainly takes a government to create something as economically retarded as an aircraft carrier or an atomic bomb!

    Now, once again, this socialist-leaning forum is not a good place to have this debate, especially when outspoken points of view are restricted to only 2 posts a day. If you want to debate this further then please go to a more libertarian / Anarcho-Capitalist forum instead, where dissenting views are likely to be treated more substantively and not stifled, as they are here.

    Which is complete BS, and utter speculation.

    You talk about the Jews in Germany being as well armed as the Swiss? It still would have happened, to say otherwise is more speculative BS, and propaganda.

    There is no economic advantage to competition, unless you can crush and eliminate the competition. While there is a huge advantage to cooperation. That's how trusts form. Its basic game theory.