Does it pay off in the long run...

thanks for giving me eye AIDS

>falling for such obvious bate

I don't like autistic editors, but recently I've switched from nano to spacevim because - unlike nano - it has syntax highlighting and code completion. I only use it for editing files over ssh and would never do my everyday coding with it. Invest 1 hour of your life into learning how to use it, but no more.

Hello Ganeesh. How to the code off IDE sirs ?.

Attached: shitcoder.jpg (474x727, 52K)

vs code + vim extension

99% of the functionality with only 1% of the autism.

wasting time learning useless bullshit to feel like a 1337 hacker is the MO of freetards tho

It literally takes half an hour to learn the basics of vim

Fucking normies man

Yes, it's an excellent training ground for evil-mode until you finally see the light.

emacs

Attached: 1556933473751.jpg (931x873, 227K)

>c++
>beautiful and cleanly designed

> Years

Are you retarded ? I've been using it since i was 15, and i learnt it in a week at most.

The time you spend typing is negligible. The most important part about programming is thinking how the code goes, not just typing.

i use it to quickly fix spelling errors in small files on command line then push to git and deploy quickly. if youre using vim to develop java from scratch youre fucking autistic

This is true, but the typing part is boring so the less you have to spend on that the better.

For the same reason you want a powerful CPU for programming: compiling might only take a second or two but it's a boring and annoying second or two and if you can cut it down to under .5 sec that's great.

I'm referring to God-tier editing skills

Oh god what the fuck is this god awful website

How would a moron like you know anything about the time required to gain what you perceive to be ``god-tier'' editing skills? Any basic vim trick would be ``god-tier'' for subhumans like you.

you can be efficient in vim by just learning 15-20 shortcuts. if that takes you years, then you might not be cut for programming. not saying everyone should use vim btw

This. vi/vim has its place as an editor for quick fixes (like in sysadmin situations), but actually using it for large, full programs is a huge pain in the ass.

How so? Most people develop large JS projects (for example) with regular text editors, what makes Vim any less suitable for these use cases?

>years
maybe if you are fucking stupid, took me 15 minutes with vimtutor

Uh it takes like a month to learn Vim.

Yes. It pays off.
Basic text editing is no more complicated than other cli text editors. You will keep on learning more useful tricks and features the longer you use it.

I've been using linux for

>hides C++ code
kek

you dont have to know everything about vim in one go, you can be productive with a small subset and increase your knowledge from there.

Nobody masters vim in a month or a year.
You may stop learning in a month, but that just means there's a lot you don't know.
The longer you use vim, the more you learn about it.

wanted to see if it's a meme so i switched to it from vscode and never went back.

This right here is the answer to everything.

>open terminal
>vimtutor
>hit enter
wow op I learned vim in like 20 fucking minutes

Lmao @ coping c++ fags

Learn the keybindings and use them on any editor of your choice. It may shave off a sliver of time when typing, but if you program daily, that adds up to a great amount over time. Just learn the basics of moving around, copying, deleting, and pasting, then lastly macros, and then you’ll be golden.

>hjkl instead of jkli
WHAT WHERE THEY THINKING?

Attached: f.jpg (800x450, 41K)

>not emacs

Every vimmer I know has installed so many plugins that they may as well just fucking use Emacs

Most of the skill involved in being "God-tier" in editors is actually just skill at writing code and having things planned out in your head in advance, and those skills transfer between editors.
Someone who is "God-tier" at emacs could switch to vim and be just as fast as they were in emacs within a couple of weeks.

Basically: if you want to build a bookshelf, knowing how to use every one of hundreds of tools in a workshop wont make you able to build the bookshelf any faster. Knowing the steps to building a bookshelf, and being able to plan out the steps with whatever tools you may have is what will make you efficient and fast.

