Slashdot is powered by your submissions, so send in your scoop

 



Forgot your password?
typodupeerror
×
Open Source Programming Red Hat Software Virtualization IT

Who Controls Vert.x: Red Hat, VMware, Neither? 118

snydeq writes "Simon Phipps sheds light on a fight for control over Vert.x, an open source project for scalable Web development that 'seems immunized to corporate control.' 'Vert.x is an asynchronous, event-driven open source framework running on the JVM. It supports the most popular Web programming languages, including Java, JavaScript, Groovy, Ruby, and Python. It's getting lots of attention, though not necessarily for the right reasons. A developer by the name of Tim Fox, who worked at VMware until recently, led the Vert.x project — before VMware's lawyers forced him to hand over the Vert.x domain, blog, and Google Group. Ironically, the publicity around this action has helped introduce a great technology with an important future to the world. The dustup also illustrates how corporate politics works in the age of open source: As corporate giants grasp for control, community foresight ensures the open development of innovative technology carries on.'"
This discussion has been archived. No new comments can be posted.

Who Controls Vert.x: Red Hat, VMware, Neither?

Comments Filter:
  • Does not support PHP (Score:1, Informative)

    by Anonymous Coward on Saturday January 12, 2013 @03:56PM (#42569363)

    Funny how they support "the most popular languages", except for the one everyone actually uses. I think they meant "corporate", not popular.

  • by nickmalthus ( 972450 ) on Saturday January 12, 2013 @05:03PM (#42569781)
    There is precedence for this, it happened before with the Sun OpenDS [wikipedia.org] and the Sun/Oracle Hudson [wikipedia.org] Open Source projects. When the contest of ownership comes down to project developers and corporate lawyers the lawyers usually win the legal battle but the developers win the community battle due to forking.
  • by Evardsson ( 959228 ) on Saturday January 12, 2013 @05:10PM (#42569825) Homepage
    That would probably be because the PHP-Java bridge [sourceforge.net] is a kludge and horribly inefficient. Having had occasion to use the bridge for a non-trivial project, I am actually ok with this Java-based server not supporting it.

    That said, if you really want the headache, I am sure you can figure out a way to use the PHP-Java bridge to tie to your current PHP apps and use them as Java in the Vert.x server. I do have to say, though, I do pity anyone who has to do this.
  • by Anonymous Coward on Saturday January 12, 2013 @06:43PM (#42570445)

    It's Java-based and should be banned by every user considering themselves half computer literate.

  • by rtfa-troll ( 1340807 ) on Saturday January 12, 2013 @06:49PM (#42570479)

    If they assert ownership of the code, and decline to release it under an open source licence then they can pretty much kill the fork as well.

    a) Fortunately not because VMWare and Red Hat [google.com] have already made a posting otherwise.

    b) Fortunately not because this is a public project and has been explicitly and openly discussed by a number of people from VMWare over a long time. In general, companies are liable for the things their employees do as part of their work. Especially if they knew about it or should have known about it. The only comeback they have is disciplinary action against the employee. Judges sometimes come down really hard on companies which try to wriggle out of this kind of thing.

    c) Just think about it. If what you said was true, wouldn't Barings bank [wikipedia.org] just have said "no; sorry, rogue trader; give us back our stolen dollars". Don't think the tech industry will manage tricks the financial industry has never thought of.

  • by drinkypoo ( 153816 ) <drink@hyperlogos.org> on Saturday January 12, 2013 @10:03PM (#42571647) Homepage Journal

    So does that mean that VMWare will soon be bought by Oracle?

    No, anything but that. VMware works.

One possible reason that things aren't going according to plan is that there never was a plan in the first place.

Working...