Why you guys like text editors over IDE?

Why you guys like text editors over IDE?

Other urls found in this thread:

youtu.be/F6-phM56H-Q
repo.msys2.org/distrib/x86_64/msys2-x86_64-20161025.exe
youtu.be/SYGIQLruaFs
twitter.com/SFWRedditVideos

Because I prefer to do my tasks with needless additional complexity to further fuel my superiority complex.

Custom env for my needs

> He needs a bloated IDE to program

brainlet.

Simple text editors get out of my way and let me get shit done on toasters too.

they keep doing annoying stuff I do not feel like digging through deep trees of config options to fix, if it even is possible to fix.

>to further fuel my superiority complex
I think you mean inferiority complex

Those with a superiority complex belittle themselves to make others feel better

Is their a shortcut to compile?

up+return in a separate terminal?

Edit it in your .vim keybindings idiot.

>How do you compile with a text editor?
>How do you debug with a text editor?
>How do you refactor with a text editor?
>How do you generate code with a text editor?
>How do you generate class diagrams with a text editor?
>How do you have errors, warnings, code smells, etc. automatically underlined/highlighted with a text editor?
>How do you get code completion with a text editor?
>How do you quickly access documentation for any type/method/function/etc. with a text editor?
>How do you easily manage dependencies and packages with a text editor?
>How do you quickly find usages of a certain type/method with a text editor?
>How do you find dead, unused code with a text editor?

An IDE is just objectively better. It gives you access to many very useful features for programming. It's simply the better tool for the job. Sure, you can use a text editor, but that's just putting you at a disadvantage for no reason.

leader+ll

One tool for one job.

>How do you compile?
With your compiler
>How do you debug?
With your debugger
>How do you refactor?
This is possible in all good text editors
>How do you generate code?
Use a dedicated code generation tool
>How do you generate class diagrams?
Use a tool for generating class diagrams
>How do you have errors etc highlighted?
Possible in all good text editors
>Code completion?
See above
>Access documentation?
With your file manager of choice
>Manage dependencies?
With your package manager
>Find usages
Possible in all good editors
>Dead or unused code?
Possible in all good editors

All of the features which are possible are, as they should be, implemented in plugins which you can add on to your text editor. The base text editor should be capable of exactly one thing, editing text: it is up to the user to decide if they would like to extend its functionality. Nothing should be included just because it is assumed it might be useful.

>Nothing should be included just because it is assumed it might be useful.
But it objectively is useful. All programmers will benefit from things like code completion and access to documentation. Sure, you can find workarounds, but there's no way that you can argue that digging around through a file manager for documentation is somehow better than just putting your mouse over a part of the code that you're already looking at.

Wow. That's good to know. Thanks, bro.

using an IDE in 2017 is like using a dial up
you spend all that time waiting to actually connect and then the time spent actually using the internet is minimal

Because I don't like waiting for an IDE to catch up with my keystrokes while it suggests function names.

But not everybody using a text editor is a programmer. What happens if you are an author writing a novel? Code completion certainly doesn't help you, but you might want something like spellcheck, which typically only gets in the way for a programmer. The text editor should be adaptable to all use cases, preferably by using a tool specifically dedicated to the task you're looking to do, or if necessary, via extensions. It is the user's choice to sacrifice performance for functionality, not the editor's.

I prefer an IDE

To be fair you can do all that in a very extensible text editor. That just makes the text editor as heavy as an ide and more decentralized in terms of support and quality of each part. In general though I agree and ide is better, particularly if you are not familiar with all the extensions one needs to bulk a text editor into a more full featured tool.

That's why people use text editors for editing text, and integrated development environments for developing software. Text editors aren't intended for programming. It's like the difference between MS Paint and Photoshop.

Bump

>this is what pajeets literally think

most IDE features are crutches

What if I told you I have vim but don't have a compiler yet

This. Wrote my last two novels in vim.

So I have vim. What compiler do I download for c++ programming? Then how do I do compile/debug?

Almost all (((IDEs))) these days come with analytics enabled by default. It's pathetic.

g++ of course

Programmers who program without an IDE and use dynamically typed interpreted languages are idiots. Here is why...

- They assume they never make mistakes and write perfect code all the time, in reality they write shit that appears to work but nobody fucking notices it dosent actually work until several years later when they are long gone. Then some newbie needs to sift through their poorly organised spaghetti to find that variable that should have been pluralised or should have been a number and not a string (an IDE would have caught this fucking horse shit!).

