IDE's or editors?

Coldblackice

[H]ard|Gawd
Joined
Aug 14, 2010
Messages
1,152
What's your IDE-vs-editor workflow, as far as general (personal) programming projects?

Do you use an IDE for any/all programs you write, no matter the size, or do you use an IDE for "project"-sized programs, but use a simple editor for smaller/shorter/quicker programs?


Personally, I'd prefer to use an IDE for any/all programs I write. However, the notion that you're forced to create an entire project for any little program you want to hash out makes me resort to an editor for a lot of my quickie programs.

I'm curious what most of your programming workflows/workspaces are.

(And because this can be largely language-dependent, feel free to answer with specifics of a specific language/IDE, etc.)
 
PHP developer...

I used Netbeans for years and still do love it... however on a whim i gave Komodo Edit a try(actually saw one of the authors post on reddit about it). I like it a lot and have been using it for about three months now. I miss the plugins/community from Netbeans... but like the simplicity of Komodo Edit(Netbeans has so many damn features I didn't use 3/4 of them). One thing that I do miss is the Git integration(as far as highlighting changes) that Netbeans provides... Althought I use SourceTree or CLI for most of my Git work, it was still nice to have a visual representation in the project of modified files since last commit.

When I was a Windows guy I used Notepad++ almost exclusively then I switched to Netbeans. Netbeans followed me to the Mac world... I tried Sublime for a few months... and just couldn't get into it. It just felt clumsy with the package manager and no real interface for the plugins.

Side note... I usually try to pick a cross platform editor that works very similar on both Mac and PC since I still have a PC at home that I occasionally do coding on.
 
I'm old school; i use an editor in a terminal. And another terminal to compile/push if needed (working in an environment where there's no compile/push step is a lot less friction though, if you can manage it). I've done php, perl, c++, erlang, and a little java like that. Java is the hardest one to avoid an IDE though... but it's doable mostly (building can be a pain, especially on an existing project where people are building with IDEs)
 
Just choose whichever lets you make the most efficient use of your time.

Some personal habits:
- IDE for any significant amount of programming, going from throwaway console applications to full applications and websites.
- A text editor for a quick/trivial edit of static files (xml, markup, etc).
- Sometimes LinqPad for LINQ or SQL statement tests.
 
I use whatever works best for what i'm doing but also try to load a vim engine for the editor when possible.

e.g. jVi + netbeans, viemu/vsvim + Visual Studio, or gvim for standard text file editing.
 
If I'm doing any sort of 'real' work, I'm using an IDE. If I'm doing Groovy or Java stuff, I'm in Eclipse. If I'm doing database work, I'm in Rapid SQL. If I'm doing Windows stuff, I'm in Visual Studio or Powershell ISE.

I do sometimes stray away from Eclipse for things like simple text editing, since Eclipse was designed by mutants and put together by chimps, so I often find myself editing XML and other text files in Notepad++, even though they're part of my project in Eclipse. Visual Studio's features and tools are anywhere from 9 to 4000 times better than anything Eclipse does for me, so when I'm using Visual Studio I generally never deviate from doing things in Visual Studio.

I honestly wish the tools available to Java developers were a bit better, since usually the only time I end up doing things outside of my IDE is a result of the IDE's shortcomings. Eclipse's UI feels like it was designed by 16,000 developers all arbitrarily assigned some piece of the UI and not allowed to talk to each other until it's finished. It also generally doesn't seem to work in the way it was intended sometimes. It's also the slowest thing in the universe. I have only limited experience with Netbeans, but it doesn't seem much better, and even if it were, I wouldn't be able to use it at work. I spend most of my 'coding time' (what little of it there is at work, now a days) working out of Eclipse, and to this day it has yet to grow on me.
 
Last edited:
Just choose whichever lets you make the most efficient use of your time.

Some personal habits:
- IDE for any significant amount of programming, going from throwaway console applications to full applications and websites.
- A text editor for a quick/trivial edit of static files (xml, markup, etc).
- Sometimes LinqPad for LINQ or SQL statement tests.

this.

Most efficient tool for the job, IDE for any programming, quick text editor for simple text.
 
