I switched to Vim – and it took me only 6 years to learn it

Re:I switched to Vim – and it took me only 6 years to learn it by ilrwbwrkhv on Sunday June 23, 2024 @05:47PM (#40770861)

Only problem is that vim doesn't work with LSP. It is a broken tool.

Easy check proving absolutely that it is broken:

1. Create a new wails project with `wails init -n myproject -t svelte-ts` 2. Create a svelte file and use a function defined in app.go 3. Run `wails dev` to compile and run the app 4. Delete the function from app.go

Result: The svelte file which imports the function generated from app.go doesn't show any errors even thought the function doesn't exist anymore.

So use VS Code or Sublime which actually work with LSP without issues.

Don't use broken tools for your work.

[ Parent | on HN ]

Re:I switched to Vim – and it took me only 6 years to learn it by naught0 on Sunday June 23, 2024 @06:13PM (#40771046)

It sounds like something broken with this specific workflow. I use LSP features in typescript and python daily without issue.

Don't use a tool that's broken for your work. There are plenty of bugs in other editors

[ Parent | on HN ]

Re:I switched to Vim – and it took me only 6 years to learn it by ilrwbwrkhv on Sunday June 23, 2024 @06:49PM (#40771287)

VS Code has no bug which is not also in Neovim. So VS Code is the best of the lot.

[ Parent | on HN ]

Re:I switched to Vim – and it took me only 6 years to learn it by xigoi on Monday June 24, 2024 @05:19AM (#40773937)

Bugs are not the only thing that matters. VSCode is way slower than (Neo)Vim, uses more memory, contains proprietary parts and lacks many of (Neo)Vim’s features.

[ Parent | on HN ]