Lazy as default

[e-roux]

Hello,
a minor point... it's called Lazy but lazy=false as a default. Any reason apart to make a transition from packer and other pkg manager smooth ?

[folke]

I don't fully understand your question, but are you asking on how to migrate from Packer?

You can check the docs on that here https://github.com/folke/lazy.nvim#packernvim

[e-roux]

Sorry for being unclear. I migrated and everything is ok, I quite like the plugin! 👍🏼

https://github.com/folke/lazy.nvim/blob/main/lua/lazy/core/config.lua#L9 -> lazy=false as a default value. As the plugin name is "lazy", I was wondering why the default is not lazy=true.

[folke]

because lazy=true requires the user to make sure all plugins have proper lazy-loading handlers

[e-roux]

Sure, users are confronted to a wider configuration of handlers in that case. Globally lazy loaded plugins is one of the features (hence its name I guess) so I would have expected lazy=true as default because it's consistent to what is expect from it: it's not Packer, it's Lazy and things are done another way. But I understand that setting it to false is user-friendly and allow a smooth transition from other pkg manager.

[ryuheechul]

I agree with folke's comment and I'm against lazy=true being default despite it sounded intuitive at first, the consequences are that nothing loads by default unless you properly add lazy-loading conditions. Which will make migrations (to resemble the similar state of using the previous plugin manager) take a lot longer and harder.

Besides, even with lazy=false it still improved startup time a lot. (from ~700ms to ~200ms)

I think what's good to have is to be able to switch this behavior quickly so I used 'env' to do that - (this is also entire diff for the migration from packer)

Now running with vi is with lazy=false and vil is with lazy=true which allow me to lazify on my own leisure instead of having to lazify my entire packages which will take long time since it's a category of a optimization that doesn't have an easy answer.

[e-roux]

This is clear that lazy=true requires a "little" bit more configuration! But in case lazy=trueas default, it's always possible to do for quick migration:

require("lazy").setup({}, {lazy=false})

It's not an important point, in my case, I pass lazy=true and it's fine. As I said, just wanted to point out a kind of "inconsistency" (this is only my opinion) between one of the technical highlights of the project and its associated default value.

[ryuheechul]

I hear you. {lazy=true} possibly better default (in case to endorse laziness) for people who are also fresh starters didn't have anything to migrate over (or previous syntax were entirely foreign so have to put a lot of effort anyway - in case with non-packer plugin manager). {lazy=false} is potentially less frustrating and mysterious for people who need to migrate from existing non-lazy setup.

I feel:

• {lazy=true} is more consistent default especially the plugin name itself is lazy.
• {lazy=false} is a compromise for a good reason.

I favor the compromise for the ease of migration. But I understand people will favor different default depends on what they care/prefer.

At the end of the day, as you said it's just easy as just one boolean flip though 😃 .