|
|
TOP THREE LINKS YOU MUST CLICK ON
Java
Sun Will Open-Source Java "Today, Tomorrow or Two Years Down the Road"
Hard on the heels of the announcement by Sun's president and COO Jonathan Schwartz earlier this week that Solaris will be open-sourced comes confirmation from Sun's Java technology evangelist: 'We haven't worked out how to open-source Java - but at some point it will happen,' says popular speaker and expert in Java technology and distributed systems, Raghavan 'Rags' Srinivas.
Reader Feedback : Page 1 of 1
#22 |
jimcap commented on the 9 Jun 2004
Every one who has ever done some serious Java work will (or should) agree with most of the remarks made sofar. Sad but true. Yet, Java is still growing becoming better with every release, it''s future looks better than ever. Is that a paradox? |
#21 |
JavaRocks commented on the 4 Jun 2004
It makes perfect sense if Sun is doing this for the same reason Apple open sources the internals of Mac OS X. Allowing their users access to the source to Solaris-- even if the license is "poisoned" to prevent it from being mixed with GPLed code-- would help Sun''s users. They would be able to adapt the OS to strange fine-tuned uses and arcane hardware, or more easily debug kernel plugins. A shop that might otherwise have gone "well, we like solaris, but we don''t want to be limited to sparc and x86, so we''ll go with linux" might be dissuaded. Allowing their users access to the source to the JVM-- even under a GPL-incompatible license-- would do the same. It would allow Sun''s users to port the JVM to those few platforms Sun doesn''t support yet, or more easily debug JNI software. This is definitely a benefit for Sun''s users. It makes both Java and Solaris more attractive. It makes a lot of sense. |
#20 |
ryen commented on the 4 Jun 2004
Are there any "success stories" of proprietary software going open source? i guess the definition of "success story" is subject to opinion: Success for the releaser? (Sun) Success for the community? |
#19 |
atehrani commented on the 4 Jun 2004
I think Java is fine the way it is. Open Sourcing it will not bring any improvements and actually might hurt Java. Name one advantage for Java going open source? |
#18 |
minkwe commented on the 4 Jun 2004
CORRECTION: Sun will "hybrid-source" Java. This is hybrid-source not open-source. Please use the right term for the right software. |
#17 |
eeg3 commented on the 4 Jun 2004
Of course the opening of Java's source will be neat for "the community," but it doesn't seem like a very smart business move for Sun. There might be some temporary benefits in publicity, but no real benefits in the long run. Atleast if they keep it closed, they'll retain some control, and have the ability to possibly make money off of it. However, i'm sure they know this, and that's why it's not being released now, and it probably never will be, unless they somehow conjure up a way to release the source and retain complete control of it. ...Which seems impossible to me. |
#16 |
Call me paranoid or even a conspiracy theorist, but what if Microsoft is behind this? What if Microsoft, as part of their settlement with Sun, asked them to open-source Java so that they could embrace and extend it, and pollute it as they tried to before? How much do you want to bet that Java will be open sourced under a BSD-style license, and not the GPL. |
#15 |
mrfibbi commented on the 4 Jun 2004
I think that people who worry themselves over the ominous and supposedly inevitable "fragmentation" really need to take a second look at things. 1-There are numerous examples of open source programming languages that have remained centralized and unfragmented, like Perl and Python. 2-Because java depends on a uniform standard and VM, any attempts to split off or fork the source tree will die miserably due to a lack of compatibility with the massive pool of existing code and classes. 3-In fact, there is actually LESS chance of fragmentation when Java lies in the hands of the public, first because it means that no one will start up a competing "openjava", a venture that would almost certainly lead to incompatibilities, and second because, as the example of the death of xfree86 shows, too much central and absolute control over software by a small group will inevitably anger developers and users alike, leading them to search for an alternative. |
#14 |
kjj commented on the 4 Jun 2004
The most annoying part of Java on Freebsd is that you are required to build the thing yourself due to all the restrictions. This wouldn't be such a problem but the Java libary gets larger all the time and gets to be a bigger chore just to install it. As I understand it this is due to licensing that only allows the Java on Freebsd developers to release patches with must be applied to the base source downloaded from Sun. If Java used a true open source license then this would no longer be a problem, because there would be no restrictions on redistribution of either modified source or binaries built from the modified version. |
#13 |
Tarantolato commented on the 4 Jun 2004
Sun has this spooky, almost pathological, fear of forking. I guess you can attribute it to fallout from the proprietary Unix wars of the 80s and 90s. Thing is, those were a direct consequence of proprietary licensing. Everyone took the "historical Unix" code, put it in their own systems, and then chugged along incompatibly, with the new code hidden. The difference with GPL'd code is that if you use it, you have to publish it. So your rivals can copy or emulate incompatible features easily. GPL projects can fork, but the forks can dovetail back into one another. Proprietary projects that fork stay forked. |
#12 |
Vengeful weenie commented on the 4 Jun 2004
Why is it that so many people feel the need to jump on Sun & Java? There are pleny of companies that have given less to their respecive industries. Yes, so Sun has decided to OS Java, a step that they said they wanted to do a while ago, but didn't want to see the language pulled apart while it was immature. Well, if they feel it's time then great. They did start it up, and pay for a ton of development, and do a lot of promotion. Did they benefit? You bet. They are a company, and after all hopeful dreams alone never get you anywhere. BSD, RPC, NFS, Java -- I can't wait to see what they come up with next. The're not the only ones with great solutions, but they have a good track record. Kudos. |
#11 |
PointofInformation commented on the 4 Jun 2004
If you develop in java, you don't have to pay sun any money. Sun uses what they call a "protected source" license, which basically says, "Anyone can use this, but only we can make changes, or release new distributions." Open sourcing java wouldn't really hurt them, and god knows java could use it. |
#10 |
This will be a great thing for Sun and the open-source community, but only as long as the source is licensed under a non-restricting license. I don''t think that is going to happen though. If it happen, all I can say is "rejoice!" :) |
#9 |
leshert commented on the 4 Jun 2004
It''s not nearly as big a deal as open-sourcing, say, Solaris, simply because it''s not going to wreck a primary revenue stream for Java. I''ve wondered for a while where Sun makes money from Java, particularly enough to recoup what they spend on it. I can''t imagine it affects sales of Solaris boxes that much. |
#8 |
dekeji commented on the 4 Jun 2004
Sun has been saying that they will "somehow open source Java" since 1996. Has it happened? No. They changed their mind. Sun has also been saying that they will "somehow have Java standardized by a standard body" since 1996. Has it happened? No. They changed their mind. Sun like Java being owned completely by them, and they won''t change. What they will do is that they will fiddle with the Java source license a little an declare that it is now "open source", just like they created the "Java community process" and claim that it''s an "open process". You don''t have to worry about Java forking: Sun isn''t going to give up control. They are going to keep Java proprietary, and they are not going to "open source" it in any sense anybody other than they themselves would recognize. |
YOUR FEEDBACK  | JavaOne 2008: Chris
Keene's Prescription for
Curing the Java Flu By Christopher Keene HommeDeJava wrote: GWT is
what JSF would have to
be...
Building on over six
millions Java developers
and sound expertise of
Rich Webapps the Google
Web Toolkit (GWT) could
become the next big thing
for Java development.
GWT and
Java-to-JavaScript
compilation are already
big.... |  | Virtualization Journal
Attracts JavaOne
Attendees to SYS-CON
Media Booth By Virtualization News Desk JavaOne News Desk wrote:
Virtualization Journal
now reaches more than
60,000 online readers
with monthly digital
editions and weekly
newsletters |  | Borland Finally Dumps
CodeGear Tools Division By Maureen O'Gara CodeGear News Desk wrote:
It's only taken Borland
two years but it's
finally dumped its
CodeGear tools division,
responsible for Borland's
hereditary JBuilder,
Delphi and C++ Builder
lines as well as its new
web ventures into PHP and
Ruby, said to be used by
7.5 million developers. |  | Managing
Environment-Specific
Properties By Jason Newman; Dave Jones Michael Frank wrote: The
article asserts that most
will want to use a
classpath for locating
their "external"
properties files, but
I've found that the
easiest way to manage
external properties is to
use the local file
system, but include the
root directory for all
files as a... |  | Memory Caching in WAS By Pooja Gupta; Sherman Lee was5118 wrote: Authors do
not mention the
SampleCacheCommand class
must implement com.ibm.we
bsphere.command.Cacheable
Command or extend com.ibm
.websphere.command.Cachea
bleCommandImpl, also
source code is not
provided for download.
I would encourage readers
to visit IBM Tech Journa... |
SUBSCRIBE TO THE WORLD'S MOST POWERFUL NEWSLETTERS
|
SYS-CON FEATURED WHITEPAPERS
|