|
|
|
|
|
|
by shadowgovt
1056 days ago
|
|
|
> You are excited that it's dated to 'now'. Yes, I am. That's very convenient for me. > Were you around when Microsoft decided to drop the UX they'd been using for a few decades and change to "The Ribbon" ? I was, and you're right. Microsoft functionally owns the chrome for vscode and it isn't as configurable as far as I can tell as emacs at that layer. There's certainly a possibility they will make a decision later to mess everything up. But for now, my previous observation stands. I have to do less configuration out of the box to get vscode into a daily use work configuration than a naked emacs install. I highlight this because it's not an unsolvable problem for emacs. It requires making a recommended default configuration that will be more correct for the 95% use case and advocating that configuration on the install channels for the tool. |
|
|
For people interested in this, I know about Doom Emacs [1] and Spacemacs [2].
[1] https://github.com/doomemacs/doomemacs [2] https://github.com/syl20bnr/spacemacs