Yeah, like many others I maintain my configuration files in Git, so having to use files to configure is a pro, not a con, at least for me! I haven't been using VS Code but this sole factor might be the reason I will reconsider using it in the future.

Some might say having both manual configuration and automated dialog would be better, but many such interfaces ruin the structures of my intentionally organized setting files. I will take no GUI than misbehaving GUI at any time.

This is one of the things I really like about VC, they just implemented their config editing largely the way they support any language: just a json-file (but with comments) which has full-blown intellisense, and offers you a complete example of the defaults side-to-side with clear examples and explanations.

It also allows you to override certain settings per project/directory, which can then easily be included in git (like files to exclude from the file view for a specific project, path/tool settings, indentation settings, ...)

To your point, Atom allows both. Don't like the UI? Just edit config.cson or whatever directly! You're not locked into it.

I just find that if I have to go through a LOT more steps without a UI.

I would rather have devs invest time in serious functionality then doing stuff like GUI.

Otherwise, this quickly turns to nonsence such as Nano server image builder [1] because Microsoft is still babysitting people who CBB to spend few hours to learn Powershell basics and need a GUI that generate 1 liner script.

Microsoft should definitelly rise beyond click next culture.

[1] https://blogs.technet.microsoft.com/nanoserver/2016/10/15/in...

Discoverability and ease of use ARE serious functionality.

To be fair, the settings editor in VSCode shows all the settings possible in a split window with user settings, with neat categories and auto-completion. It's almost like a GUI setting dialog noways and makes it way easier to see what you have changed.

This: https://i.imgur.com/oPYr6Ch.png isn't discoverable?

The comments tell you in detail how each setting works (as you can see, they are even translated), you can search for a specific setting on the top, and it's categorized as well; defaults on the left, your own on the right.

No, wading through a huge text file is not discoverable.

How would you suggest that many settings be implemented in a GUI? It'd have to break them up into groups, and it appears that's exactly what VS Code is doing.

There are different ways to discover stuff. Powershell itself clearly proves that it can be done on system level without any GUI whatsoever.

We had the "ease of use" in GUI paradigm for decades and it didn't hold. Why don't you give it a chance as a text ?

Why do you want to limit yourself to only one way of doing things?

Just curious, is Atom's UI considerate about modifying the content of a configuration file? I'm tired of programs changing the structure of it willy-nilly without even notifying the user (e.g. a click in the toolbar implicitly loads the configuration file and saves it with a different layout). Is Atom OK with this?

This is a problem with Sublime Text too. Don't bother putting comments in your settings file, or rearranging its contents. One hit of Ctrl-minus, even by accident, and your config file is wiped out and replaced with an auto-generated one, which incidentally contains your updated font size. You're welcome.

Seriously, Ctrl+Shift+P and start typing gets me to what I need 99% of the time, it's glorious.

Combined with the VIM plugin and I rarely need to touch the mouse.

I didn't try vim plugin but in general, no vim plugin is substitute for vim.

If you mostly just want the memorized shortcuts to work, they tend to work OK in VSCode, Atom, IntelliJ and even Emacs - Spacemacs is even a better ViM for some.

As someone who did a fair amount of hacking in vimL, evil-mode is a drastically improved vim. It gets basically everything right, out of the box, and extending it isnt nearly as painful as using vimL or interacting with vim's Python API.

> It gets basically everything right, out of the box

Custom bindings don't work on the default document. That's a pretty big failure right out of the box.

And I still prefer vimL to lisp, it's the php of editor extension languages. It's not great for big plugins but ok great to slap things together quickly.

It doesn't, in my experience, get insert mode shortcuts like C-h right out of the box because it clashes with emacs' help mode functionality.

I don't get that mindset at all. I can see desiring a file/command line interface for settings, but to want no GUI option at all for others is just strange.

The difference back in the years of old between running a Linux Server and running a Windows Server is one was GUI based and one is text based. I prefer text based a thousand times over. GUI is fine for single use but for text files it is a simple softlink and git away from having everything the same everywhere.

I use VS Code in three locations in three different OS and I love how it works the same everywhere because I just have text files.