4 ms·
Yep that pretty much sums it up. If Apache leaves that would be bad news for Oracle. There is a good deal of Java products that use Apache libs is some shape of
by kls 16y ago
Yep that pretty much sums it up. If Apache leaves that would be bad news for Oracle. There is a good deal of Java products that use Apache libs is some shape of form. I would venture to guess that it has to be near 80% of apps at least. I can't think of a single Java project that I have worked on that did not use Apache libs. They are even in the app servers IBM and Oracle's. If their is one group that I can think of that could kill Java with their absence Apache would have to be the one that comes to mind. While it may not kill it, it would be the shot that send a mass of developers out looking for the next big thing.
- nl 16y agoPulling out of the JCP doesn't mean that Apache will stop doing Java projects, though. But I agree with your point - less involvement by Apache in Java is a bad thing.
- deleted 16y ago[deleted]
- kls 16y agoObviously it is just speculation but, I think it means that Apache sunsets official Java, takes there own path and diverges. Without the TCK there is no way to guarantee that it works. Which if it happens, will fragment the market onto two separate JVM's. At that point, why not call it something else and move on. I know if it happened I would be hitching to the Apache trial as opposed to the Oracle one, if they diverge I would feel more comfortable on the Apache side. I have already been bit by two Oracle decisions since Acquiring Sun (Killing OpenSSO, being the one I am most PO'ed about). I would not stick around for a 3rd if they push Apache out. I have to imagine there would be quite a few others that feel the same.