4 ms·

This is preciselly the reason I and many of my collegues love it - no GUI for settings. This means you can use hundreeds of tools to manage your settings and it

This is preciselly the reason I and many of my collegues love it - no GUI for settings. This means you can use hundreeds of tools to manage your settings and it is in true spirit of unix philosophy to keep everything as a text file. Much more time is wasted by looking for options in GUI equivalent and reproducibility, sharing, backup and comparing (diff) are way harder or nonexistent. Creating frontend for it is trivial, but honestly, why drop from horse to donkey as they say. All the apps should have settings like that.

vvanders 10y ago
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.
- majkinetor 10y ago
  I didn't try vim plugin but in general, no vim plugin is substitute for vim.
  - AsyncAwait 10y ago
    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.
    - emidln 10y ago
      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.
      - flukus 10y ago
        > 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.
      - Lio 10y ago
        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.
joekrill 10y ago
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.
- majkinetor 10y ago
  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/introducing-the-nano-server-image-builder/ https://blogs.technet.microsoft.com/nanoserver/2016/10/15/in...
  - st3v3r 10y ago
    Discoverability and ease of use ARE serious functionality.
    - majkinetor 10y ago
      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 ?
      - st3v3r 10y ago
        Why do you want to limit yourself to only one way of doing things?
    - AsyncAwait 10y ago
      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.
yokohummer7 10y ago
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.
- koffiezet 10y ago
  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, ...)
st3v3r 10y ago
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.
- baldfat 10y ago
  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.

vvanders 10y ago

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.

majkinetor 10y ago
I didn't try vim plugin but in general, no vim plugin is substitute for vim.
- AsyncAwait 10y ago
  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.
  - emidln 10y ago
    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.
    - flukus 10y ago
      > 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.
    - Lio 10y ago
      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.

joekrill 10y ago

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.

majkinetor 10y ago
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/introducing-the-nano-server-image-builder/ https://blogs.technet.microsoft.com/nanoserver/2016/10/15/in...
- st3v3r 10y ago
  Discoverability and ease of use ARE serious functionality.
  - majkinetor 10y ago
    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 ?
    - st3v3r 10y ago
      Why do you want to limit yourself to only one way of doing things?
  - AsyncAwait 10y ago
    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.

yokohummer7 10y ago

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.

koffiezet 10y ago
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, ...)

st3v3r 10y ago

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.

baldfat 10y ago
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.