3 ms·
It's really disappointing to see this sort of "reasoning" used so often these days. Just because somebody points out serious flaws or problems with one technol
by Pacabel 13y ago
It's really disappointing to see this sort of "reasoning" used so often these days.
Just because somebody points out serious flaws or problems with one technology does not automatically mean that he or she thinks that other, unrelated-yet-similar technologies aren't flawed or are somehow perfect.
- 1stop 13y ago> I'm glad we've started to move away from node.js and started to use Java. That is what I was responding to directly. The implication from the statement was that npm flaws (i.e certificate changes that break everything) is a good reason to switch to Java. It isn't at all a good reason to switch to java, as java's equivalent would easily waste more time than even this rather embarrassing certificate problem with npm. > unrelated-yet-similar technologies It is related, and similar, it is a like-for-like comparison between nodejs package management and java package management.
- teacup50 13y ago> It isn't at all a good reason to switch to java, as java's equivalent would easily waste more time than even this rather embarrassing certificate problem with npm. Works fine for me. Has a healthy ecosystem of 3rd-party artifact repository implementations.
- deleted 13y ago[deleted]
- EdwardDiego 13y ago> It isn't at all a good reason to switch to java, as java's equivalent would easily waste more time than even this rather embarrassing certificate problem with npm. As someone who has used it daily for the past 5.5 years - not really. That said, I'd prefer something like Gradle, but I can't fault Maven for just working, goddamnit.