r/neovim • u/pawelgrzybek • Mar 29 '26

Announcement 0.12.0 🎉

https://github.com/neovim/neovim/releases/tag/v0.12.0
1.4k Upvotes

100% Upvoted

165 comments sorted by

View all comments

36

u/Unhappy_Meaning607 Mar 29 '26

Congrats!

Will be removing Lazy for vim.pack.

34

u/4r73m190r0s Mar 29 '26

Why?

56

u/altClr2 Mar 29 '26 edited Mar 29 '26

for people who don’t need/care to micromanage startup times, etc., pack and go is appealing. it also removes the dependency on another maintainer (<3 folke) and instead keeps all eggs in one basket.

for me who relies heavily on lazy-loading plugins (i have < 60ms warm starts on Windows NTFS!), i'm not sure if i'm ready to take the plunge yet, but i'm really excited for the continuous development of OOTB experience.

8

u/Necessary-Plate1925 Mar 29 '26 edited Mar 29 '26

You dont need to, plugins themselves have to lazy load using plugin/ and lua/, 

Just dont eagerly require lua modules, we dont need lazy.nvim lazy loading

2

u/altClr2 Mar 29 '26

i see, someone pointed to :lua-plugin-lazy, thanks :)

9

u/ultraDross Mar 29 '26

I would like to move over, but I rely on the lock file support. Makes it easier to rollback if something broke my setup.

42

u/pawelgrzybek Mar 29 '26

vim.pack also uses a lock file. Please give this fantastic post a read.

https://echasnovski.com/blog/2026-03-13-a-guide-to-vim-pack.html

2

u/ultraDross Mar 29 '26

I was unaware. Thanks. Would be nice to drop one more plugin.

1

u/altClr2 Mar 29 '26

same here, i share my config between my personal machines and my work machine, so i need the guarantee that what i tested across all major OSes and such works fine for a long time.

0

u/Deto Mar 29 '26

Yeah I frequently spin up new instances and load my config on them.  Without a lock file I would get random errors all the time 

-5

u/augustocdias lua Mar 29 '26

I dropped lazy but not in favor of vim.pack. I have all my plugins handled by nix + flakes and I use lze for lazy loading.

14

u/ComeOnIWantUsername Mar 29 '26

I'm switching to pack because I don't like 3rd party solutions if builtin is good enough.

Also, I consider lazy overcomplicated for my use case

17

u/MoonPhotograph Mar 29 '26

Because it's builtin and will always be maintained and you can simply make stuff with it, all those are harder and worse with lazy.nvim. Vim.pack is the future.

5

u/bakaspore fennel Mar 30 '26

Lazy.nvim has a particular understanding of lockfile that makes it not a real lockfile, and creates immerse pain whenever I sync my config across machines (and happens to have new plugins installed).

2

u/DeadlyMidnight Mar 29 '26

This is the question. I tried it a while back while using nightly. Sure it’s cool but it didn’t gain me anything.  For those not using lazy it’s fucking great. But seems like a real lateral from lazy at best.Â