STOP USING NEOVIM

Comments · 310

• DA

  @dacctal · 1 day ago (edited) · pinned

  little disclaimer:<br><br>that logo i used to represent vis isn&apos;t exactly THE vis logo.<br>vis technically doesn&apos;t even have a logo, but there was a thread on a github issue which has what seems to be the most popular logo for it.<br>i couldn&apos;t get an SVG for the logo, so i had to make-do and create my own as close as possible to the original.<br><br>here&apos;s the issue: <a href="https://github.com/martanne/vis/issues/328">https://github.com/martanne/vis/issues/328</a>

  100

• 3E

  @3eyedgod · 5 hours ago

  &quot;abandon the mainstream tool for the obscure one&quot; performs well as a video and rarely survives as a daily driver.

  139

• XE

  @Xenomorphy000 · 6 hours ago

  While I do agree with most points made here, especially the issue with the community itself, I think it&apos;s bad faith not to point out the fact that you don&apos;t <b>need</b> a single one of those issues to be present with your neovim experience to have a good code editor. My entire config is one 244 line file. That is everything from editor settings to keybinds to autocommands to plugins and their settings in one file. The backend might be bloated but the user doesn&apos;t see or feel that.

  75

• CH

  @Choogey · 1 day ago

  This might get me to switch. From nano 😂

  120

• OG

  @oglothenerd · 3 hours ago

  Fun fact: the reason the base set of 16 terminal colors cannot do orange is because they are 3-bit BGR colors with a 4th bit for the brightness.

  10

• TO

  @tony-btw · 14 hours ago

  Vis(ionary)

  83

• OH

  @oh8rs · 1 day ago

  I do love nvim, but I have basically 7 plugins and lazy so Im not exactly ricing it.<br><br>That being said, vis does seem more refined from this introduction. <br><br>I think I like the regex changes, multicursor, and some of the other opinionated choices the creators have made! <br><br>All that said, Im not sure I can currently be convinced to leave the ecosystem - even with my tiny config. Like helix, vis just isnt mature enough (especially the community) for me to swap, but people like yourself will hopefully change that.<br><br>I may reconsider (and research some more) in the future, however. This seems like it could be a genuine joy to use, with a little more time and development.<br><br>Thanks for the video!

  52

• MO

  @moussaadem7933 · 7 hours ago (edited)

  tried it a few years ago, it&apos;s wayyy too limited for anything beyond simple text editing.<br><br>i really admire the clean design however, the project doesn&apos;t have to deal with the historical constraints on vim and neovim<br><br>Edit: it has a scripting API and builtin LSP support now ? fine, i will check it out again

  21

• C4

  @C4_Shaf · 5 hours ago (edited)

  That video will not stop me from using Neovim.<br><br>I agree that it&apos;s bloated, but the main reason it is, is for retro-compatibility. If Neovim were &quot;supposed&quot; to be entirely built in Lua, which is a great idea, that would sacrifice the retro-compatibility. So no, I don&apos;t agree when dacctal says that &quot;this is what Neovim should have been&quot;, because Neovim is about being fully compatible with vim. Not being a brand new thing built from scratch.<br><br>vis is an awesome project, but far from being as mature as Neovim. I&apos;ll follow it until it&apos;s ready, and then I would decide if it&apos;s better to ditch Neovim for vis, or Neovim is just fine on its own.

  5

• DR

  @DreamerTheBurp · 7 hours ago

  Vis is good, but ive been resting with helix and never been happier.

  61

• RO

  @Rocksy7 · 8 hours ago

  Tsoding reference

  128

• TA

  @taeliantalittia612 · 4 hours ago

  That&apos;s it. Someone has to fork Kate into a terminal app and call it Kiramman.

  1