LazyVim From Scratch — What an 18-Month-Old Setup Video Still Gets Right

📌 Read this first

This video is from February 2025. That is unusual for this series, and it changes how it should be read.

None of that makes the video worthless — the opposite. The workflow it teaches (install bare, discover through the menu, add capability through Extras, configure only what annoys you) is unchanged and is the durable part. But if you follow the keystrokes literally you will hit differences within the first minute. Section If you install it today lists them precisely.

🎬 The premise 0:00

The opening is a parody of the genre it belongs to, and it earns the piece a lot of goodwill:

The pivot is the argument: that was true, and it stopped being true. Neovim core maintainers now ship kickstart projects, and beyond those sit full distributions — a ready-made setup with language servers, themes, completion, debuggers, AI integration and fuzzy pickers already wired together.

He states the standard objection without softening it — "overkill, hidden configuration, bloated" — and answers it with an appeal to opportunity cost rather than a rebuttal: "we don't all have years to wait, and honestly, if I had the luxury of Neovim users nowadays, I'd take it without blinking twice."

💾 Install, and the backup 1:42

The first practical instruction is the one most tutorials skip, and it is the correct one: back up before you clone. Four locations, not one:

# move the existing setup aside — all four, not just the config
mv ~/.config/nvim{,.bak}
mv ~/.local/share/nvim{,.bak}
mv ~/.local/state/nvim{,.bak}
mv ~/.cache/nvim{,.bak}

# then the entire installation
git clone https://github.com/LazyVim/starter ~/.config/nvim
nvim

On first launch, lazy.nvim installs the baseline set — bufferline, the Catppuccin theme, fzf-lua, gitsigns and others he describes as "almost considered a must these days", with the honest qualifier: "obviously it's all opinionated, but can be changed easily later."

A useful detail for anyone with an existing setup: his own ~/.config/nvim is a symlink into a dotfiles repo, so "deleting" it is safe by construction. That is the pattern worth copying, independent of LazyVim.

⚡ Startup time as the argument 2:42

This is where the review stops being a tour and starts being evidence.

After the first restart the status line reports 4 of 34 plugins loaded — because lazy.nvim defers the rest until an event actually needs them. Startup: 25 milliseconds.

He returns to the number three more times as the config grows, and the trajectory is the point:

⌨️ The leader-key discovery loop 3:52

The mechanism that makes a distro learnable is not documentation — it is that pressing the leader key shows you the map.

Space alone pops a command palette; from there, submenus for files, buffers, code, debugging, git and UI. Press f for files, then e for the explorer. Nothing memorised in advance.

The mappings he singles out:

His repeated advice is to read the mappings table in the docs at least once — "to see what resonates with you and match your workflow" — and it is well placed, because the discoverable menu shows you where things are, not that they exist.

🧩 Extras — the real feature 8:49

The demonstration that carries the piece. He opens a real work project — a Go-based Kubernetes controller — and finds syntax highlighting but no language server. Treesitter shipped with basic languages; Go is not among them.

The fix is :LazyExtras, a menu of bundled mini-packages. Each Extra is not a plugin but a set of plugins configured to work together:

:LazyExtras          " browse the catalogue
                     " lang.go bundles: mason, mini-icons, neotest,
                     " nvim-dap (debugger), lspconfig, and more
                     " press x to install, then restart

After the restart, gopls immediately flags a misplaced variable declaration, inline type hints appear as ghost text, and completion starts working. One keypress, one restart.

🔧 Config the sanctioned way 6:01

The customisation section answers the "hidden configuration" objection directly, and the method is more interesting than the specific tweaks.

He wants jj to exit insert mode. LazyVim already ships an empty keymaps.lua — "so that we can have a place for these settings without wondering where it's best placed." That is the distro's real contribution to configuration: not fewer options, but a sanctioned location.

Plugin overrides, done properly

To rebind mini.surround he creates lua/plugins/surround.lua rather than editing anything LazyVim owns — returning a table per Lua convention, following the "configuration recipes" section of the docs. The remap is from gsa to <leader>sa, and the payoff is that the new binding appears in the which-key menu automatically — the override participates in the discovery system rather than bypassing it.

