3 ms·
The config file still seems like a cop-out for "we couldn't be arsed to build a GUI settings editor". Excusable at alpha/beta, not a final release. Command pro
by benbristow 6y ago
The config file still seems like a cop-out for "we couldn't be arsed to build a GUI settings editor". Excusable at alpha/beta, not a final release.
Command prompt & Powershell both have GUI settings editors.
- AshleyGrant 6y agoOr.. "We haven't built a GUI settings editor yet" VSCode didn't have a GUI settings editor for quite a while.
- snazz 6y agoVS Code's configuration is a GUI skin over JSON, so that's probably what they should do with the terminal as well.
- Already__Taken 6y agothey probably will but code did not launch with that GUI. if it's going to be like the other modern settings UI I'm in no rush for them to either.
- genr8 6y agoYea. But that was added later, and theres still important JSON build-system files that you need to edit manually to this day. JSON isnt descriptive enough to auto-translate the raw files into a functional GUI. They seem to think its better off as text, but that goes against everything else on Windows mentality, and its not documented properly.
- Someone1234 6y agoPeople have been complaining for years that Microsoft's stuff isn't configurable enough for power users/developers. Now they're following VSCode's lead and offering "infinite configurability" that's also wrong because it is "too hard!" This would almost be funny if it weren't so obnoxious. Now, I will fully cop to out-dated docs being annoying, particularly when most of the configuration isn't really obvious or self-documenting. But complaining about Microsoft of all people offering highly flexible text-based configurations is hugely ironic to me.