Anyone looking for Apache Mesos in the list of Apache Attic projects, news of its demise appears to have been greatly exaggerated: The decision to retire the project seems to have been canceled: [1]
You likely already know this, but for the sake of those reading: XML itself is still alive and well, what's retired is the "Apache XML Project," a collection of XML-related software.
It's even less momentous than that: "Apache XML Project" was a banner under which several different tools lived. Some of those tools have gone on to have their own lives and live on elsewhere.
Actually, according to the linked project page [1] only the "umbrella" XML project had been decomissioned; the only actual subpackages retired are axkit and xindice (never really used or even heard of those). Xerces, which as Xerces/J is a major part of Java's XML stack, and all the other subprojects have just migrated into standalone projects, including even XMLBeans which was resurrected on request of Apache's POI project for reading/creating MS Office files.
Fun fact: when I started contributing to Apache httpd in the 1990s, it was hosted on CVS; when you delete a file in CVS, its revision history ,v file in the repository is moved into a subdirectory called Attic. You can see Attic directories in NetBSD’s cvsweb, eg. http://cvsweb.netbsd.org/bsdweb.cgi/src/ (but not in OpenBSD’s repository for some reason?)
I'm feeling nostalgic. Anyone who has developed something for the internet in the early 2000s for sure have downloaded something from Apache website (e.g. Apache httpd which most people simply call "Apache", and Tomcat). Many products in the Attic were born during the golden age of Java.
Because I used Java extensively around 2001, then not till 2020, I paid no attention in the interim. It seems like it had an early golden age, then a middle ages in which horrors like Spring were born to compensate for the stagnation, and is enjoying a resurgence or renaissance now with Scala / Clojure / Kotlin / Java16 ?
I worked with Java from 2009 until now. I can't account for the 01-09 timespan, but I'd say the big gap between say java 1.5 and 1.8 was less about stagnation and more about letting other languages feel things out. I like that Java is never too far ahead or too far behind.
I do think the "hip" side of tech has started to warm back up to Java, both as the language adopts some of the niceties that python/ruby/kotlin/scala/etc have shown are quite ergonomic and also as the community, I think, warms back up to the idea that static typing can be net helpful and that maybe a good JIT compiler is nice too.
That's some solid historical revisionism is action here :-)
That period you mention was definitely due to stagnation, on Sun's part. It wasn't "watch the pioneers as the crash and burn and pick the good parts". It was "we're stuck".
That's probably fair. I was in high school during that period. I've mostly only ever known the Java owned by Oracle, where it seemed... reasonably kept? Java 8 happened under Oracle, after all.
26 comments
[ 2.8 ms ] story [ 69.5 ms ] thread[1] https://lists.apache.org/x/thread.html/rf0359da13d1c3baff882...
https://wicket.apache.org/
[1]: http://archive.apache.org/dist/xml/
It's a different approach to Hibernate, but has similar ends. We recommended it for teams who were comfortable with writing SQL directly.
with other forks https://github.com/baomidou/mybatis-plus
If you want to compose your SQL queries, it is excellent.
https://blog.mybatis.org/p/about.html
I do think the "hip" side of tech has started to warm back up to Java, both as the language adopts some of the niceties that python/ruby/kotlin/scala/etc have shown are quite ergonomic and also as the community, I think, warms back up to the idea that static typing can be net helpful and that maybe a good JIT compiler is nice too.
That period you mention was definitely due to stagnation, on Sun's part. It wasn't "watch the pioneers as the crash and burn and pick the good parts". It was "we're stuck".