Although there are Kotlin and Scala, which are a little revolution in the Java development I still exclude them for their missing ecosystem equivalent to NPM.
What would an "ecosystem equivalent to NPM" be like? There are like millions of packages in the Maven Repository.
Graduated in Digital Media M.Sc. now developing the next generation of educational software. Since a while I develop full stack in Javascript using Meteor. Love fitness and Muay Thai after work.
You're right and I was very vague here. I personally count dev experience with Maven as too technical and overly complex compared to NPM. I will clarify that in the post.
Maven uses XML. Generally speaking, that's the extent of its complexity, at least in regular day to day usage. Besides that, maven tends to be much more reliable than npm, both with regard to how it functions and with regard to the packages that are available.
Graduated in Digital Media M.Sc. now developing the next generation of educational software. Since a while I develop full stack in Javascript using Meteor. Love fitness and Muay Thai after work.
These are technical arguments and I agree with them on the technical side. Still lacks UX to me and in my post I mentioned it should also make fun.
For example: How do you search for, let's say a "currency converter" package and estimate, based on the results, if the package/library could be worth to become a dependency of your project plus then install it? I mean please prove me wrong but this was not really a joyful experience for me or maybe I just did it wrong.
You Google "Java currency converter maven" and try the handful that come up. Something to keep in mind is that although it's not hard to publish to the Maven repository, the barrier is higher than for npm. As a result, people tend to not use the Maven repository as a Pastebin, meaning that the average quality tends to be much higher.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
What would an "ecosystem equivalent to NPM" be like? There are like millions of packages in the Maven Repository.
You're right and I was very vague here. I personally count dev experience with Maven as too technical and overly complex compared to NPM. I will clarify that in the post.
Maven uses XML. Generally speaking, that's the extent of its complexity, at least in regular day to day usage. Besides that, maven tends to be much more reliable than npm, both with regard to how it functions and with regard to the packages that are available.
These are technical arguments and I agree with them on the technical side. Still lacks UX to me and in my post I mentioned it should also make fun.
For example: How do you search for, let's say a "currency converter" package and estimate, based on the results, if the package/library could be worth to become a dependency of your project plus then install it? I mean please prove me wrong but this was not really a joyful experience for me or maybe I just did it wrong.
You Google "Java currency converter maven" and try the handful that come up. Something to keep in mind is that although it's not hard to publish to the Maven repository, the barrier is higher than for npm. As a result, people tend to not use the Maven repository as a Pastebin, meaning that the average quality tends to be much higher.