Sure. I meant moreso that this would be cheaper than Kagi while providing the same selection of models.
As for deepseek, I couldn't even sign up because my email domain is not on their whitelist. To just try it out for now I don't mind the increased cost.
Selling dev tools is ferociously hard, as partially evidenced by this thread talking about how changing anyone's development flow/tooling/process is also ferociously hard
I would guess dev tooling usually also falls into the "nice to have," or as my former CEO used to say "vitamins vs painkillers"
I've been using vim and neovim for over 15 years with many 10s of plugins and I can probably count on one or two hands when an update has caused problems.
Also use Arch for about as long.
It's so odd to me when someone says that updates break their vim or Arch frequently.
There are so many threads about it on /r/neovim that people have started to ask just which plugins actually work together cohesively without breaking [0], something that is not asked about for VSCode. Just go through their "Needs Help" flair and you'll see lots of issues [1]. For me, I also use tens of plugins but inevitably something breaks at least once every couple of weeks.
just use lazyvim[1] and be done with it! some people takes care of the compatibility and they are probably more competent than you (i mean a newcomer who starts writing their nvim config)
One of those threads is about lazy.nvim, not lazyvim. The other is a question about what to do after accidentally installing lazyvim with the wrong shell on windows, not about plugin updates breaking things.
Lazyvim is powered by lazy.nvim, at some point it'll break. These are example posts, you can feel free to go through reddit for more examples but yes Neovim does routinely break more for me than VSCode ever does, which is basically never.
it never has been my experience! i have used lazyvim distro for the last year or so and run some :Lazy update for time to time and usually i just need to close neovim and restart and it will all be working well..
I think i had an issue when they moved to conform.nvim from the deprecated language server based method but that's maybe about it (I deleted the nvim cache and it was all good after)
Your anecdote does not somehow counter dozens of others that clearly exist across the internet. Just because it works for you does not mean it works across the board.
I have! And I liked it! But Surfingkeys has 95% of the functionality of Tridactyl, but but does not need a troubleshoot guide like Tridactyl. Moreover, Surfingkeys implements a better search function on websites. With Surfingkeys, you also don't need to install an external application to work in input masks with Vim, as Surfingkeys has a Vim implementation on board that is completely sufficient for filling out input masks. I also like Surfingkeys' visual mode.
It's only hepatoxic at high doses. Taking 1 or 2 Tylenol a day is not going to cause any problems.