- They think IDE's are a crutch. This roughly translates to either one of two things... they are too fucking stupid to know how to use an IDE. Or they can't be bothered with the extra capabilities like you know... actually testing their fucking code with the debugger. Just write it in a text editor, run it once and assume it works when it dosent crash.

- They think memorising function names, return types, all that shit intellisense takes care of for you is actually useful somehow. In reality it ends up with them reinventing the wheel over and over because they missed that there is a built in function to do the thing they've been doing manually for years and years.

- The worst of all... the majority seem to have started programming on a text editor and a core reason they won't use an IDE is that they don't like change... despite working in an industry that literally changes all the time.

Useless cunts. If you program with a text editor when an IDE is an option, die in a fire. You are the reason spaghetti code exists and projects fail. Fuck you.

I think they prefer to be called Code Artisans, user.

We're still more paid than you user.

Unless you're devops at a big4, I really doubt that.

A text editor like vim is certainly intended for programming.

You do realize you can still use text editors as crutches and absolutely none of your arguments actually hold up because you fully believe the extent of text editors today is notepad.
This is why you're a neet. Unable to comprehend alternative perspectives.

>an industry that literally changes all the time

Gee, I wonder why they choose to keep something as basic as their code writing tool simple? Maybe something to do with IDE's changing all the time and new IDE's popping up all over the place. Why bother yourself with learning new features to something as basic as the tool you use to get code written? Better to spend time actually learning the language itself by, you know, reading! Or, you can let the IDE be your God tool that just knows everything and you never have to remember a single thing. Pretty soon the IDE will auto correct your shitty code and basically write the program for you.

If you can do things from within your editor, it is an IDE.
If you need to leave the IDE to see which line number the error was at or need a separate tool to set the breakpoints in your debugger, I can see why you claim you use a text editor instead of an IDE.

If we should talk about what is wrong with IDEs, then do that.
Eg I personally hate that most if not all are in a single window and they don't have a multi window option.
My window manager is far more capable of managing the different windows than stuffing everything into a single window where you can't even see the code.
I want a full screen window for the build output, the run output and the code.
I have multiple monitors and multiple desktops, why not assume that others have that and want to use that?
Ctrl + click navigation is nice, but why isn't there a way to have two windows open and click on one window and it will adjust on the other like when you click on an error in the build output and it takes you to it in your code.
I often end up compiling in a terminal even though I have an IDE because the window management is so shitty.
Why do they do it at all?

>How do you compile with a text editor?

:! g++ -Wall myprog.C -o myprog


>How do you debug with a text editor?
Syntastic. Also assertions, using a good methodology, the right programs and not being stupid.

>How do you refactor with a text editor?

-open split screen
-yank content in between braces (with one vim comment)
-goto new screen
-paste inside new method

>How do you generate code with a text editor?

By not using a shit language like Java that needs to generate a metric fuckton of boilerplate getters/setters..?

>How do you generate class diagrams with a text editor?

Brainlet.

>How do you have errors, warnings, code smells, etc. automatically underlined/highlighted with a text editor?

Plugins like Syntastic do a great job marking wrong code. Code smells are about being a good coder.

>How do you get code completion with a text editor?

For example: YouCompleteMe.

>How do you quickly access documentation for any type/method/function/etc. with a text editor?

ctrl-p plugin --> open file in differnt screen and look it up

>How do you easily manage dependencies and packages with a text editor?

vim Makefile?

>How do you quickly find usages of a certain type/method with a text editor?

I don't need a coding nanny holding my hand, but you can also use ctrl-p here, I guess?

>How do you find dead, unused code with a text editor?

-install command line tool for that
-run tool from within vim


Vim is just objectively better. It gives you access to many very useful plugins for programming. It's simply the better tool for the job. Sure, you can use an ide, but it's just slow and bloated for no reason.

>>How do you refactor with a text editor?
Refactoring isn't just about moving code around though. How do you rename your methods, types, namespaces, etc. everywhere for example? This isn't always as simple as a find and replace. For example, changing namespaces in some languages can require updating using/import statements as well, or removing them if the type is now in the same namespace, etc.

>Plugins
If you have all these fancy plugins that give your text editor IDE features, then it's now an IDE as well.

>Command line tool for this, command line tool for that
Is that really more efficient than just having it right there in your IDE?

Whoa dat level of strawman..

>They assume they never make mistakes and write perfect code all the time

