When JetBrains releases an IDE as a service then I'll be excited.
I do admit that of all the IDE's I've used IntelliJ was definitely the least annoying. But it still doesn't hold a candle to Emacs in Evil Mode for me.
When JetBrains releases an IDE as a service then I'll be excited.
I do admit that of all the IDE's I've used IntelliJ was definitely the least annoying. But it still doesn't hold a candle to Emacs in Evil Mode for me.
No, because IDE are more than just coding.
They offer an integration of services that one usually requires in large scale projects.
I want:
- semantic refactoring
- background compilation as I type
- static analysis
- integration with bug tracking software and source control
- visual debugging of data structures, threads
- ability to change code during debbuging sessions
- navigation of binary artifacts
- debugging unit tests
- semantic code navigation
- GUI designers
- XML build tools
- visual navigation of databases
- UML dual way generation
- ...
And above all, avoid trying to make Emacs or VIM do half of these features, every time I install them.
A great part of an IDE worflow is the visual experience. Having some kind of service, while forcing each client application to create their own UIs, kind of beats the purpose.
This is why on UNIX world the developer experience feels half-baked to those of us that could step a bit into the world as imagined by Xerox PARC.
Nothing about having a service prevents offering that visual experience. IntelliJ/Eclipse the IDE can still exist while consuming the same backend that my Emacs consumes. You get your visual experience that helps you achieve flow state. I get my highly configurable/optimized editor that helps me achieve flow state.
win/win
Sure, its learning curve is unusually high and Elisp knowledge is required for some edge cases, but it's definitely worth in the medium and the long run.
Did you miss the visual and semantic adjectives?
I know UNIX since Xenix and DG-UX days, before Linux was a thing and Emacs was my editor to go up to 2005.
Unless it has changed radically, no it cannot do all these features. Half of them, yes.
Sure you can program them yourself, to get as end result some text interface to ELisp functions.
But I no longer want to spend time doing that.
> For Lisp languages there is simply no other option.
Only if you don't want to pay for proper Common Lisp environments. They can do so much more.
It didn't. Emacs still tries to do most of those things and fails more often than not. I love Emacs and I use it daily, but between it's dated look, monstrous codebase, enormous feature set and limited resources dedicated to development it cannot hope to match programs written for a single purpose by a team of professionals.
Still, Emacs is great editor. I'm not going to dump Org Mode, for example, and calc is great, and scripting is absolutely awesome (Emacs is also great IDE for Elisp) and so on. It's great for many things, and it's even ok for programming, but it's never going to be as good as IDEs. And IDEs are not going to have mail & newsgroup clients built into them, I suppose.
I used Emacs on my UNIX projects between 1994 and 2005.
BTW I've recently tried omnisharp-emacs, but found dealing with larger C# source files was way too slow to be useful. But it's pretty great to be able to use Emacs for C# and get useful code completion, so I'll be continuing to make efforts to make this work.
[1] http://blog.jetbrains.com/blog/2013/09/18/upsource-a-platfor...
Pitching a new IDE is asking a programmer to throw away years of experience in their editor of choice (mine, for better or worse, is Emacs) for some shiny feature.
(I see above that people are arguing that this doesn't solve the issue of visual integration, but I don't see why separation of concerns in this way would make it harder to write a language-specific IDE--can anyone point to any examples?)