News for hackers. Stuff that matters.
Re:Screenshots from developers: 2002 vs. 2015 by BrandonBradley on Saturday December 12, 2015 @09:16AM (#10722802)
I wouldn't jump to that conclusion unless I observed how people use it in real-time.

For verbose languages, you can't beat auto-completion and auto-import.

Re:Screenshots from developers: 2002 vs. 2015 by creshal on Saturday December 12, 2015 @09:19AM (#10722815)
> For verbose languages, you can't beat auto-completion and auto-import.

And you can get both in vim, emacs, etc. The lines between those and full IDEs are blurry with the right (or wrong) amount of plugins.

Re:Screenshots from developers: 2002 vs. 2015 by izacus on Saturday December 12, 2015 @09:47AM (#10722896)
The autocompletion in both vim and emacs was always significantly worse than any IDE-based ones, no matter the plugin I tried (for C, C++, Python or Go). Most of them are pretty much limited to ctags with no context matching, others simply died on projects beyond trivial.
Re:Screenshots from developers: 2002 vs. 2015 by to3m on Saturday December 12, 2015 @09:55AM (#10722919)
For C/C++ and emacs, try rtags: https://github.com/Andersbakken/rtags

It's clang-based, so suffers from none of the tags-type issues: it's context-sensitive, and can see straight through gnarly stuff such as identifiers generated by token pasting.

Good points:

- Only mildly fiddly to set up

- Code browsing works well

- Code completion works well when it works

- Cute gcc/g++/etc. wrapper trick means you don't have to change any build settings

Bad points:

- Making it work with code you haven't built yourself on your local system (e.g., 3rd party stuff that's not complete, code for another platform) is less straightforward

- Code completion sometimes doesn't work with certain files (and for no reason that I've ever been able to figure out)

- It's probably my own limitations but I found it extremely inconvenient to debug (internally it's surprisingly complicated: separate client and server, lots of lengthy command lines, client code writes elisp code to stdout and elisp in emacs eats it up, the actual completion popup is a separate package, etc.)

Re:Screenshots from developers: 2002 vs. 2015 by bdisraeli on Saturday December 12, 2015 @11:48AM (#10723283)
Cider (for Clojure) and Ensime (for Scala) give you excellent support for auto-completion, documentation, and refactoring in Emacs. It's definitely possible, so it probably just depends on how popular Emacs/Vim are in your language community.
Re:Screenshots from developers: 2002 vs. 2015 by rmcpherson on Saturday December 12, 2015 @11:18AM (#10723176)
For go auto completion in vim, vim-go with youcompleteme works well for me. It's not tags-based, based on the source AST, shows method signatures as well.
Re:Screenshots from developers: 2002 vs. 2015 by DrJokepu on Saturday December 12, 2015 @10:56AM (#10723101)
I never managed to get it working in vim, but you can get pretty decent auto Go completion (with Go oracle) in Emacs.
Re:Screenshots from developers: 2002 vs. 2015 by simula67 on Saturday December 12, 2015 @09:53AM (#10722910)
Not all auto-completions are equal. I have felt that Intellij's auto-completion is far superior to vim's YouCompleteMe.

There are many other advantages like out of the box support for a lot of common use cases like refactoring, navigation, build tool support, reuse common shortcuts like Control-C Control-V for copy-paste etc.

I would definitely advice new engineers coming into languages like Java to pick up an IDE like Intellij instead of vim.

Re:Screenshots from developers: 2002 vs. 2015 by Roboprog on Saturday December 12, 2015 @02:35PM (#10723841)
Intellij with vim plugin :-)

I like how you can use command keys to quickly toggle on and off the project file and current-file's-components browsers, leaving the "distraction free" * editor window for much of your work.

* yeah, there's a mode with this name that auto-wacks ALL the supplemental panels, AND the window frame. I don't usually go that far, but it does show that they "get it" as far as what many of us IDE resisters disliked.