ChangeInnerWord
ddelete line
ChangeInner"
ChangeInner{

oh, man, how will i ever remember these keybindings?

this, I find it requires less brainpower over keybinds

That was the layout of the keyboards.

Attached: 500px-KB_Terminal_ADM3A.svg.png (500x162, 13K)

compared to java, sure
of course the future is picture related

Attached: 1553862210308.jpg (554x554, 30K)

If you have to ask, it’s probably not worth it

Don't you guys have mice?

Attached: phones.jpg (1280x720, 61K)

They weren't retarded gamer kids like you and realized that hjkl were all on the home row.

shouldn't even take one year if you actually use it as your only editor and try to keep learning

>Why take years to learn this
It takes a few hours to learn the basics, which is more than enough to code.

No generics

Promptly leave this imageboard and go back to where you came from, Ledditor.

You don't need '''god tier''' skill to use vim and be efficient.
Just go through vimtutor and google 'vi graphical cheat sheet', print it and hang it some were in front of your face.

You can only benefit from vim/emacs if you can touch type well, and you are using a verbose language like C++.
Otherwise your typing is bottlenecked by your thinking.

You have to setup everything that would otherwise come out of the box with an ide. Clipboard is not interchangeable without custom recompiling flags and too many plugins will make it run like shit.

this. it takes, as a ballpark estimate for any random person, 30 minutes to learn how to do 'what they can do in xx editor' in vim. After that, you're at the same speed you were in the previous editor and anything else you learn can only be improvements in editing speed.

Text editor != IDE, and i'm fairly certain most IDEs come with some semblance of vim key binds. However, you can continue to use vim keybinds in your text editor for editing text files, config files. when you say clipboard is not interchangable you mean you can't use it between, say, vim and your web browser? have you tried the + register?

it feels good desu, atom or vscode is bloated af and triggers my ocd

kek.

learning xorg - pain
learning vim - pain
learning bash - pain
learning mutt - pain
People use all their life for practice linux skills.

>learning is hard, better give up
>if you learn something you need to learn everything about it in its entirety
if you don't practice something, you lose it, it's a fact of life.

It doesn't take years. I learned both vim and emacs from the printed manual that came with my first linux distro while waiting for the install to finish. Now that there are plenty of other good editors around those are not as important as 15 years ago, but it is such a small investment that you could do it anyway just for fun. Also writing a vi clone might be a cool little project for a 1st year cs student.

I'm at the tier of vim autism, moving about without vim keybindings is an absolute pita. I'm using them everywhere, not just for moving around text but moving around everywhere

it's not even autism, it's just comfy. it kills me that the only vim package i can find for sql server management studio is paid and it's actually pushed me to use linqpad (paid still, but at least it has native vim support and other shit included) just to get vim keybinds in my sql writing.

No generics

>using Go when you can use Elixir

Checked

>Does it pay off in the long run?
It takes about a week to learn the basics and it pays off because you're never without a very powerful editor. vim works on everything everywhere so you're never without it.

Attached: arturo.jpg (500x500, 57K)

No, it's shit held together by bubble gum. Just bind alt+hjkl or alt+wasd as directional keys in a less fucked up editor and get on with life.

>t. has no idea how to use vim
it's more than just holding hjkl or w/e and moving in that direction and the fact that you just assumed that's all vim was shows how dumb you are.

>he's not going mouseless with Vim
youtube.com/watch?v=E-ZbrtoSuzw

>wanting RSI

>Clipboard is not interchangeable without custom recompiling
the gvim package ships with a clipboard included compiled vim binary

My new collegues make fun of me when I type nano. Halp.

>Does it pay off in the long run?

Yes

>Why take years to learn this when I can get straight to coding

Because it only takes a few days to learn enough to be as fast and productive as notepad++ or VS Code or whatever the fuck you're using now.

From then on you pick up a bit more each week until you can edit code at the speed of thought (roughly 6-12 months if you pick a few commands here and there every week.

I mean try vimtutor yourself and see. You asked a loaded question so I'm guessing you already decided its not worth it and came here for validation. Try it yourself

#LearnToCode

youtube.com/watch?v=OvrmZ_9KX30

Attached: Tucker Covers ‘Learn To Code’ .jpg (474x248, 29K)

click nano instead, only troglodytes use CLI

It's a lot like learning regex. Both are powerful tools for dealing with text with some amazing simple features that can pretty quickly get you returns, but they take years to master fully.
Vim can even be thought of as a text editing language, much like how regex is a pattern matching language. Unlike regex, Vim is not ubiquitous, so if you've already mastered some system for generalized text modification it's not worth it.
However, if you've ever refactored a semi-repetitive code pattern manually over a huge codebase and thought "there must be a better way", maybe you should give it a try.

Hi nice to meet you, I have very few plugins. Now you know someone who doesn't.

I don't understand.
Why use text editors? What are those tools people say text editors have? What does text editors have that IDEs doesn't? Why there aren't IDEs that can do what text editors can?
I'm new into programming so I just use Code::Blocks. But it fails me a lot. I wanna change. But I just don't understand. You type your code in one program than copy it to an IDE to run it?
Since I'm an n00b, I have to troubleshoot a lot. This workflow seems terrible to me.
I just want to understand.

Attached: 1442985450868.jpg (393x390, 46K)

>takes years to learn
Yeah, if you're a brainlet.

You dont need IDE to compile

So I can compile directly from the text editor? this is a native feature or I have to configure it?
I think I'll give notepad++ a shot

Type your code into Vim and then run gcc (or whatever other compiler) on that code to make an executable. The process is actually far simpler than using an IDE.

You don't compile from the text editor. You compile with a separate compiler. The text editor is just used for writing your code.

Ok, but which features make it better than an IDE exactly?
And if you can compile in a text editor, what does an IDE do?

Attached: 1442985478381-1.png (287x318, 107K)

It's just personal preference. Neither option is inherently better, they're just different. I personally like using Vim because it's easier and faster to remember keystrokes than it is to navigate a plethora of menus.

>you can compile in a text editor
You can't though.

I see. Would you recommend notepad++ to a beginner?

No. There's no reason to fuck up your brain with meaningless garbage you'll abandon later anyway if you're even a half-decent programmer. Just use whatever you use for now and learn vim on the side till you feel more comfortable in it. Download vim and run vimtutor.

>using a google product
it will be abandoned in a couple years just like angular

also:

>Years to learn vim
It takes less than an hour. Open a terminal emulator window and type 'vimtutor' and it'll launch an interactive vim tutorial that takes 20-60 minutes depending on your typing skills and comfort with the 'home row'. You can also use graphical frontends like gvim.

A generalized text editing language. Need to refactor a variable code pattern in a 100,000 line codebase automatically? Vim can do that.
>what does an IDE do?
An IDE is just a GUI on top of build and development tools. That's it. Many people prefer using individual development tools because IDEs can have slow GUIs and obstruct a lot of options.

Code::Blocks is the reason I switched to Linux and modular development tools over IDEs. I was learning C, and all I had to do was enable a single flag for gcc. I looked up the instructions online, and I had to go through tens of steps and deep menus just to enable a single flag. It just wasn't working, and none of the logs gave a hint.
At the bottom of one of the guides was an alternative solution, I still remember the words:

If you're on Linux, just type `gcc -O3`

From that day on I was hooked. I never want to go through menu hell again.

You're very obviously confusing vim with emacs. Vim's bindings are all based around the 'home row', as that's where your fingers ought to be when on the keyboard, so all of the important keys are *literally* at your fingertips. Emacs, on the other hand, was designed around LISP and at the time "the" LISP keyboard with the Space Cadet keyboard, so a lot of the emacs bindings were designed with that keyboard in mind. I'll never understand the people that use emacs without at least a space cadet clone, as it's the most godawful uncomfortable, unintuitive garbage ever on a standard keyboard. There's a reason you can find so many add-ons out there for popular software to add vim keybindings. Vim is laid out for efficiency and ease of use. The only time it's not incredibly intuitive is when you're using a non-standard layout like Dvorak, and even then you can change vim's default binding to Dvorak's home row or whatever the "resting position" is.