Vim is absolutely not an IDE. It has no integrations with any language. It’s just a powerful text editor. You can add language plugins and configure it to be an IDE.
That’s what most IDEs are. VS Code doesn’t have any native integrations. Everything is provided by plugins. The default plugins that ship with VS Code can be disabled, and you’ll have just a powerful text editor.
(To do this, go to Extensions tab, click the filter icon, select “Built-in”, and go down the list to disable all of them. Or just build a version with no built-in plugins.)
In that case every IDE is “just a text editor” because basically every IDE is built around modularity in this same way. This is just nitpicking over what is preinstalled.
Eclipse, visual studio, pycharm, idea… Those are full blown IDEs. They come with all the extras. All the text editors that can become IDEs have extensions or plugins that enable what these other actual IDE do natively.
Nowadays using vscode to debug a running program is common, but that was something only restricted to full blown IDEs some years ago, I’d say that vscode is lightweight IDE that can be expanded, but vim is a text editor first and foremost. You can’t really debug code in vim AFAIK, the most you get is syntax highlighting, linting, automatic whitespace removal and auto formatting? Not sure about the last one.
No offense intended here - But why is this being upvoted?
vim absolutely is an IDE if that is how you want to use it. Syntax highlighting, linter, language specific autocomplete, integrated sed/regex. And much, much more.
The things you’re describing are still just text editor features. An IDE generally has specific functionality for building, testing, packaging, debugging etc. for one or more programming languages/environments.
(Which vim can do if configured, I don’t really have an opinion about that tbh)
Syntax highlighting, linting, and language specific autocomplete are features supported by plugins and scripts. Plain, simple vim is a powerful extensible text editor. The extensibility makes it easy to turn into an IDE.
Yeah, there is a generic syntax highlighting scheme. I had forgotten because it’s not very good for some languages, I’d replaced it with a LSP-based implementation years ago.
I’m not a text editor. But anyway, would you call a shell script that invokes python.exe $1 a Python IDE? Why would you? Vim isn’t designed to facilitate the use of vimscript, vimscript is just an extensibility feature of Vim.
Vim isn’t designed to facilitate the use of vimscript, vimscript is just an extensibility feature of Vim.
Vim is designed to edit code, by the people who were doing it back in the 70s and all of its features are there to enable better, faster, and more efficient editing.
It has scripts for the sake of those scripts enabling integrated developer features. Because they’re part of vim they’re in the environment and the program is used predominantly for development.
To edit text files. It doesn’t matter if it’s code, configuration files, or plaintext. There are no interpreters, no compilers, no debuggers, nothing designed to support any particular framework or language or workflow. All of that is possible to add through the extensibility features.
Vim is a highly configurable text editor built to make creating and changing any kind of text very efficient.
Vim is an advanced text editor that seeks to provide the power of the de-facto Unix editor ‘Vi’, with a more complete feature set.
Vim is a highly configurable text editor built to enable efficient text editing.
Vim is a text editor which
includes almost all the commands from the Unix program “Vi” and a lot of new
ones. It is very useful for editing programs and other plain text.
Those features aren’t enabled nor integrated. They’re added to Vim at its extensibility points.
And that has to be just about one of the pettiest to distinctions known to man.
It’s still built to write code. Yes text is code, but vim is not a text editor in general,. It’s made for programmers, nobody else is crazy enough to learn such obtuse syntax or want to have a developer with a scripting language built into it.
The features are in the editor. They are integrated with the editor. Yes, it’s through plugins, but they’re still part of the editor instead of part of some different program.
The word integrated literally just means you don’t go into some other program to run your build.
It’s an integrated environment for development.
It’s an IDE!
It has debuggers.
It has syntax highlighting
It has compiling.
Even if you have to install them as plugins, it’s designed to be doing all of those things.
@kogasa Hehe, shit, so long done something wrong as I use #vim as an IDE. Okay, some own helpers, some plugins, the direct integration for #golang via LSP and since some time also ChatGPT and Copilot. But hey, it’s no IDE. 🤪
Like I said, Vim can be made into an IDE by adding and configuring plugins. Basic barebones vim is designed to be a powerful, extensible text editor, not an IDE.
Word is a WYSIWYG editor. We don’t talk about it much these days because it’s just how things are done, but it took a long time for the industry to come up with a way to display text on screen with rich formatting and have it come out the same way in print. There was a lot of buzz around it in the late 80s and early 90s.
Word solves a completely different problem than an IDE. Notepad is a raw, minimal tool that could be built on for either WYSIWYG or an IDE.
Vim really is an IDE, not a text editor. It’s usable as an editor but overkill.
Nano serves a difference purpose. It’s like telling someone on a bike that a mustang is better.
Vim is absolutely not an IDE. It has no integrations with any language. It’s just a powerful text editor. You can add language plugins and configure it to be an IDE.
That’s what most IDEs are. VS Code doesn’t have any native integrations. Everything is provided by plugins. The default plugins that ship with VS Code can be disabled, and you’ll have just a powerful text editor.
(To do this, go to Extensions tab, click the filter icon, select “Built-in”, and go down the list to disable all of them. Or just build a version with no built-in plugins.)
Sure, and VSCode without any plugins is a text editor, not an IDE.
In that case every IDE is “just a text editor” because basically every IDE is built around modularity in this same way. This is just nitpicking over what is preinstalled.
Eclipse, visual studio, pycharm, idea… Those are full blown IDEs. They come with all the extras. All the text editors that can become IDEs have extensions or plugins that enable what these other actual IDE do natively.
Nowadays using vscode to debug a running program is common, but that was something only restricted to full blown IDEs some years ago, I’d say that vscode is lightweight IDE that can be expanded, but vim is a text editor first and foremost. You can’t really debug code in vim AFAIK, the most you get is syntax highlighting, linting, automatic whitespace removal and auto formatting? Not sure about the last one.
You cannot remove java from idea. Therefore it is not just a text editor because support for the language isn’t added through an extension
IDEs are designed to support a software development workload. A text editor is designed to edit text files.
Ah, so Code is the same as Vim if… I go out of my way to either disable things on one or install things on the other.
Or… Or… Code is an IDE (that you can strip down) and Vim is a text editor (that you can strip up).
We don’t stop calling a computer one just because it can still boot without most of its modules. The default presentation matters.
No offense intended here - But why is this being upvoted?
vim absolutely is an IDE if that is how you want to use it. Syntax highlighting, linter, language specific autocomplete, integrated sed/regex. And much, much more.
“You see here my car has positions for all the parts of a boat so it’s easily made into a boat and it’s already waterproof but it’s just a normal car”
The things you’re describing are still just text editor features. An IDE generally has specific functionality for building, testing, packaging, debugging etc. for one or more programming languages/environments.
(Which vim can do if configured, I don’t really have an opinion about that tbh)
Syntax highlighting, linting, and language specific autocomplete are features supported by plugins and scripts. Plain, simple vim is a powerful extensible text editor. The extensibility makes it easy to turn into an IDE.
There’s syntax highlighting by default in vim though.
Yeah, there is a generic syntax highlighting scheme. I had forgotten because it’s not very good for some languages, I’d replaced it with a LSP-based implementation years ago.
ladies please, you’re all beautiful
You can’t run and debug things in vim, can you?
It literally has a built in scripting language.
So it’s an IDE for vimscript…? No.
You’re not a normal text editor if you have a built in scripting language.
I’m not a text editor. But anyway, would you call a shell script that invokes
python.exe $1a Python IDE? Why would you? Vim isn’t designed to facilitate the use of vimscript, vimscript is just an extensibility feature of Vim.Vim is designed to edit code, by the people who were doing it back in the 70s and all of its features are there to enable better, faster, and more efficient editing.
It has scripts for the sake of those scripts enabling integrated developer features. Because they’re part of vim they’re in the environment and the program is used predominantly for development.
To edit text files. It doesn’t matter if it’s code, configuration files, or plaintext. There are no interpreters, no compilers, no debuggers, nothing designed to support any particular framework or language or workflow. All of that is possible to add through the extensibility features.
https://vim.org/
– https://vimhelp.org/intro.txt.html#intro.txt
–
Those features aren’t enabled nor integrated. They’re added to Vim at its extensibility points. Baseline vim doesn’t have them.
And that has to be just about one of the pettiest to distinctions known to man.
It’s still built to write code. Yes text is code, but vim is not a text editor in general,. It’s made for programmers, nobody else is crazy enough to learn such obtuse syntax or want to have a developer with a scripting language built into it.
The features are in the editor. They are integrated with the editor. Yes, it’s through plugins, but they’re still part of the editor instead of part of some different program.
The word integrated literally just means you don’t go into some other program to run your build.
It’s an integrated environment for development.
It’s an IDE!
It has debuggers.
It has syntax highlighting
It has compiling.
Even if you have to install them as plugins, it’s designed to be doing all of those things.
i don’t care if vim is an text editor or ide but i just wanted to ask if they even had debugger back when vim was created ?
Yea, vim really isn’t anything near how useful emacs is.
Emacs really is powerful, all it needs now is a decent text editor.
It has one. It’s called evil-mode.
@kogasa Hehe, shit, so long done something wrong as I use #vim as an IDE. Okay, some own helpers, some plugins, the direct integration for #golang via LSP and since some time also ChatGPT and Copilot. But hey, it’s no IDE. 🤪
Like I said, Vim can be made into an IDE by adding and configuring plugins. Basic barebones vim is designed to be a powerful, extensible text editor, not an IDE.
It’s designed to be an extended vi clone above anything else.
Nano is for those that occasionally edit text files from a terminal.
Vim is for those who make a living out of it.
So like Word vs Notepad?
Not really, or that doesn’t feel right to my. Word and notepad basically still do the same thing except for that word lets you add style.
Like a manual vs an automatic car, maybe?
Word is a WYSIWYG editor. We don’t talk about it much these days because it’s just how things are done, but it took a long time for the industry to come up with a way to display text on screen with rich formatting and have it come out the same way in print. There was a lot of buzz around it in the late 80s and early 90s.
Word solves a completely different problem than an IDE. Notepad is a raw, minimal tool that could be built on for either WYSIWYG or an IDE.
More like Visual Studio Vs Notepad
For the pedants, I hope y’all can at least agree that lunarvim is an IDE:
https://www.lunarvim.org/
(Note, a comment saying it’s a “bad IDE” doesn’t make it not an IDE)