Slashdot Mirror


JBoss Founder Hard-Nosed About Open Source

Infonaut writes "In this Business Week interview, JBoss founder Marc Fleury refers to "hobbyist" Open Source contributors and makes the case that "no one is going to work for free." Fleury dismisses people who contribute for something other than money as "Hari Krishnas" and makes reference to the "hippie dream". Fleury's sharp, profit-focused approach has brought him success, but isn't it in some sense built on the shoulders of the hippies and hobbyists he seems to scorn?"

14 of 423 comments (clear)

  1. Again? by Anonymous Coward · · Score: 4, Insightful

    makes the case that "no one is going to work for free."

    Hey, 1990 called. They want their open-source-failure theory back!

    1. Re:Again? by Anonymous Coward · · Score: 3, Insightful
      Hey, 1990 called. They want their open-source-failure theory back!

      He's not completely wrong. Open source people will only work on what interests them so you have a ton of very crappy, partially-finished open source software out there that usually just barely scratches the itch of the original programmer. Sure there are successes like Mozilla Firefox, Apache, KDE, Gnome, the Linux kernel, etc., but for every success there are hundreds of completely useless failures out there.

      Most businesses would be insane to rely on open source programmers to develop their software for them... that's why many of you reading this still have a job developing commercial software or in-house homegrown software. They give you money, you develop software that they want. It's a win-win situation. The alternative is they give you nothing, you starve, someone spends all their free time writing another damn e-mail client or content management system in PHP.

    2. Re:Again? by Lepaca+Kliffoth · · Score: 5, Insightful

      "He's not completely wrong. Open source people will only work on what interests them so you have a ton of very crappy, partially-finished open source software out there that usually just barely scratches the itch of the original programmer. Sure there are successes like Mozilla Firefox, Apache, KDE, Gnome, the Linux kernel, etc., but for every success there are hundreds of completely useless failures out there."

      And why do you want to use the failures rather then the successes? I use kernel + Xorg + KDE + several applications like mplayer, amaroK, thunderbird and so on. They are all very polished, perform admirably and only the testing versions ever crash (and I use unstable things only in rare cases). If someone wants to code a pile of crap it's none of my concern, the great, well coded apps I can install are more than I'll ever use.

      "Most businesses would be insane to rely on open source programmers to develop their software for them... that's why many of you reading this still have a job developing commercial software or in-house homegrown software. They give you money, you develop software that they want. It's a win-win situation. The alternative is they give you nothing, you starve, someone spends all their free time writing another damn e-mail client or content management system in PHP"

      I don't see the problem here. Open Source programmers are still programmers and they're paid by whoever employs them. Novell and Red Hat aren't exactly what you would call community-driven, heh. The programmers giving code for free are usually guys sending in patches for some kind of problem they found and were able to fix. Anyway if someone wants to donate it's his decision, nobody points a gun at him. If someone starts a project, leaves it and it remains unfinished it will go in the pit together with all the crappy programs I'll never use.

    3. Re:Again? by eyeye · · Score: 4, Insightful

      but for every success there are hundreds of completely useless failures out there.

      The same could be said of commercial software development...
      --
      Bush and Blair ate my sig!
    4. Re:Again? by slavemowgli · · Score: 4, Insightful

      How many non-trivial, successful open source software projects aren't written mostly by staff paid to do the job?

      That's the wrong question to ask. I'd argue that any piece of open-source software that is non-trivial, successful and serves a purpose that is of interest to companies *will* eventually attract funding, including developers paid for by companies, but that doesn't mean that open-source must have a commercial (paid) developer base to be successful. You have the direction reversed here: success leads to paid development, not vice versa.

      The *real* question you'd have to ask is how many successful, non-trivial FOSS projects were *started* by people with a commercial interest (companies), and if you do that, things will certainly look differently. Tools like the GNU system, the Linux kernel itself, PHP, Perl and so on were all started without any commercial help - it was only later on, when they were already successful, that they attracted commercial help. JBoss may be different (or not - I don't know its history), but if I had to make an educated guess, I'd say that the amount of FOSS started by companies is by far the minority.

      And of course, that's only looking at FOSS that is of interest to companies, anyway, which gives a skewed picture, since there are several important projects and high-profile projects (not to mention countless smaller ones) that cater to a different target group - namely, end users themselves, who arguably are both more important and more abundant than companies.

      --
      quidquid latine dictum sit altum videtur.
  2. If... by zotz · · Score: 3, Insightful

    If he really has this attitude, he is sadly mistaken and most likely being a jerk.

    A lot of my motivation for contributing is a way saying thanks.

    How does he pay for all of his foundations? Or is he just a taker?

    Since his stuff is Free (if it is) you can look at it as who cares?

    One thing with people who only do it for the money is that I tend not to trust them not to make things unnecessarily complex in order to earn the service/consulting money.

    In any case... Go Free Software.

    all the best,

    drew

    --
    FreeMusicPush If you want to see more Free Music made, listen to Free
  3. Its true what he says by rerunn · · Score: 4, Insightful

    There really is no such thing as a free lunch and where the rubber meets the road, it comes down to the bucks. However, it certainly makes him look like a knob to piss on very things that have helped him get to where he is now. Dude needs to chillax and smoke a bowl I say.

  4. the art of open source by handy_vandal · · Score: 4, Insightful

    How many artists choose Art over Money?

    Most of them. Some artists do actually starve for their art, although this is perhaps a romanticized minority. Nonetheless, the general principle holds true: people driven to create art have less time for day jobs -- or if they're confined to day jobs, their souls suffer for want of art.

    Thus with some coders, who give it away: they are driven to create the art of open source.

    -kgj

    --
    -kgj
  5. I don't get it. by KriKit · · Score: 5, Insightful

    Why are people so hate filled when it comes to the thought of people working in their spare time to help each other? Its called charity. I think this guy feels threatend. Why be so negative to a concept thats so positive?

  6. "Support Contracts" = "closed source" by jfengel · · Score: 4, Insightful

    I think that you're overestimating the value of support contracts and other open source based business plans. Sure, there's some money to be made there, but it's a latecomer to the open source party and only a tiny piece of the puzzle.

    Open source works because all of us are smarter than one of us. Programmers naturally look for preexisting solutions to problems, because it enables them to get to the thing that they really want to do faster. And they'll naturally return the favor when they can. It's just politeness to contribute bug fixes.

    This model has serious, serious flaws. There will always be more takers than givers. But the good news is that distribution is cheap, so one giver can support hundreds of freeloaders.

    Other problems are harder. Many of the contributions take place against the background of a standard closed-source project, where the management doesn't mind participating in open source as long as the real product development remains proprietary. A utopian pure open-source environment will fail; the whole thing works as well as it does only because the economics of redistribution are so cheap.

    There are many other issues which are not easy to work around, and that's what this guy is really getting at: open source can't promote the non-fun stuff, like good user interfaces and (for the most part) QA. Certain crucial pieces of infrastructure (Apache, Linux kernel) have so many people banging on them that they get QA'ed anyway, and they're so integral to other money-making schemes that it ends up being in some people's interests to do the work anyway. But away from those projects the software gets buggier and buggier, and you'd have to pay people to make them less buggy.

    So in the end there's money to be made in the standard business model, which is actually what JBoss is using. The difference is that some of the software they develop "leaks" around the edges into open source, because that's their way of playing nice with other people doing the same thing. The more core something is, the more effective it is to share your work and to use the shares in return; the system supports the freeloaders.

    The real money is in doing specific work for specific customers, of which "support contracts" are only a trivial part. "Support contracts" are really just another name for "closed-source, proprietary software" built on top of the open source. And that's just business as usual.

    As programmers, we'll share because it's fun and we'll share because we're a community that likes to help each other out. That's at the end of the day; from 9 to 5 we'll continue to write software the way it's always been done, for the same economic reasons: you have to pay people to develop the boring stuff and the stuff that involves knowing the subject domain. The kernel and Apache mean you don't have to know about anything except computers. If you want to build a ticket reservation site or a pharmaceutical database, you actually have to know something outside of computers, and that always costs money.

  7. RTFA by Anonymous Coward · · Score: 5, Insightful

    Read the fucking article.

    He's not calling all open source contributors "Hari Krishnas", he's calling the ones who heckle him at conferences "Hari Krishnas".

    The best test of your belief in free speech is when someone says something you don't like.

    The best test of free software is when someone does something with it that you don't like (e.g. making money).

    This guy is following the license and spirit of the GPL, and making money doing it. People should be patting him on the back, not giving him a hard time.

  8. Re:Only one draw-back to open-source. by tacocat · · Score: 4, Insightful

    You are kidding right? That or your pretty wrong.

    Microsoft and AOL have been adopting something called SPF that was originally presented by one of these F/OSS Hippies.

    IIRC TCP/IP was originally developed in F/OSS software because it was Open.

    Who did transparent GUI design?

    Who first developed a XML based solution for the general group of Office Products?

    Who developed and presented the rssmail whitepaper? Hippies or Suits?

    What was the first tool for real time chat? IRC or AIM? Who developed it?

    Was the first implimentation of a Web Browser (Mosaic) open source or coompany derived?

    You forgot to wrap your comments in sarcasm tags or you are an idiot.

  9. Re:Mr. Fleury doesn't know his way around FLOSS by Rakishi · · Score: 3, Insightful

    He does understand that as well, read the actual interview not the butchered blurb, however they're all hobbyists to him. And he is right, they are hobbyists at least those who write the actual software. What is so hard to understand about that? As you yourself said, they're motivations are different and in essence more "fluid" than that of a paid developer. They may get bored when that annoying last 5% of the app has to get done (like fixing those annoying bugs, etc.), other things may come up, and so on.

    However, as he says they seem to get pissed off quite often when they realize he is able to make money of it while they can't.

    The interview is pretty vague, however it appears to me that he doesn't particularly like the model where you basically sell service or whatever while using hobbyist to make the actual code. As you yourself pointed out hobbyist have different motivations, which he would probably argue aren't the best for keeping such a business model alive. Even in Linux the main developers, asfaik, are basically paid to work on the Kernel.

  10. Added value... by Kjella · · Score: 3, Insightful

    you can't have a business model where you say, "Hey, guys, you write my software for me and then I'm going to make all the money off of it!"

    ...of course you can. Game publishers, book publishers, movie companies, tv stations, music labels and so on thrive on taking a "production" and delivering it to consumers. However, you do need to have some added value. Even though the applications are FLOSS there are many way to do that, I'm sure you can think of a few...

    Kjella

    --
    Live today, because you never know what tomorrow brings