5 ms·

> My gut feeling is that people who haven't looked up from emacs or vi for a decade or two have no idea what modern IDEs are capable of out of the box. I use v

> My gut feeling is that people who haven't looked up from emacs or vi for a decade or two have no idea what modern IDEs are capable of out of the box. I use visual studio in my day-to-day job for .net and C# work. I know what it’s capable and it’s a very impressive piece of technology. What it doesn’t do is allow me to shape it to fit my workflow. I always have to adapt to fit the tool as opposed to the other way around, and any level of customization and extensibility feels extremely shallow compared to Emacs. With Emacs I get everything my way. And I don’t think that can be said about any other tool I know of. Needless to say I use both editors side by side and use whatever tool is best for the job at the time. Edit: IMO standardized technologies like LSP is now bridging the gap for many (but obviously not all) IDE features. I suspect the imminent death of the “plain editor” is vastly exxagerated :)

crimsonalucard 9y ago
The problem is often you have to build "Your way" from the ground up. Some people just want "A way" that's working as soon as they open up the editor.
- josteink 9y ago
  Sure. But that applies to almost any problem I face on a daily basis as a programmer. I don’t see why optimizing my flow and tools should be less important than optimizing what I deliver. The former practically enables the latter. This mindset is pretty much what has given us the high quality FOSS projects we use everywhere. I wouldn't really call this is a “problem”.
- btschaegg 9y ago
  ...and that's where Emacs starter kits come into the picture. Especially when compared to VS, Emacs based solutions always seem superior to me because they don't require me to use the mouse for every. little. effing. thing. I want to achieve. That, and they are usually much more designed around a more UNIX-focused toolset than most IDEs, which means less interdependent blobs of cruft like Intellisense and the like.

crimsonalucard 9y ago

The problem is often you have to build "Your way" from the ground up. Some people just want "A way" that's working as soon as they open up the editor.

josteink 9y ago
Sure. But that applies to almost any problem I face on a daily basis as a programmer. I don’t see why optimizing my flow and tools should be less important than optimizing what I deliver. The former practically enables the latter. This mindset is pretty much what has given us the high quality FOSS projects we use everywhere. I wouldn't really call this is a “problem”.
btschaegg 9y ago
...and that's where Emacs starter kits come into the picture. Especially when compared to VS, Emacs based solutions always seem superior to me because they don't require me to use the mouse for every. little. effing. thing. I want to achieve. That, and they are usually much more designed around a more UNIX-focused toolset than most IDEs, which means less interdependent blobs of cruft like Intellisense and the like.