rubygems

Yes but in practice a lot of them do, for example, when they download a library from PyPI or rubygems...?

Most of the time that is likely due to bundler/rubygems stuffing your load path full and causing thousands of unnecessary stat calls.

Ruby => Rails (most of the time...) Python => Django NodeJS => ExpressJS Ruby => RubyGems + Rake + Bundler Python => (finally something...

The core issue is that Rubygems adds the `lib` directory of every gem to your path, so you end up calling stat a zillion times.

The actual time spent loading/parsing files is in most cases a tiny fraction of the startup time of any large project using rubygems and bundler.

I found the scheme environment too fragmented and lacked a decent equivalent of rubygems.

If RubyGems were hacked, progress might move slightly faster.

> PyPI or rubygems These are not activities which a web server does though.

* Integrating Rubygems was the dependency hell I was talking about.

Performance has been a major focus of every release since 1.9.1; integrating Rubygems considerably helped with tooling and dependency issues; encoding-aware strings were a major feature of 1.9; coroutines and generators can be implemented more effectively with 1.9's Fibers.

That is simply the fundamental nature of dependencies and will be true no matter which ecosystem you're working with, hence the ubiquity of package managers like npm, rubygems, composer etc.

I've had no shortage of troubles with Ruby gems: requiring on the git binary to build the gem (even in a release tarball), test suites not being included in the gem releases on rubygems.org, rampant circular dependencies, etc.

Installing it requires some amount of care and technical knowledge (don't even bother installing it with a Linux package manager -- you're almost guaranteed to end up with the "wrong version" of ruby and rubygems).

#foo.rb module Foo module Bar def biz return 10 end end end # main.rb require './foo' include Foo::Bar biz() # => 10 > don't even bother installing it with a Linux package manager -- you're almost guaranteed to end up with the "wrong version" of ruby and rubygems Because that's not the case for Python or PHP on linux too?

Existing package systems like Maven, Rubygems, NPM etc basically evolved to wire together a monolith at build time.

Rubygems has been lagging behind other packagers like Apt, RPM, NPM, and even newer things like Rust's Cargo.

You you should update to the latest version of Rubygems.