Testing is a thing, you know?
Also: syntastic plugin for vim (there are probably similar tools for emacs or other text editors).


>They think IDE's are a crutch.

I've worked with Eclipse. Never again.

>They think memorising function names, return types, all that shit intellisense takes care of for you is actually useful somehow.

There are many autocomplete plugins for vim..

>the majority seem to have started programming on a text editor and a core reason they won't use an IDE is that they don't like change

Have you actually programmed in vim or emacs or are you pulling this out of your ass?

>Useless cunts

"Driven by hunger, a fox tried to reach some grapes hanging high on the vine but was unable to, although he leaped with all his strength. As he went away, the fox remarked 'Oh, you aren't even ripe yet! I don't need any sour grapes!' "

IDE does not integrate well with my environment. On windows I will use VS but on linux using an IDE is plain retarded, it doesn't even make sense, it's the opposite of integrated, it makes it impossible to write cross-platform software as you are dealing with stupid "project files" instead of a real build system. CMake can generate project files for most IDEs including VS, can cross-compile for different platforms, generate compilation databases, and does not need a gui toolkit to run. The only people who use IDEs on linux are stupid college students and kids who took some kind of programming class in HS using ubuntu and netbeans or some shit, it is totally impractical for making real software that will be deployed in a production environment.

>How do you rename your methods

:%s/old_method/new_method/gc


>For example, changing namespaces in some languages can require updating using/import statements as well

How often do you changed name spaces in the past, if I may ask?


>If you have all these fancy plugins that give your text editor IDE features, then it's now an IDE as well.

No, because:
-I choose to work as minimalistic as possible. I don't need to click through 8 levels of [OK]buttons to get cracking.
-And IDE doesn't give you the skills of a decent text editor like vim or emacs.


>Is that really more efficient than just having it right there in your IDE?

No, but it doesn't have to be. How often do you run dead code elimination?

Because I feel more productive with it. Also IDEs are rarely customizable enough for me

You can do all those things to a text editor. Just add the feature. Get some pre-made or make it yourself to function JUST the way you like it.

Text editors were invented for programming u brainlet

>If you can do things from within your editor, it is an IDE.
This is fucking retarded and you know it.
Just goes to show you IDE fags are legitimately nonfunctioning.

How are you programming then user? Accept the vim master race.

Okay, I'll bite. I'm an IDE guy but I'm willing to give Vim or Emacs a try. Can someone help me get started then?

What's better between Vim and Emacs?
Where do I find all these fancy plugins to make it good for programming?
How do I learn all the keyboard shortcuts and how long does it take?

you are so stupid it hurts.

Your sense of self importance is so inflated. Jesus Christ. Why the fuck would you care what some retards on Sup Forums thought of you?

Vain dipshit.

ITT: Retards who use a shitload of plugins to transform their text editor into an IDE and then pretend that they are not using one.
If it looks like a duck, swims like a duck, and quacks like a duck, then it's a fucking duck.

You use g++ for compiling, and gdb for deugging.

IDE on my main (asus x555lab) laptop but want to be like you guys on my thinkpad.

They use vim because it has a lot of shortcuts and shit you can do with needing to use your mouse or arrow keys.
youtu.be/F6-phM56H-Q

Can't tell you shit on the compiler or debugger.

Their compatible with windows 7?

without*

