4 ms·
>> Remind me again why this is killing Django and Rails for mindshare Staying specific to package managers (which the article is about), Python's Pip doesn't h
by nilliams 10y ago
>> Remind me again why this is killing Django and Rails for mindshare
Staying specific to package managers (which the article is about), Python's Pip doesn't have a dependency resolver [0] and Python packaging is miserable without using virtualenvs, which is frustrating overhead. Also the setup.py situation is a hot, unstandardised mess.
As far as Ruby goes, (I don't have as much experience here, but ...) Rubygems seems hella slow, and the require story sucks compared to npm. Do I have to require 'rubygems'?, should I require_relative? In my book npm has both beat for 'is fast' and 'just works'.
[0] https://github.com/pypa/pip/issues/988 https://github.com/pypa/pip/issues/988
- stouset 10y ago> Do I have to require 'rubygems'? No. Never. Your code should not expect/require a particular dependency manager. > should I require_relative? This has nothing to do with package management, and the answer is again, "no, never" if you're trying to require a gem. This is to require files from within your own projects.
- nilliams 10y ago> Do I have to require 'rubygems'? >> No. Never. Your code should not expect/require a particular dependency manager But there's loads of code out there that does that. So the answer isn't clear. > should I require_relative? >> This has nothing to do with package management, [...] It's to do with the interplay between what you install via package management and what you require. In Node you require a package by the same name as you install it, and there's one `require()`, end of story. In Ruby, it's less clear. That's what I meant. If you want a further example: Why do I `gem install activesupport`, but `require 'active_support'`?