Jean Boussier

@deivid-rodriguez the problem isn't so much of defining a default, the problem is that the ideal state is to get both lazy loading in development and eager loading in production....

> Then should those other frameworks do the same as Rails? If they wish to be Zeitwerk aware then sure, but they may not want to? If the framework isn't...

> to make sure interested users evaluate beforehand what makes more sense for the gem they are about to create. Why I tried to explain is that what makes sense...

> are terms usually used for web applications like Rails or maybe applications that run continuously on some machine Yes. There are cases like CLIs where indeed, lazy loading can...

Yeah, I think lazy loading with a README note about what it means / what to do is probably the way to go.

> IMO I would love to see this added to Ruby somewhere. I don't see why not? We already have impl-specific things like `GC.stat`. I think the decision to ship...

Well, say you use `gvltools` with `GVLTools::GlobalTimer.monotonic_time`, that number represent the total amount of time spent waiting for the GVL. Say you have X threads, and you snapshot the monotonic...

> I'm still not sure what to do with that data though. Well, since the only thing you can know about a job before poping it is its queue, I...

I'd say the correct behavior would be for `first` to raise if there isn't an implicit order. Because right now it relies on whatever order the database returns which is...

So why not, but I think we could start by making the default better. This list was established 16 years ago in https://github.com/rails/rails/commit/eb39d0f7b999f09c4e13f035634887a8f5592443 I'm thinking we could exclude directories rather...