6 ms·
Bower is definitely not dying, and in fact Npm is totally unsuited for some communities http://harry.garrood.me/blog/purescript-why-bower/ http://harry.garrood
by berdario 10y ago
Bower is definitely not dying, and in fact Npm is totally unsuited for some communities
http://harry.garrood.me/blog/purescript-why-bower/ http://harry.garrood.me/blog/purescript-why-bower/
- zatkin 10y agoTL;DR: dependencies are a difficult problem. When you use two distinct dependencies that subsequently have the same dependency but separate major releases, you may encounter breakage. The author simply prefers Bower because of how it handles this problem differently than npm.
- joshwcomeau 10y agohttps://www.google.com/trends/explore?q=bower,npm https://www.google.com/trends/explore?q=bower,npm "Dying" is a bit strong, but there's no question that NPM is becoming the go-to choice for javascript development across the stack.