this post was submitted on 25 Oct 2023
1326 points (100.0% liked)
Programmer Humor
854 readers
1 users here now
Post funny things about programming here! (Or just rant about your favourite programming language.)
Rules:
- Posts must be relevant to programming, programmers, or computer science.
- No NSFW content.
- Jokes must be in good taste. No hate speech, bigotry, etc.
founded 5 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
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.
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"
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.
You can't run and debug things in vim, can you?
ladies please, you’re all beautiful
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 $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 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.
If it's a petty distinction, why not acknowledge what I'm saying and move on? What is the point of this conversation for you?
It's built to edit text, not just code. Yes, text is code, but Vim is a text editor in general.
Once you put them there, yeah.
Once you put them there, yeah.
.
..
@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.
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)