8 ms·

More that you want to carve a bowl out of wood. Vim is like a knife that with some modifications you can turn into a carving knife. VSCode is like a chainsaw th

More that you want to carve a bowl out of wood. Vim is like a knife that with some modifications you can turn into a carving knife. VSCode is like a chainsaw that has attachments that have been made for it and it also has bowl carving attachment. If you don't know your tools, then you can easily mess the knife modification and not end up with a carving knife. The chainsaw with ready made attachments is way easier to get going, but in return you have to carry the chainsaw with you and if there are any problems with the tool itself you probably aren't going to be able to fix or modify it yourself. So it is more like trading initial speed with more precision, but also being able to do more after the initial learning curve.

p-e-w 3y ago
> The chainsaw with ready made attachments is way easier to get going, but in return you have to carry the chainsaw with you and if there are any problems with the tool itself you probably aren't going to be able to fix or modify it yourself. This is where your analogy breaks down for me. The "chainsaw" (VSCode) is absolutely perfect for the tasks I'm using it for. When I write Python code, the Python extension gives me exactly what I want. That's because the environment it creates has been fine-tuned based on feedback from thousands of users with similar requirements to my own. There's no need for me to modify anything, any more than I modify my car or my trousers. It's simply ready for me to do professional work, and whenever I have special requirements, I know that I will find an extension that caters to them also. I don't need or want to reinvent a wheel that has been invented hundreds of times already, and polished to perfection through more man-hours than I could ever hope to invest myself.
- nextlevelwizard 3y ago
  It does not break down. Chainsaw is very good at doing chainsaw things. If what you need to do is cut down bunch of trees then chainsaw is exactly what you need. No one in their right minds would start with a knife and start building it into a saw and then attach a motor to motorize it. Mind you we were carving a bowl, but as per Internet argument you completely dismissed the use case and inserted your own. If VSCode does exactly what you need out of the box exactly how you want it to do it, then you are set and you should use VSCode.
  - jahsome 3y ago
    I can think of a few YouTubers who would and probably have done just what you described. Now that I say that though, I realized you used the phrase "right mind" and I don't think I'd count many if any in that cohort.
  - oblio 3y ago
    The problem is that Vim can be used to create config files and source code files among other things. VS Code can be used for very much the same things. The output of both tools is practically the same thing. The niche of things Vim can do and VS Code can't is tiny and constantly decreasing.
    - skydhash 3y ago
      It's always been like this. Vim is an editor, and so is Sublime Text, Emacs, VS Code, Geany, Kate, Notepad++, and more. What sets vim apart is its ubiquity (it's been on every Linux box I touched) and its philosophy of editing text (modal editing). Apart from that, it's a matter of preferences and practicality.
      - slowmovintarget 3y ago
        Emacs is a lisp environment, with an editor housecoat on.
    - xcxcx 3y ago
      You can run Neovim on a remote server through ssh. I think that's the main difference
      - oblio 3y ago
        VSCode can do that with the remote extensions.
        xcxcx 3y ago
        Sorry, I meant from the terminal
- xeyownt 3y ago
  You get exactly the same functionality with (neo)vim plugins. Only difference is that because vim has been open-source for decade, there are many many more plugins, and hence the choice is harder to make. VSCode also helped improve the (neo)vim experience (e.g. language servers) Comparing VSCode and Vim is like comparing a standard calculator with an RPN one.
  - p-e-w 3y ago
    > Only difference is that because vim has been open-source for decade, there are many many more plugins No, the main difference is in the quality of plugins, not in how many there are. For example, Rust-Analyzer provides an official VSCode extension, which is professionally maintained by members of the Rust core team. The extension is part of the Rust-Analyzer project itself, and can be installed with a single click, at which point it just works. For Vim, you have to manually download (and update) the Rust-Analyzer binary, install a third-party plugin, configure them to work together, and hope (1) that the whole thing doesn't break when the plugin or the language server is updated, and (2) that this concoction provides a tiny fraction of the functionality that the official VSCode extension does.
    - jahsome 3y ago
      I'm a vim user, but only because of the keybinds. I use VS code an equal amount because I often get too frustrated trying to wire the disparate vim tools. The never ending fiddling and 30-step process to get the equivalent of one click in vs code is exhausting. The people who _enjoy_ the toil seem to truly struggle to comprehend that someone might not want to spend hours upon hours learning how to get things working, only to immediately forget.
      - UltLRS 3y ago
        There is a vim plugin for VS code. It gives you vim keybindings. https://marketplace.visualstudio.com/items?itemName=vscodevim.vim https://marketplace.visualstudio.com/items?itemName=vscodevi...
      - 3y ago
- palata 3y ago
  > This is where your analogy breaks down for me. The "chainsaw" (VSCode) is absolutely perfect for the tasks I'm using it for. Then just use the chainsaw... and accept that the knife may be absolutely perfect for the tasks of somebody else.