I honestly wish the tools available to Java developers were a bit better, since usually the only time I end up doing things outside of my IDE is a result of the IDE's shortcomings. Eclipse's UI feels like it was designed by 16,000 developers all arbitrarily assigned some piece of the UI and not allowed to talk to each other until it's finished. It also generally doesn't seem to work in the way it was intended sometimes. It's also the slowest thing in the universe. I have only limited experience with Netbeans, but it doesn't seem much better, and even if it were, I wouldn't be able to use it at work. I spend most of my 'coding time' (what little of it there is at work, now a days) working out of Eclipse, and to this day it has yet to grow on me.

Try IntelliJ. Far better than Eclipse...
 
There are no IDEs for CoffeeScript, so it's Sublime for that. For C++, it's Xcode and Visual Studio.

It'd be great if there were a JavaScript IDE well-suited for the demands of doing application-scale JavaScript projects, but I'm unaware of any. TypeScript in VS is about as close as it gets.
 
It'd be great if there were a JavaScript IDE well-suited for the demands of doing application-scale JavaScript projects, but I'm unaware of any. TypeScript in VS is about as close as it gets.

I haven't done much with it, but WebMatrix 3 has built in support for Javascript (and its libraries, such as jQuery) as well Node.js. It's targeted at the Microsoft stack, though, so that could be difficult to work around for those of us who don't have control over what platform they have to publish to. I haven't tried it for that, but supposidly you can build fairly large web applications out of Javascript using WebMatrix.

...And as it turns out (I just now read this), WebMatrix 3 also has built in Coffeescript support.
http://www.microsoft.com/web/webmatrix/node.aspx
 
I always use an IDE as even "quickie programs" need to be compiled and debugged.
 
IDE, eclipse for everything. I dont create new projects for most throw away code though, i just keep a "scratch" project for different languages that fills up with small scripts. This is for languages that allow multiple 'main's. The CDT i havent fussed with enough to allow multiple binaries, so i create separate projects for c code.
 
My primary language is JavaScript and I'm strictly a terminal/vim guy. I use tons of automation tools where I run node tools, use make or shell scripts, so tmux is my best friend. I also stick with vim when doing Python or occasional Ruby stuff.

When I go into .NET mode, well only VS for sure, but I can't write JS efficiently in VS, I'm sure others could, but not my cup of tea.

When I have to do some Java, it's probably Android related, so Eclipse works well here. Although Google has a new Android IDE using JetBrains.

I think if you want a solid IDE for general web dev, WebStorm is a great choice. It would be my secondary choice behind vim. Tons of plugins, tools, refactoring is a breeze. I bought a license a while ago, but don't use it.

Full IntelliJ is pretty nice for Java too, but I don't use enough Java to justify the price tag.

When Obj-C and occasional C/C++ comes up, I like XCode. I know people don't, but I think it works great. I do want to try Xamarin though, as I hear people rave about it.

I'm trying to learn Emacs because I'm learning some Clojure/ClojureScript, but I still can't quite grasp it.
 
IDEs are bloat.

IMO, it's best to use a good text editor such as vim or sublime and modify it to your liking. Unnecessary GUI just slows down workflow.
 
IDEs are bloat.

IMO, it's best to use a good text editor such as vim or sublime and modify it to your liking. Unnecessary GUI just slows down workflow.

No it doesn't. There are far greater bottlenecks than what you write your code in. Not to mention any good IDE (i.e. Visual Studio) will let you operate as if the GUI isn't even there if you so choose, and extensions will let you use the text editor just like vim.
 
IDEs are bloat.

IMO, it's best to use a good text editor such as vim or sublime and modify it to your liking. Unnecessary GUI just slows down workflow.

I don't know about you, but trying to do any kind of meaningful work without an IDE would be fairly painful for me. How do you run unit/integration/regression tests without it being painful? How do you set up your text editor to integrate well with your tools? Setting breakpoints from the command line using a tool like gdb can generally be fairly annoying. Do you never use code navigation tools? (E.g. go to declaration) Do you ever run or publish code remotely? How have you set your environment up to handle that? How do you integrate your text editor with source control? If someone asks me for a code review, a good IDE integrated well with a good source control tool will make everything but the actual review process trivial and almost error-free (if they tell me the right check-in, I'm not going to be looking at the wrong code). Do you refactor your code by hand? What if you need to change the name of a class or method, because the lead developer on your team doesn't like the name you picked? How do you do that quickly and effectively?


