Well, there's a bit of work to do. See Ungoogled Chromium for an example of a stripped-down Chromium.
kogasa
It's based on Chromium.
In context, Microsoft has made it quite annoying over the years for users to keep using the browser they like. This is yet another nag in a long series.
"have to follow the standard for HTML"
Websites have historically been so godawful about complying with web standards that browsers had no choice but to support grossly non-standard code. Which then became standard. Now the vast majority of the web only works because of browser implementation details. So it's Chromium and Gecko and nothing else ever again.
I recommend Ungoogled Chromium if you have to pick a Chromium derivative. It's a solid browser with the spyware removed, rather than taped over and exchanged with Microsoft's own.
And that has to be just about one of the pettiest to distinctions known to man.
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 still built to write code. Yes text is code, but vim is not a text editor in general,
It's built to edit text, not just code. Yes, text is code, but Vim is a text editor in general.
The features are in the editor.
Once you put them there, yeah.
They are integrated with the editor.
Once you put them there, yeah.
Yes, it’s through plugins,
.
but they’re still part of the editor
..
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.
Vim is designed to edit code
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.
-- https://vimhelp.org/intro.txt.html#intro.txt
--
It has scripts for the sake of those scripts enabling integrated developer features.
Those features aren't enabled nor integrated. They're added to Vim at its extensibility points. Baseline vim doesn't have them.
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.
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.
IDEs are designed to support a software development workload. A text editor is designed to edit text files.
IntelliJ IDEA isn't really more generic than PyCharm. It's a Java IDE built on the generic IntelliJ platform. You can load different language plugins in both.