DropInIn 3y ago
Nah vs code is a multitool with both a hook blade (the knife younuse for carving out a bowl) And a chainsaw.... Slightly more unwieldy in that specific narrow use case than a plain hook knife but you don't need a second tool to cut the log you take the wood for the bowl from... In other words, it's a tool that let's you do near anything with minimal modifications whereas vim is a tool that requires significant modification just to do Any task other than looking at it.

p-e-w 3y ago

> The chainsaw with ready made attachments is way easier to get going, but in return you have to carry the chainsaw with you and if there are any problems with the tool itself you probably aren't going to be able to fix or modify it yourself. This is where your analogy breaks down for me. The "chainsaw" (VSCode) is absolutely perfect for the tasks I'm using it for. When I write Python code, the Python extension gives me exactly what I want. That's because the environment it creates has been fine-tuned based on feedback from thousands of users with similar requirements to my own. There's no need for me to modify anything, any more than I modify my car or my trousers. It's simply ready for me to do professional work, and whenever I have special requirements, I know that I will find an extension that caters to them also. I don't need or want to reinvent a wheel that has been invented hundreds of times already, and polished to perfection through more man-hours than I could ever hope to invest myself.

nextlevelwizard 3y ago
It does not break down. Chainsaw is very good at doing chainsaw things. If what you need to do is cut down bunch of trees then chainsaw is exactly what you need. No one in their right minds would start with a knife and start building it into a saw and then attach a motor to motorize it. Mind you we were carving a bowl, but as per Internet argument you completely dismissed the use case and inserted your own. If VSCode does exactly what you need out of the box exactly how you want it to do it, then you are set and you should use VSCode.
- jahsome 3y ago
  I can think of a few YouTubers who would and probably have done just what you described. Now that I say that though, I realized you used the phrase "right mind" and I don't think I'd count many if any in that cohort.
- oblio 3y ago
  The problem is that Vim can be used to create config files and source code files among other things. VS Code can be used for very much the same things. The output of both tools is practically the same thing. The niche of things Vim can do and VS Code can't is tiny and constantly decreasing.
  - skydhash 3y ago
    It's always been like this. Vim is an editor, and so is Sublime Text, Emacs, VS Code, Geany, Kate, Notepad++, and more. What sets vim apart is its ubiquity (it's been on every Linux box I touched) and its philosophy of editing text (modal editing). Apart from that, it's a matter of preferences and practicality.
    - slowmovintarget 3y ago
      Emacs is a lisp environment, with an editor housecoat on.
  - xcxcx 3y ago
    You can run Neovim on a remote server through ssh. I think that's the main difference
    - oblio 3y ago
      VSCode can do that with the remote extensions.
      - xcxcx 3y ago
        Sorry, I meant from the terminal
xeyownt 3y ago
You get exactly the same functionality with (neo)vim plugins. Only difference is that because vim has been open-source for decade, there are many many more plugins, and hence the choice is harder to make. VSCode also helped improve the (neo)vim experience (e.g. language servers) Comparing VSCode and Vim is like comparing a standard calculator with an RPN one.
- p-e-w 3y ago
  > Only difference is that because vim has been open-source for decade, there are many many more plugins No, the main difference is in the quality of plugins, not in how many there are. For example, Rust-Analyzer provides an official VSCode extension, which is professionally maintained by members of the Rust core team. The extension is part of the Rust-Analyzer project itself, and can be installed with a single click, at which point it just works. For Vim, you have to manually download (and update) the Rust-Analyzer binary, install a third-party plugin, configure them to work together, and hope (1) that the whole thing doesn't break when the plugin or the language server is updated, and (2) that this concoction provides a tiny fraction of the functionality that the official VSCode extension does.
  - jahsome 3y ago
    I'm a vim user, but only because of the keybinds. I use VS code an equal amount because I often get too frustrated trying to wire the disparate vim tools. The never ending fiddling and 30-step process to get the equivalent of one click in vs code is exhausting. The people who _enjoy_ the toil seem to truly struggle to comprehend that someone might not want to spend hours upon hours learning how to get things working, only to immediately forget.
    - UltLRS 3y ago
      There is a vim plugin for VS code. It gives you vim keybindings. https://marketplace.visualstudio.com/items?itemName=vscodevim.vim https://marketplace.visualstudio.com/items?itemName=vscodevi...
    - 3y ago
palata 3y ago
> This is where your analogy breaks down for me. The "chainsaw" (VSCode) is absolutely perfect for the tasks I'm using it for. Then just use the chainsaw... and accept that the knife may be absolutely perfect for the tasks of somebody else.

DropInIn 3y ago

Nah vs code is a multitool with both a hook blade (the knife younuse for carving out a bowl) And a chainsaw.... Slightly more unwieldy in that specific narrow use case than a plain hook knife but you don't need a second tool to cut the log you take the wood for the bowl from... In other words, it's a tool that let's you do near anything with minimal modifications whereas vim is a tool that requires significant modification just to do Any task other than looking at it.