The whole point of an IDE isn't the GUI. It's the integration. I have tools that I need to work with to do my job effectively and correctly. Fumbling around with a bunch of tools on their own is what slows down workflow. Regardless of how I'm writing my code, I'm going to need to use a debugger. Having all of the tools you use seamlessly integrated speeds up workflow.


To be brutally honest, I haven't met a person who criticizes the notion of IDEs so generally who does anything even remotely sophisticated. Nobody writes their company's data warehouse system, or their flagship software product in a sublime window with no tools.
 
I don't know about you, but trying to do any kind of meaningful work without an IDE would be fairly painful for me. How do you run unit/integration/regression tests without it being painful? How do you set up your text editor to integrate well with your tools? Setting breakpoints from the command line using a tool like gdb can generally be fairly annoying. Do you never use code navigation tools? (E.g. go to declaration) Do you ever run or publish code remotely? How have you set your environment up to handle that? How do you integrate your text editor with source control? If someone asks me for a code review, a good IDE integrated well with a good source control tool will make everything but the actual review process trivial and almost error-free (if they tell me the right check-in, I'm not going to be looking at the wrong code). Do you refactor your code by hand? What if you need to change the name of a class or method, because the lead developer on your team doesn't like the name you picked? How do you do that quickly and effectively?


The whole point of an IDE isn't the GUI. It's the integration. I have tools that I need to work with to do my job effectively and correctly. Fumbling around with a bunch of tools on their own is what slows down workflow. Regardless of how I'm writing my code, I'm going to need to use a debugger. Having all of the tools you use seamlessly integrated speeds up workflow.


To be brutally honest, I haven't met a person who criticizes the notion of IDEs so generally who does anything even remotely sophisticated. Nobody writes their company's data warehouse system, or their flagship software product in a sublime window with no tools.

Pretty much all of this. I can't imagine being able to get any of my work done in a reasonable amount of time without an IDE. That said, I do like having Notepad++ around whenever I just want to try something for the sake of trying it, and not having to mess around with my applications.
 
-Asp.net, C# and C++ - Visual Studio
Python - Visual Studio and Notepad++
-PHP - Notepad ++(maybe net beans)
-Java - Netbean
-Android(java) - Eclipse


edit:// I guess it all depend on the language for me
 
IDEs are bloat.

IMO, it's best to use a good text editor such as vim or sublime and modify it to your liking. Unnecessary GUI just slows down workflow.

Which debugger do you use?
 
Someone who says IDEs are just bloat, is probably not using the right IDE or not writing much code. I also wonder what you are using to do debugging.
 
Someone who says IDEs are just bloat, is probably not using the right IDE or not writing much code.
Indeed, it's hard to imagine anyone writing code professional who would say such a thing. Maybe it was just a troll.
 
Indeed, it's hard to imagine anyone writing code professional who would say such a thing. Maybe it was just a troll.

On my previous project, half the developers used vim exclusively for Java development.

The project failed... in part due to poor tooling.

There are people who claim to be programmers that use text editor exclusively... i.e. run unit tests via Maven, etc. But in reality, it hurts them so much....
 
I don't know about you, but trying to do any kind of meaningful work without an IDE would be fairly painful for me. How do you run unit/integration/regression tests without it being painful?

I work as a web developer, currently with Node.js. I use VIM as my editor. I can have a single terminal window (with multiple tabs) open in which I can do everything extremely easily. I use a tool called mocha for testing. I *could* have mocha integrated into VIM but I choose not to, it's usage is too simple:

Code:
mocha --reporter spec --bail

One line into my second terminal tab (which I can open / close / focus with a single keystroke combination) and my testing is in progress.

How do you set up your text editor to integrate well with your tools? Setting breakpoints from the command line using a tool like gdb can generally be fairly annoying. Do you never use code navigation tools? (E.g. go to declaration)

Most of my debugging is based on watching logs (automatically, of course), and debugging is usually a flag with whatever that I may be working with. I don't think debuggers are all that popular in web development. Nothing, however, stops you from using a text editor extension that can take advantage of, say, GDB. A good text editor doesn't stop you from extending it's capabilities.

Do you ever run or publish code remotely? How have you set your environment up to handle that?

Of course, it's a single command away. I've been using heroku lately:
Code:
git push heroku-test master

How do you integrate your text editor with source control?
Why do I need to have it integrated? Why gimp yourself with a plaster of GUI that will never, ever be as powerful as what it covers up?