I use Visual Studio on a Celeron/4gb laptop and it runs fine, no lag unless I try to work on a gargantuan project (larger than anything I'd want to do with my home laptop).

I really like emacs though, org-mode is amazing. Still, I don't see the point in making up memes about IDEs.

mouseless editing

>Visual Studio on a Celeron/4gb laptop
Jesus how? I guess my work projects are huge... We have workstations with Xeons + 32gigs and they can bog down predictably.

Because I prefer a simple, easy to understand interface that doesn't get in my way. All of my build and debugging tools are available on command line and trivial to work with.

repo.msys2.org/distrib/x86_64/msys2-x86_64-20161025.exe

You're welcome.

My IDE interface is also simple and easy to understand, though I have been using it for many years now so i'm sure that is a good reason for why that is.

Meanwhile, any time I pick up any IDE I find that there are too many buttons in too many places, and I just want something to edit some fucking text. Moreover, they always try to shoehorn some sort of wonky project system onto me. I especially can't understand Visual Studio's .sln files. It's as if they weren't designed for humans to read and edit, and yet are nonetheless in plain text.

How am I supposed to trust that?

if you just want to edit some text then use a text editor. I do that all the time, but when I need to actually develop a software project I use my IDE. Solution files are pretty easy honestly, though you shouldn't be trying to alter them by hand (unless you know what you are doing) but editing things from within visual studio. They are essentially just a file that holds the group of project files and build settings.

>but when I need to actually develop a software project I use my IDE
A software project is just a collection of plaintext files. You edit the source code, you run a build script. You run a debugger if things fuck up. Lather, rinse, repeat.

>you shouldn't be trying to alter them by hand (unless you know what you are doing)
The syntax of the build system should be well documented and easy to understand, such that a build script can be developed without the use of automated tools. If a human cannot easily understand how it works, they cannot understand how their program is built, and they will be screwed when some part of the build process must be changed.

CMakeLists.txt is easy to understand. If the parameters of how the program needs to be built change, I can edit the build script without issues. The output files of cmake, Makefiles, are even more trivial, and their syntax is even taught in university classes.

you are doing it wrong then if you are wanting to alter visual studio projects/solutions by hand, or build them outside of visual studio. You can also alter any portion of the build process through simple interfaces inside of visual studio. The files are human readable too, I've had to do many things inside both the solutions and individual project files.

> If a human cannot easily understand how it works, they cannot understand how their program is built

Do you think compiling software is some esoteric act?

CMake is a good general purpose build tool, Visual Studio though is not meant to be "general purpose" but is instead focused on specific applications. I'm sure your aversion to it is just simply not having any experience with it, and you are set in your ways. So when something is "unfamiliar" to you, you simply throw it away.

>you are doing it wrong then if you are wanting to alter visual studio projects/solutions by hand, or build them outside of visual studio.
Honestly I design my programs to be built anywhere. Windows, Linux, ARM, x86... unless I have hard requirements to some platform I make things as generic as possible. I never use MSVC when on Windows, however.

>You can also alter any portion of the build process through simple interfaces inside of visual studio
You know what is simpler, more straightforward, and often better documented? Editing a text file.

>Do you think compiling software is some esoteric act?
Not at all. And it should never feel esoteric. When I run my build script, I should be able to at least figure out what all commands are being run behind the scenes and why.

>CMake is a good general purpose build tool, Visual Studio though is not meant to be "general purpose" but is instead focused on specific applications.
And most of those specific applications are better achieved with a general purpose tool. There is only one case where I could imagine Visual Studio is necessary, and unfortunately it is the one time I have had to use it.

>I'm sure your aversion to it is just simply not having any experience with it
I had had to work with it when developing Windows kernel modules for my master's research paper. It's a pain in the ass. Intellisense kept getting in my way so I typed the whole thing up in Sublime and pasted it over. Debugging with a VM through Visual Studio is half-broken and poorly documented. Using the GUI to change anything about building or debugging takes multiple clicks across a convoluted interface that could be replaced with a very small script.

Unless it identifies as a dog. Checkmate, pajeet

y-you win this round, user~

your spacing is giving me cancer

Vim has spellcheck built in baka.

B U M P

IDE's, and even most programmer's editors just piss me off. There's a LOT of garbage that just gets in my way...

Tabbed editing for example -- I'm a multiple display user, if I can't move just one section of code to another display, what's the point. Shoe-horning everything into one window is just stupid.

Needlessly crytic macro nonsense is another; if your code is complex enough and your habits sloppy enough to need any of that crap, you're probably doing something wrong.

Colour syntax highlighting is yet another bit of asshattery I just don't get, as the acid trip of colours makes it impossible for my eyes to focus and actually *SHOCK* READ THE CODE. Maybe it's because I've got ingrained indentation and formatting habits, maybe it's because I'm not punctuation blind... maybe it's because I programmed for at least a decade before there even was such a thing - but colour coding code just makes it harder for me to work with.

Stupid space-wasting toolbars. I know how to use the keyboard and to navigate menus, I don't need precious screen space that would be better used to simply show code

"command oriented" editors -- for **** sake I just want to TYPE!!! That's why I consider vi/vim/99% of the crap *nix-tards call 'editors' to be useless crap.

My first choice right now is Flo's Notepad2. Scintilla based, but it's not a steaming pile of Scite like a lot of other editors based on it. Most importantly while it defaults to all the things I dislike, it also includes the options to turn all that crap OFF.

... and it provides the tools I do like -- like indentation guides, block indent/de-indent with tab/shift-tab, block sliding with ctrl-shift-arrow, word-wrap indicators, word-wrap matching indentation, trailing blank stripping, blank line stripping, case conversion, regex search/replace, uri encode/decode, c escape encode/decode, tab to space/space to tab conversions, long line indicators, brace matching, and so forth.

Going to try that editor out

I honestly feel that most of you text editor fans are either 50+ and started before IDEs were invented or you have legitimate autism.

Soo when a person uses a text editor and already downloaded the appropiate compiler. You always use the cmd to compile it?

Why do buttons on a toolbar scare you so much? Nobody's forcing you to click them. The large majority of an IDE's GUI is a text editor area where you can click to place your cursor and just start typing like normal. It's much easier to jump into an IDE than something like Vim where you have to go through tutorials just to know how to even type text.

I've used vim to write essays in TeX but I guess that's a grey area.

Why?

I need a good C/C++ IDE, help

two windows in tmux, Ctrl+B Down.
Up, Enter. bam

vscode

Honestly, not joking, Turbo c++ in dosbox, I know it sounds retarded but it is literally the comfiest and most pzrfect ide I have ever used.

It's fast, intuitive and efficient. Text editors offer a greater order of language integration which is used in practical projects

Ohcool, pacman on windows

That' not an IDE

this

Vim is insanely faster and more powerful than conventional typing.

How long does vim take to load, on average, with those key development plugins? Would it be possible to alias things like dvim and have it load up vim with development plugins and then use vim to open up vim without those?

Vim system requirements: moderate to severe autism.

Im out....

IDEs aren't necessarily bad but they all seem to fall prey to feature creeping and turn into massive bloated laggy crash prone messes

youtu.be/SYGIQLruaFs
live in regret faggot

setting it up and getting used to it at first is not easy

but once you get acclimated to Vim you will never be able to use anything else afterwards without pain

Cross language. Mobil tools I take with me.

>that vertical highlight
my fucking dick

Shell
Shell
Do it yourself
Write a script
That one idk
Linter/ syntastic like plugins
Vim has plugins for that
Man pages/shell
Shell
Emacs has plugins for this stuff
I dunno

Enjoying emacs
Or enjoying vim + tmux really pisses off ide programmers

it certainly is an integrated development environment. I don't ever leave it when working on node/web/electron typescript projects just like I don't ever leave intellij idea (also an ide) when working on various java software. both integrate all the tools I need in one environment

No professional ever uses a text editor for programming. Sup Forums is a technological zoo, or a asylum where most mentally damaged people reside to measure their e-peen. They have ZERO idea of how shit works irl, which is why they shit on java , because of the pajeet meme. These are the people you should just look at, observe, and laugh at. Don't follow their advice. Their lives go by discussing intel vs AMD, their highlight of the day is what port is applel gonna remove. They spend their lives arguing how SICP is the best,they spend their days """configuring""" their shit distros because in it GIMP renders their loli wallpapers 0.000001ms faster. These people are human trash, always talking big but never actually accomplishing anything. 90% of them don't even program., or are uni students in CS101,just like 90% of /fit/ is DYEL. These people watch anime most of their time, and they ""code"" in text editors instead of IDEs because using vim and emacs reminds them that they have to get their carpal tunnel treated and that changing keybindings is totally a 1337 thing, totally. This is also why they have ""configured"" their distro to have a tiling wm with anime backgrounds, not because they like it but because it's aesthetic and schway. These people have never programmed anything above 1k lines(which was for their failed game they stopped working on), most complex thing they've made is a web scraping script in python, and they ""configure"" their distros following a step by step guide written by actual productive people for these normalfags in denial. Think about it. What kind of professinal, in his right mind would ever use a distro which he has to waste his time configuring ? I get it, distros need to be secure and customised, but people here don't actually care about that, they want to LARP . This board, is one big meme which you should cherish but never adopt. Only thing they're right to some extent (aka the good memes) about is thinkpads.

>No professional ever uses a text editor for programming.
actually over 50% of them do
also stopped reading there

>inb4 replying to copypasta

IDE is a crutch that hides the fact that your code is becoming too complex. Reading a mountain of autogenerated IDE boilerplate code is torturous. If you use an editor with just a couple most useful tools, you'll be forced to make your code terse and easy to understand in order to keep control over it, and everyone who will ever maintain it will be thankful for that.

>IDE is a crutch that hides the fact that your code is becoming too complex.
no, it hides the fact that it's becoming COMPLEX. and very often you can't avoid complex code, unless of course you're a /dpt/ fizzbuzz programmer