|
|
|
| Authored by: hardmath on Saturday, May 05 2012 @ 08:49 AM EDT |
Some fragmentation is inevitable, certainly under the terms of the GPL, but even
before that and entirely of Sun's own making (which Oracle tried and gave up on
resolving).
It's entirely reasonable to consider fragmentation as a "bad thing",
while at the same time contributing to it over the immediate horizon as one
adapts and innovates.
If the Spring framework example illustrates anything about the evolution of
Java, it is that useful features of third-party packages could be (over time) be
successfully folded back into the mainline distribution.
---
"Prolog is an efficient programming language because it is a very stupid theorem
prover." -- Richard O'Keefe[ Reply to This | Parent | # ]
|
| |
| Authored by: hAckz0r on Saturday, May 05 2012 @ 02:00 PM EDT |
| A GPL question for others that might know the answer. What is the
possibility
of
Google switching to OpenJDK and releasing it as LGPL? My understanding
is
that Google didn't want plain GPL because of the licensing issues with
the
handset makers. If Google could fork the OpenJDK then they could
modify it
enough to become what they have now, only with an LGPL
license to better suit
the handset makers. How would that affect the
handset makers negatively? I
understand making it LGPL might be tough
considering Oracles hand in the
matter.
How does the LGPL compair to the standard Android
license?
---
DRM - As a "solution", it solves the wrong problem; As a
"technology" its only 'logically' infeasible. [ Reply to This | Parent | # ]
|
- OpenJDK/LGPL ? - Authored by: Anonymous on Saturday, May 05 2012 @ 06:39 PM EDT
|
|
|
|