I can push, commit & update as fast as I can type. Pretty damn fast.

If someone asks me for a code review, a good IDE integrated well with a good source control tool will make everything but the actual review process trivial and almost error-free (if they tell me the right check-in, I'm not going to be looking at the wrong code).

While it may be good, it will always be a nerfed version of what you should learn to use. Git is git. SVN is SVN. Mercurial is Mercurial. All are command line tools.

Do you refactor your code by hand? What if you need to change the name of a class or method, because the lead developer on your team doesn't like the name you picked? How do you do that quickly and effectively?

Global search and replace isn't an IDE-only feature. It's an editor feature.


The whole point of an IDE isn't the GUI. It's the integration. I have tools that I need to work with to do my job effectively and correctly.

No. What you have is what you are given. It's tools that you need, may need, or may not need.

Fumbling around with a bunch of tools on their own is what slows down workflow. Regardless of how I'm writing my code, I'm going to need to use a debugger. Having all of the tools you use seamlessly integrated speeds up workflow.

You will always battle with tools that you may not need, may not be able to configure, etc.

To be brutally honest, I haven't met a person who criticizes the notion of IDEs so generally who does anything even remotely sophisticated. Nobody writes their company's data warehouse system, or their flagship software product in a sublime window with no tools.

That's the whole point of going with a basic editor. It's up to YOU to pick the right tools for the job. You can integrate your tools as you wish, whatever floats your boat.
 
Most of my debugging is based on watching logs (automatically, of course), and debugging is usually a flag with whatever that I may be working with. I don't think debuggers are all that popular in web development. Nothing, however, stops you from using a text editor extension that can take advantage of, say, GDB. A good text editor doesn't stop you from extending it's capabilities.

lol.... using logs for debugging instead of breakpoints, just lol.


To be honest... I use command line for Git other than switching branches (dozens, sometimes hundreds of branches I have to manage) for which I use UI. Most efficient tool for the job ;)
 
When it comes to web development, I agree with krogen. I use vim/git/node tooling in much the same way. Every browser has debug tools for breakpoints, and automation with make/shell scripts and Grunt makes testing/building pretty straightforward.

But like others have said, right tool for the job, when it comes to C#/Java I think a solid IDE is a good fit.
 
I work as a web developer, currently with Node.js.

Then given the nature of Node.js, and the projects which it lends itself to most effective, you've only confirmed my suspicions.

Don't take my statement the wrong way. I think Node.js is excellent, and I try to use it whenever it makes sense to. But in a lot of situations, it doesn't, because the single-threaded, non-blocking model isn't appropriate in said situation. If you're a Node.js developer, you might be able to get away without using high calibre tools (though I would argue that good Node.js developers still use debuggers), but the rest of us can't get away with debugging using log files. If you're doing more complicated things, an IDE isn't bloat...It's the only thing that makes sense.


I use VIM as my editor. I can have a single terminal window (with multiple tabs) open in which I can do everything extremely easily. I use a tool called mocha for testing. I *could* have mocha integrated into VIM but I choose not to, it's usage is too simple:

Code:
mocha --reporter spec --bail

One line into my second terminal tab (which I can open / close / focus with a single keystroke combination) and my testing is in progress.

...Which is all fun and good, until you get to large, demanding regression tests (such as coded UI tests) and load tests which might not be ideal to run every time you want to test something. Sometimes I'm going to be running every test. Sometimes I wish to be selective. You can go along with with the command line, but at some point it just ends up being better to use an integrated tool.

Most of my debugging is based on watching logs (automatically, of course), and debugging is usually a flag with whatever that I may be working with.

...Which is why you can get away with using an unsophisticated tool set...You're doing highly unsophisticated debugging.

I don't think debuggers are all that popular in web development.

You don't have to think that....But it doesn't change the fact that there are plenty of uses for debuggers in web development.

Nothing, however, stops you from using a text editor extension that can take advantage of, say, GDB. A good text editor doesn't stop you from extending it's capabilities.

...Aside from the fact that I'm generally not paid to write an extension to software to provide functionality that is already offered in software we already own licenses to so that people can circumvent the use of the software we already have licenses to. If there aren't good extensions to the text editor I would use that integrate the tools I am using, I would have to write the extension myself.

...And after all that extension writing to integrate tools into my development environment, I'd be getting dangerously close to something which could be considered an IDE, at which point the whole exercise was a complete waste of time.

