I have been on JetBrains Mono ever since it's release. I am getting FOMO from not using Berkely Mono, because it totally looks like something that would sit right with me.

> The folke/lazy.nvim is the most used plugin manager at the time of this writing. And rightly so: it is very capable with lots of features. Ironically, this itself makes it not very suitable to be a part of Neovim as most of the features come with significant code and maintenance complexity. Plus the whole idea of treating lazy loading as the main goal of a plugin manager does not sit well with Neovim core team.

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

I'd stick to lazy.nvim for now. Lazy loading is really neat and lazy.nvim's ability to specify plugin dependencies isn't something vim.pack has either.

I'd guess if you don't care about lazy loading and OK with just loading everything all the time - vim.pack is great to have as a built-in.

That's my impression too. However, I might give `vim.pack` a go for the novelty.

That being said, there is a way to lazy-load the plugins — Evgeni has a guide for that [1]. The "Load not during startup" variant is really simple with putting `vim.pack.add()` into `vim.schedule()`. The other myriad of options (keys, cmds, event) that lazy.nvim provides would require you to set up appropriate autocommands.

It gives me vibes of writing in Go. Everything is right there — builtin — but there's some verbosity to bear with.

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

Thanks for the pointer. I guess to simulate what lazy.nvim does with loading plugins based on user commands, you can use something like this:

``` vim.api.nvim_create_autocmd("User", ... ```

But it only solves the actual lazy part. Not sure how you can solve defining plugin dependency graph for such loading that lazy.nvim allows.

I can try experimenting with it anyway.

If you need to adjust cursor speed and want scroll behavior to differ between the TrackPad and a mouse, then I can vouch for LinearMouse [1]. It is free of charge and open-source, and perfectly covers my needs.

[1]: https://github.com/linearmouse/linearmouse

With JavaScript you could make it a three state toggle: light, dark, and auto. The last one would allow to to back to the default - no preference.

I thought this might use indeterminate checkbox, but that wouldn't be necessary. 'Light', 'dark', and lack of thereof in localStorage already amount to three distinct states.

It's already there in Firefox for Android! If you take a look at MDN, it states it's available since 121 that released on 2023-12-19.

In fact, I am using it right now, and the example works without issues.

ijq [1] is. I am using it almost every time I need to come up with a jq expression. However, it gets noticeably laggy with enormous JSONs.

[1]: https://sr.ht/~gpanders/ijq/

It looks like the README in jj repository does not do justice when it comes to available syntax for queries. jj uses gjson (by the same author) and its syntax [0]. From what I saw the first one can be handled with:

    jj 'data.#(age<=25)#' -i input.json

I don't think there is a way to sort an array, though. However, there is an option to have keys sorted. Personally, I don't think there is much annoyance in that. One could just pipe jj output to `sort | uniq -c`.

I just discovered that gjson supports custom modifiers [1]. So technically, you could fork jj, and add another file registering `@sort` modifier via `gjson.AddModifier` and have a custom jj version supporting sorting.

[0]: https://github.com/tidwall/gjson/blob/master/SYNTAX.md

[1]: https://github.com/tidwall/gjson/blob/master/SYNTAX.md#modif...

It is the same conference! They have rebranded this year to Neovim conf [0]. The conference however is not exclusive to Neovim content.

[0]: https://www.neovimconf.live/rebranding-rationale

That's confusing to say, at best.

If it's called VimConf, I could understand including content from anything vim related, even vi or neovim stuff (or from the other forks/variations/bases).

But if it's called NeovimConf, I wouldn't expect that to include the entire Vi ecosystem.

According to the FAQs they rebranded because all the traditional vim people complained about too much neovim content.

Apparently the neovim people are more chill about it.

The neovim people are even chill about Emacs evil-mode content.

Most VIM stuff works in NeoVIM as well. NeoVIM exclusive stuff doesn’t work as well or at all in VIM.

That will be changing soon. Vim 9 has a new version of Vimscript (called Vim9script) which Neovim doesn't support, and its APIs for things like async jobs are also different. However Vimscript itself will probably remain a common denominator for many years to come.

TJ DeVries (one of the Neovim contributors, and a frequent streamer) was working on some sort of vim9 translation support for Neovim. Seems more like a side project rather than something that will be built into Neovim, though.

https://github.com/tjdevries/vim9jit