3 ms·
I actually like this viewpoint because I have done both and generally I disagree with you. But here's my take. I use VSCode often because its "just easier". Th
by xf1cf 6y ago
I actually like this viewpoint because I have done both and generally I disagree with you. But here's my take.
I use VSCode often because its "just easier". The extensions are at best (in my opinion) ok approximations to what I can get with emacs. Especially for a language I'm inexperienced with in emacs VSCode is a nice integration layer while I adjust my configuration.
Emacs (and to that point vim) is vastly superior to any offering VSCode has. The problem is you have to be productive. Many nights I labored over my emacs configuration to tailor to my job. I've done this for the last 10 years. It takes effort. To that, you have a point. VSCode is effortless. On that, VScode doesnt feel like anything to me except a bridge layer. Emacs and vim offer a vastly better experience (without the git politics!) if you're willing to spend the time customizing it. But that is the difference - are you willing to spend the time? Many developers are not and that's fine. But for a marginal additional investment you can have something better.
Something to think about at least. I can install my Emacs configuration in 30 seconds from my github.
- random_cynic 6y agoEverywhere in this thread I see vague and generic statements like this. Do you have concrete examples of specific things in your 10 year old Emacs configuration you "labored over" that can do something VSCode (and its extensions) can't and which makes Emacs "vastly superior"? If so please share, otherwise don't bother. We have already heard all this vague nonsense for years.
- nvarsj 6y agoThere are loads of examples in the comments here. Have you read them?