While it may be good, it will always be a nerfed version of what you should learn to use. Git is git. SVN is SVN. Mercurial is Mercurial. All are command line tools.

Unfortunately, that is not an exhaustive list of all source control tools. Sorry, try again.

Global search and replace isn't an IDE-only feature. It's an editor feature.

Text-editor based refactoring is strictly regular, and is therefore limited (mathematically limited, in fact, so save yourself the effort of trying to argue otherwise) . Not all refactoring features are a simple search and replace. Sophisticated refactoring tools (like Resharper) depend on code analysis, which allows them to do more sophisticated refactorizations. Navigation goes side by side with this, because the navigation tools in text editors can only do 'regular' things as well, so both your editing and navigation features are limited in what they can do. Your text editor can't determine where the definition of a class is. Your text editor can only determine where particular words or regular expression matches are. It doesn't know what a class is. You can try to get around this by wrapping the name of the class in a bit of syntax when you do your global search, but then you have to do different things if you're looking for a class or a method or an interface. And since your text editor can't determine whether you're looking at a class, a function or an interface, it can't determine which 'different' search it needs to do, so it can't make the option to do the search into a context menu. So in a text editor, I can't right click on an instance of a class and click on 'Go to declaration'. I have to open up a global search, and type in search terms.

You could in theory write an extension for your favorite text editor that does code analysis, but then you're simply converging on an IDE again, and creating such a thing isn't exactly trivial.
 
Last edited:
I use emacs, these days not even in X11 mode.

It isn't so much that I have something specific against Eclipse as it is at a specific point in time. But I observe very bad decision making with this "class" of huge, heavily sponsored open source projects, namely eclipse and mozilla. They have the weight to give orders to programmers and the non-programmers making the decisions call the shots (they hold the money). While the outcome is open source the decisions are usually bogus. I won't invest in Eclipse, unless I somehow end up doing Android exclusively.
 
I always have at least one or two instances of VS spun up, so it just makes sense for me to stick to using the IDE.

