npm vs. RubyGems.org

[npm]is well suited while we use it to install packages to windows, it is used to start the project from scratch to install dependencies.

Incentivized

RubyGems is a great packaging library primarily because of its verbose logging information and easy to navigate system architecture. We've dealt with artifactory systems in the past for Java and JavaScript, and RubyGems just makes it a lot easier to handle the packaging and deployment of our reusable libraries. We've noticed in the past that there are times where (if all 200+ teams) are releasing at a similar time that publishing the gems can lag, but that's fairly rare.

Incentivized

• We can easily use it to install packages

Incentivized

• Seemless packaging
• Well documented
• Verbose error logs
• Active community support
• Quick security fixes/releases

Incentivized

• Need to install dependencies for the particular package managers.

Incentivized

• Lack of solid Windows support.
• Not great performance if lots of people release at the same time.

Incentivized

RubyGems has strong community support and finding issues to errors is as simple as searching for the error message you're receiving (but usually the error is clear enough without having to bother with that). Honestly, the framework is simple enough that support isn't needed much, but it has been helpful to us in the past when we have needed it.

Incentivized

It is open source and easy to utilize and it is simply worked for me.

Incentivized

RubyGems is easier to use and to troubleshoot issues overall. Sometimes when troubleshooting in other systems errors are masked and it takes a trained eye or a lot of time searching through Google trying to find out what it really means. RubyGems is very verbose and allows for quick troubleshooting of any deployment problems.

Incentivized

• Yeah it is dependent it cause of without NPM angular doesn't work

Incentivized

• Quick package hosting.
• Faster deployment process.
• Less troubleshooting needed during deployment.

Incentivized