Apache, OK

Posted Dec 1, 2016 16:56 UTC (Thu) by ncm (guest, #165)
Parent article: Apache and the JSON license

It is fortunate that these problems principally affect Apache Project packages. Since "Apache is where projects go to die", it affects mainly moribund projects. Among those I include Ooo and everything Java, which seem to land at Apache almost by default, and which often have not yet formally noticed they are dead -- even those that started out that way.

It is good to the degree that it hastens those deaths, but bad when actually dealing with it, instead, consumes effort better spent on projects that have a future.

Apache, OK

Posted Dec 1, 2016 18:23 UTC (Thu) by marcH (subscriber, #57642) [Link]

> everything Java, which seem to land at Apache almost by default,

Not 100% sure what you meant here but J2EE is one of Java's top successes and it's strongly and obviously related to Apache the web server.

Apache, OK

Posted Dec 5, 2016 16:30 UTC (Mon) by ssmith32 (subscriber, #72404) [Link] (1 responses)

,>Among those I include Ooo and everything Java, which seem to land at Apache almost by default,

I don't see how any rational enginneer can consider Apache Hadoop or Cassandra dead (A rather large mass of Apache & Java, with a considerable ecosystem both free & commercial - > 1 billion$ - around both). There are even products I've personally recommended against using (Tomcat and any J2EE stuff) that I can't see how you would think are "dead".

Must be wishful thinking? I suppose some of my wishes and your beliefs could find common ground, but the facts are against the both of us...

Apache, OK

Posted Dec 6, 2016 0:51 UTC (Tue) by ncm (guest, #165) [Link]

I mean "dead" as used in the expression, "You are dead to me". (No, dear reader, not you. Java.)