decoration decoration
Stories

GROKLAW
When you want to know more...
decoration
For layout only
Home
Archives
Site Map
Search
About Groklaw
Awards
Legal Research
Timelines
ApplevSamsung
ApplevSamsung p.2
ArchiveExplorer
Autozone
Bilski
Cases
Cast: Lawyers
Comes v. MS
Contracts/Documents
Courts
DRM
Gordon v MS
GPL
Grokdoc
HTML How To
IPI v RH
IV v. Google
Legal Docs
Lodsys
MS Litigations
MSvB&N
News Picks
Novell v. MS
Novell-MS Deal
ODF/OOXML
OOXML Appeals
OraclevGoogle
Patents
ProjectMonterey
Psystar
Quote Database
Red Hat v SCO
Salus Book
SCEA v Hotz
SCO Appeals
SCO Bankruptcy
SCO Financials
SCO Overview
SCO v IBM
SCO v Novell
SCO:Soup2Nuts
SCOsource
Sean Daly
Software Patents
Switch to Linux
Transcripts
Unix Books

Gear

Groklaw Gear

Click here to send an email to the editor of this weblog.


You won't find me on Facebook


Donate

Donate Paypal


No Legal Advice

The information on Groklaw is not intended to constitute legal advice. While Mark is a lawyer and he has asked other lawyers and law students to contribute articles, all of these articles are offered to help educate, not to provide specific legal advice. They are not your lawyers.

Here's Groklaw's comments policy.


What's New

STORIES
No new stories

COMMENTS last 48 hrs
No new comments


Sponsors

Hosting:
hosted by ibiblio

On servers donated to ibiblio by AMD.

Webmaster
OpenJDK use and implications. | 687 comments | Create New Account
Comments belong to whoever posts them. Please notify us of inappropriate comments.
OpenJDK use and implications.
Authored by: Anonymous on Friday, April 27 2012 @ 09:24 PM EDT
Well I don't really want just lawyers views. Just interested in understanding
how it works. :)

And with regards to your second point I think that there are two ways you could
choose to use OpenJDK. You could follow what Sun/Oracle want you to do and add
back into OpenJDK maybe via the JCP as you suggest. But one of the founding
principles of Open source is that if what the code does now doesn't work for you
then you are free to innovate on top of it. As long as your innovations are
free for others to use (or you only use your code internally and don't
distribute). You release it so that others can build on it not just so they can
build YOU a better version for free!

You might decide that you want to make a new language and you like many things
in OpenJDK so you copy it and make a new language. Or you might decide that you
want to combine your new language as a small part of a bigger platform project.
Maybe your new derived language use will be used on 100's of millions of devices
some day and be use to write more applications that Java ever did (like Android
is doing now).

So just saying that maybe because of the really cunning way Sun/Oracle have
licensed OpenJDK and because of software patents we are left too scared to use
this Open source project freely as a normal GPL'ed project would be otherwise.
I guess there is a case to argue the same is true with any open source project
where Software patents may come into play.

Michael

[ Reply to This | Parent | # ]

Groklaw © Copyright 2003-2013 Pamela Jones.
All trademarks and copyrights on this page are owned by their respective owners.
Comments are owned by the individual posters.

PJ's articles are licensed under a Creative Commons License. ( Details )