He also demonstrates mini.files creating that file: navigate, type the name, press = to apply. "Like oil.nvim or some of the Neo-tree capabilities, just better."

🌿 Git, and one honest doubt 12:07

<leader>g opens git: blame, browse, commits, status, and LazyGit. He is positive about the picker-style status view — staging and unstaging by moving files left and right, in the same visual language as the file explorer.

Then he does something the genre usually avoids and registers a loss:

His resolution is LazyGit, now integrated, which he rates as "one of, if not the best git terminal interfaces". The endorsement-by-association — that DHH appeared on the author's show praising it — is weak evidence and presented as such.

🤖 AI, and what dated 17:19

Copilot goes in as an Extra (ai.copilot), authenticates with a one-time code, and immediately produces a working reconciler from a one-line comment. His observation about why it worked is the sharp one: the model "picks up the context in which it should work and doesn't only create a function, but also builds it correctly, according to how the controller works."

His stated reason for adopting it — "since GitHub's Copilot is free now" — was accurate in February 2025 and is the most obviously time-stamped line in the video.

⚖️ The distro argument 13:20

His conclusion is more restrained than the title suggests, and better for it:

Which turns the usual complaint inside out. The objection to distros is that they hide configuration; his experience is that a good default reduces the desire to configure at all. The measurement backs it: he never sacrificed the startup time he would have optimised for by hand.

🔄 If you install it today

Everything below was checked against the current LazyVim source and release history. These are the points where the video and reality now diverge.

🔍 Claims checked

💡 Key takeaways

1. The method survives, the specifics do not. 33 releases and two major bumps in eighteen months. Follow the approach, verify every keystroke against current docs.
2. Back up four directories, not one. ~/.config/nvim, ~/.local/share/nvim, ~/.local/state/nvim, ~/.cache/nvim.
3. Installed capability is not resident cost. Seven Extras added, startup unchanged at 27 ms — the lazy-loading thesis, demonstrated rather than claimed.
4. He publishes the variance. 25 → 40 → 29 → 27 ms rather than only the best figure. Disclosed noise is more credible than a clean number.
5. Discoverability is the distro's real feature. Press leader, read the menu. You do not need to know what exists before you can find it.
6. An Extra saves integration decisions, not downloads. Choosing an LSP client, test runner, DAP adapter and formatter — and making them agree — is where the months actually go.
7. A sanctioned config location beats fewer options. An empty keymaps.lua answers "where does this go" once, permanently.
8. Do not migrate your old config wholesale. His own buffer keys were still prefixed t from a tab workflow he had abandoned years earlier.
9. Overrides that register with which-key are the good kind. A remap that appears in the menu extends the discovery system; one that bypasses it creates private knowledge.
10. Commit lazyvim.json. It records which Extras are enabled and which migrations ran — it is what makes the setup reproducible. The video never says so.
11. He names what he lost. gc meant commit to him and means log in LazyVim. A curated-tool review reporting zero friction has not been used long enough.
12. The best default reduces the urge to configure. Not "hidden configuration" but configuration you stop wanting to do — with a cheap escape hatch when you do.
13. Check :LazyExtras rather than copying a two-year-old choice. Nine AI integrations now exist where the video shows one.

🔗 Resources & links

• LazyVim From Scratch To BEAST MODESource video — DevOps Toolbox, 19:17, February 2025
• LazyVim documentationKeymap tables and configuration recipes — the reference the video keeps pointing at
• LazyVim/LazyVim27,065 stars, Apache-2.0. Check the releases page before following any older tutorial
• LazyVim/starterThe scaffold cloned in the video — deliberately frozen since Dec 2024
• folke/lazy.nvimThe plugin manager underneath, and the reason startup stays flat
• jesseduffield/lazygit80,909 stars, MIT. Independent of LazyVim despite the shared prefix
• omerxx/dotfilesThe presenter's own configuration, referenced throughout

🕐 Timestamp index