Re:10 years of love for Emacs undone by a week of VSCode
by yodon on Saturday November 11, 2017 @02:49PM
(#15677807)
Yes, there was a time when I took pride in that too. Then I realized how much more effectively I could use that cognitive capacity if I was applying it where it was best used rather than where my tools forced me to spend it.
Re:10 years of love for Emacs undone by a week of VSCode
by holydude on Saturday November 11, 2017 @03:08PM
(#15677882)
Any tool or technology requires an investment. It just depends on how much you want to spend on it. You do not need to be an emacs guru to use emacs. Just learn the basics,downloads some pkgs, use what other people already built for you. Hell I never ever wrote a line of elisp but I am able to glue things together so It does what I want.
But you are right if a tool is just as good in its default configuration then it's harder to justify the investments to learn another one.
On the other hand Emacs has been here for dozens of years and it still mostly works and behaves the same. )
Re:10 years of love for Emacs undone by a week of VSCode
by platz on Saturday November 11, 2017 @03:15PM
(#15677931)
What if I don't want to make that investment, because otherwise I have to make 1000 investments for glue code projects
Re:10 years of love for Emacs undone by a week of VSCode
by donovanm on Saturday November 11, 2017 @05:35PM
(#15678562)
That's quite an exaggeration, there's already written packages in emacs for lots of programming languages. Just need to add the package to your config.
Re:10 years of love for Emacs undone by a week of VSCode
by brianwawok on Saturday November 11, 2017 @02:41PM
(#15677758)
The flipside is, I can change a method name across 100 files with 1 click in IntelliJ, and be confident that it did not blow up the world. How are you doing that with VIM, grep and then editing 100 files at once? No thanks.
Re:10 years of love for Emacs undone by a week of VSCode
by mixedCase on Saturday November 11, 2017 @03:11PM
(#15677898)
> How are you doing that with VIM, grep and then editing 100 files at once?
You don't. You do it with Vim and a language plugin. The support across languages isn't great, but this is what the LSP is helping fix.
Re:10 years of love for Emacs undone by a week of VSCode
by reificator on Saturday November 11, 2017 @03:41PM
(#15678073)
> The support across languages isn't great, but this is what the LSP is helping fix.
Which, it's important to note, was designed for VS Code.
Re:10 years of love for Emacs undone by a week of VSCode
by seanmcdirmid on Saturday November 11, 2017 @03:17PM
(#15677936)
Many IDE features (e.g. code completion) excel at letting you use code that you don’t understand well, you can jut jump right in and get something to work. But ya, it’s a just-in-time mechanism that can be used as a crutch for actually learning the abstractions of the code you are working on.
It is great if you don’t work on the codebase enough to justify learning it completely.
I use vim, and whenever I need definitions from other parts of the code base I put them all up in multiple panes or tabs. Its not as immediate as the pop ups, but it forces me to go look at that part of the code base. I find I learn the relevant parts of the code very quickly and even remember the most common definitions.