Even simple projects benefit from having an IDE to do some of the rote work (folder creation, basic file structure, etc. On top of that, the various things in the IDE are invaluable. E.g. the "Code Definition Window", using f12 to go to definition, using ctrl - to go back in my text navigation stack, using ctrl shift - to go forward, ctrl mm for collapsing/expanding blocks, and the sheer simplicity and speed of intellisense. I've used vim in the past for some javascript/ruby work, but a lot of that knowledge is fleeting when not in constant use (not to mention that the amount of customization needed to make vim acceptable for coding).

And that's just for writing the code. VS's debugging tools are great. Even though I'm relatively comfortable in WinDBG (practically a necessity for kernel debugging), that, too, is esoteric and fleeting knowledge. A few months not using it and I had to use it for something recently, which reminded me just how steep of a ramp it has. Give me my thread visualization, local variables, and integrated code view with easy cross-code navigation, please!
 
It sounds like a lot of time and effort setting up all the terminals and tools you have and understanding how to use them all and knowing all the command line tools. It may work for you, but I'm not sure it makes sense to argue that it is easier than an integrated development environment. Another major concern, what if you have new teammate who need to get involved or you leave and are replaced someday? It is much easier to have an IDE with 1-2 plugins and open a project as a whole, then explain to someone all the terminals, scripts, tools, they need to setup and become experts with to get started. Mistakes seem like a much greater possibility with this model. Most people would not find it as convenient as you do, but in some ways I understand why you enjoy a powerful command line interface from which you can perform a variety of tasks.

Most of my debugging is based on watching logs (automatically, of course)

Most people need to debug their code by stepping it, not simply watching logs or using print statements. It sounds like a lot of time and effort would be required to setup all that logging just to debug your code. I think logging serves its own purpose separate from debugging.

Why do I need to have it integrated? Why gimp yourself with a plaster of GUI that will never, ever be as powerful as what it covers up?

I can push, commit & update as fast as I can type. Pretty damn fast.

I use SVN at work and visual studio. We use both SVN shell extensions (Tortoise) and SVN VS plugins (VisualSVN). I've personally never had to resort to the command line for SVN. I'm not gimped and I always have the command line available if it really comes down to it. I can right click on a project and select "commit" faster than you or I can type the command to do so (and I am assuming we both are great typists) and without making typos. It lists all modified files and I can immediately right click each file and review the changes, etc. etc. No commands necessary.

Global search and replace isn't an IDE-only feature. It's an editor feature.

Global search and replace isn't refactoring. Refactoring is much more powerful and understands scope and usage of the variable, class, etc. It isn't simply find and replace.
 
You guys are SO missing the point.

Here's the ideal scenario:

You pick tools that solve problems in the best way possible. If I need my web application to be highly compatible across a server landscape, perhaps it's best to go with PHP as it's probably the most often used language for web development. If I want my web application to by highly integrated, perhaps it's best to go with Node. If I want my web application to be highly threaded, perhaps it's best to go with Clojure.

What's the main point of the above paragraph? It's solving a problem in the best way possible.

Same story goes for editors and IDEs. IDEs certainly don't give you the flexibility that good text editors can. You are given less choice. You are given tools that might not be ideal for your problem. Hence IDEs are bad. End of story.

P.S.
About debugging. Once again, why not integrate a debugger into a text editor, if needed? If I search for Sublime debugging I am given plenty of results. No need to write a GUI for GDB yourself. If you can think of it, it has probably been done.
 
You could also grab some plugins to assist with asset management, visualization, compilation, GUI design, a shader editor and SVN/Git/TFS. You'd then have the ultimate text editor: an IDE.
 
You pick tools that solve problems in the best way possible. If I need my web application to be highly compatible across a server landscape, perhaps it's best to go with PHP as it's probably the most often used language for web development. If I want my web application to by highly integrated, perhaps it's best to go with Node. If I want my web application to be highly threaded, perhaps it's best to go with Clojure.

What's the main point of the above paragraph? It's solving a problem in the best way possible.

We're aware. It's called being pragmatic.

Same story goes for editors and IDEs. IDEs certainly don't give you the flexibility that good text editors can. You are given less choice. You are given tools that might not be ideal for your problem. Hence IDEs are bad. End of story.

IDEs are in every way as flexible as text editors, since they supercede text editing. You seem to be lacking experience with IDEs, if you really believe they give you less choice. IDEs are extensible in the same ways text editors are. Generally, if there's a tool worth using enough for there to be a sublime plugin for it, there's a plugin for the major IDEs as well. The IDEs give me the ability to utilize the tools that I need/want in an integrated fashion.

Oddly enough, when I'm doing Windows development, the best set of tools for the job (in my opinion, at least), are already integrated in visual studio out of box. When I'm doing Java development, the best set of tools are already integrated into eclipse or readily integratable.

P.S.
About debugging. Once again, why not integrate a debugger into a text editor, if needed? If I search for Sublime debugging I am given plenty of results. No need to write a GUI for GDB yourself. If you can think of it, it has probably been done.

See here
 
Last edited:
I'm a big fan of just using an editor and writing scripts to compile/sync (if the code is going to another server). Typically I use Kate or notepad++ if in windows. KISS.

I occasionally use Vim if I need to do a quick edit, but can't imagine writing an entire program with it. I rather have something with tabs, and something where I can copy/paste code easily and what not. But Vim can be useful for a quick edit while SSHed into a server.
 
We're aware. It's called being pragmatic.

IDEs are in every way as flexible as text editors, since they supercede text editing. You seem to be lacking experience with IDEs, if you really believe they give you less choice. IDEs are extensible in the same ways text editors are. Generally, if there's a tool worth using enough for there to be a sublime plugin for it, there's a plugin for the major IDEs as well. The IDEs give me the ability to utilize the tools that I need/want in an integrated fashion.

So, if I don't like how an IDE handles debugging, or don't need it, I can remove that feature? I don't think that's often the case, unless it's written as a plugin in the first place. And if everything is written as a plugin, I would call this piece of software a text editor, not an IDE.

Oddly enough, when I'm doing Windows development, the best set of tools for the job (in my opinion, at least), are already integrated in visual studio out of box. When I'm doing Java development, the best set of tools are already integrated into eclipse or readily integratable.

See, it's your opinion, as you say. If I don't like a particular feature of an IDE, I should be able to remove it and replace it with something better. Because I have my opinion and I don't like how it handles a certain workflow.


It's not an IDE. It's a text editor modified to your own liking. You could call VIM an IDE (ha!), if you truly believe extensions make a text editor an IDE.

The word "integrated" is what makes an IDE an IDE.
 
Back
Top