Eclipse vs. Vim

I think that if someone asked me for an IDE for Java programming, I would definitely recommend Eclipse as is one of the most complete solutions for this language out there. If the main programming language of that person is not Java, I don't think Eclipse would suit his needs[.]

Incentivized

I would recommend Vim in any scenario where text files have to be viewed, created, or edited on GNU/Linux computers. Regardless if you need to quickly change a few things in a configuration file, or you need to write up a full document, Vim is great. I wouldn't use Vim to view, edit, or create anything that requires "rich-text". In other words, if you need to format the text (bolding, font colours, word-art, etc), then Vim isn't the tool to use.

Incentivized

• Eclipse organizes imports well and does a good job presenting different programming languages.
• Eclipse auto formats source code allowing customization and increased readability.
• Eclipse reports errors automatically to users rather than logging it to the console.
• Eclipse has coding shortcuts and auto-correction features allowing faster software development.

Incentivized

• The efficient modal editing makes it very fast to write/edit code as I think of it.
• The customization and wide range of plugins let me do very specific things and automate parts of my workflow.
• The fact that it runs inside a terminal simplifies my window management and just becomes another Tmux window in my workflow.

Incentivized

• While the DB integration is broad (many connectors) it isn't particularly deep. So if you need to do serious DB work on (for example) SQL Server, it is sometimes necessary to go directly to the SQL Server Studio. But for general access and manipulation, it is ok.
• The syntax formatting is sometimes painful to set up and doesn't always support things well. For example, it doesn't effectively support SCSS.
• Using it for remote debugging in a VM works pretty well, but it is difficult to set up and there is no documentation I could find to really explain how to do it. When remote debugging, the editor does not necessarily integrate the remote context. So, for example, things like Pylint don't always find the libraries in the VM and display spurious errors.
• The debugging console is not the default, and my choice is never remembered, so every time I restart my program, it's a dialog and several clicks to get it back. The debugging console has the same contextual problems with remote debugging that the editor does.

Incentivized

• Without a doubt the hardest program to learn. It is a completely different paradigm of thinking compared to other editors
• By default it doesn't have lots of fancy features you would find in larger IDE programs like code completion and linking
• It lives in the command line so a user has to be comfortable with this interface

Incentivized

I love this product, what makes it one of the best tool out in the market is its ability to function with a wide range of languages. The online community support is superb, so you are never stuck on an issue. The customization is endless, you can keep adding plugins or jars for more functionalities as per your requirements. It's Free !!!

Incentivized

It has everything that the developer needs to do the job. Few things that I have used in my day-to-day development 1. Console output. 2. Software flash functionality supporting multiple JTAG vendors like J-LINK. 3. Debugging capabilities like having a breakpoint, looking at the assembly, looking at the memory etc. this also applies to Embedded boards. 4. Plug-in like CMake, Doxygen and PlantUML are available.

Incentivized

I don't consider the steep learning curve to be a hinderance on the overall usability. I would rate this a ten, but to be honest a lot of people do get hung up at the beginning and just abandon it. However, for people who have made the moderate effort to get over the hump, nothing can be more usable.

Incentivized

I gave this rating because Eclipse is an open-source free IDE therefore no support system is available as far as I know. I have to go through other sources to solve my problem which is very tough and annoying. So if you are using Eclipse then you are on your own, as a student, it is not a big issue for me but for developers it is a need.

There is no commercial support for Vim. Thus, it will not get a mark beyond 5. However, community support is very good. You can easily find solutions for most of the problems in the community.

Incentivized

The installation, adaptability, and ease of usage for Eclipse are pretty high and simple compared to some of the other products. Also, the fact that it is almost a plug and play once the connections are established and once a new user gets the hang of the system comes pretty handy.

Incentivized

Vim's keybindings are a lot more complex than Notepad++. With that, comes a whole bunch of capability that Notepad++ just can't match. Emacs is comparable, in terms of capabilities--because Vim is built into so many unix systems, I chose to learn it instead of Emacs. Knowing both probably isn't a bad idea, but there's enough to learn in either camp to keep you busy

Incentivized

• This development environment offers the possibility of improving the productivity time of work teams by supporting the integration of large architectures.
• It drives constant change and evolution in work teams thanks to its constant versioning.
• It works well enough to develop continuous server client integrations, based on solid or any other programming principle.

Incentivized

• It always increases productivity.
• Sometimes feature discovery is not easy. It could be documented well like how to install a plugin and if it supported well or not.

Incentivized