Jean Boussier
Jean Boussier
Surprisingly the gains are much more modest on my M3: ``` == Encoding activitypub.json (52595 bytes) ruby 3.4.2 (2025-02-15 revision d2930f8e7a) +YJIT +PRISM [arm64-darwin24] Warming up -------------------------------------- after 2.761k i/100ms...
Sure. Sounds like a good idea. PR welcome.
Thank you so much @flori, I'll see with @hsbt
@flori thank you so much for arranging this.
> Is there a better way to do this? Not that I know off. I'm also quite surprised such complexity is needed. I think it might be because gems like...
What about eager loading though? By default Zeitwerk lazy load, which is great for development, but in production you absolutely want eager loading. For Rails applications this is fine because...
> So, lazy by default I'd be more comfortable with eager by default, and lazy in development only. Of course the issue being how to signal that? Because with lazy...
Thing is, I suspect most gems are small enough that lazy loading doesn't make a big difference. So I wonder if just defaulting to eager loading doesn't make more sense?...
> However, consider the compound effect when 30 dependencies of your project eager load at boot time. To be clear, in the context of a Rails app, having your dependencies...
> Agreed, when a gem gets to a later stage the user can always read up on Zeitwerk's README and configure eager loading themselves if needed, I'd argue that it's...