<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0">
  <channel>
    <title>Giovanni&#39;s (@gla@mastodon.social) bookmarks posts</title>
    <link>https://betula.tail3c2d2c.ts.net</link>
    <description>All public posts are sent to this feed.</description>
    <pubDate>24 Apr 26 12:11 UTC</pubDate>
    <item>
      <title>From lazy.nvim to vim.pack</title>
      <description><![CDATA[
<h2><a href="https://fredrikaverpil.github.io/blog/2026/04/15/from-lazy.nvim-to-vim.pack/">From lazy.nvim to vim.pack</a></h2>
<p>🔗 <a href="https://fredrikaverpil.github.io/blog/2026/04/15/from-lazy.nvim-to-vim.pack/">fredrikaverpil.github.io/blog/2026/04/15/from-lazy.nvim-to-vim.pack</a></p>
<p>🏷 <a href="/tag/lazy.git">lazy.git</a>, <a href="/tag/nvim">nvim</a>, <a href="/tag/packages">packages</a>, <a href="/tag/vim.pack">vim.pack</a></p>
<article class="mycomarkup-doc">
	<p>
		Background I’ve been using the excellent lazy.nvim package manager for more than three years now, and I’ve been super happy with it. But with Neovim v0.12.0, vim.pack was shipped: a built-in (but still experimental) plugin manager that manages plugins using Git, with no third-party dependencies required, implemented by Evgeni Chasnovski (see neovim/neovim#34009), known for his work on mini.nvim. This piqued my interest, as I’ve found myself creating abstractions and isolations with lazy.nvim that don’t harmonize with my grug brain. So I figured I wanted to see if I could simplify by moving onto vim.pack.
	</p>
</article>

]]></description>
      <author>ubnt</author>
      <link>https://fredrikaverpil.github.io/blog/2026/04/15/from-lazy.nvim-to-vim.pack/</link>
      <pubDate>22 Apr 26 13:48 UTC</pubDate>
    </item>
  </channel>
</rss>
