So, follow me with the crazy idea of creating a Java-based package manager (using Java SE). Yeah, you got it right, a typical GNU/Linux package manager.
Why does it sound so crazy after all? Let’s assume that we could split the Java libraries into two, removing Swing/Awt stuff creating a theoretical java-core package. Moreover, let’s assume that disk size is not an issue (nowadays, it’s not).
Let’s start from Python. There are so many package managers out there using Python, completely written in Python (like Entropy), which has many disadvantages in my opinion: dynamic typing, cough cough, which is the root of all the Evil in this world, and makes it impossible to reliably introspect code by static analysis tools; slowness: to write fast (enough) code, you have to write “ninja combos” (list comprehensions, cough cough), Java is much faster than Python (fact!)… and so forth! And, don’t get me started with the Python 3.x idiocy, please no (this proves that Java is much more mature and reliable than Python, syntax wise).
So, am I really crazy to think that, given the “constraints” listed above (Swing/Awt and size), it wouldn’t be too bad to consider Java as programming language for package managers, given that Python brings more or less the same dependencies and pitfalls (more and more pitfalls, actually)?
Food for thought.