Ryan is an engineer in the Sacramento Area with a focus in Python, Ruby, and Rust. Bash/Python Exercism mentor. Coding, physics, calculus, music, woodworking. Looking for work!
Calling VS Code a slow editor seems like a bold choice. Keep in mind that speed is mainly a function of familiarity. I'm not 100% there with Vim -- I'm not even probably 20% there -- and so my progress and productivity are a bit slow. Sometimes I just need to bust something out and get it done, and, since I'm used to GUI's and clicking things, I can still get a lot done that way, fairly quickly.
While I'd love to do more things and be more productive in Vim, right now, I'm most productive in VS Code, especially for largeish projects.
That's fair! I mean you're right! I didn't mean to be that aggressive on that opinion... and it's really true that, once you're used to any editor of your choice, the compete result will come faster than if you've used another editor that you're not so comfortable...
My point was kinda about my own experience of having to wait for considerable seconds when opening large files or multiple files, and some delays when you try to use these modern editors VSCODE/Atom/Sublime with some features like linters etc...
I think that in the end, it's better to invest a little bit of time on vim in the beginning than having to deal with that delays from those editors for ... (I don't know how long)..
Ryan is an engineer in the Sacramento Area with a focus in Python, Ruby, and Rust. Bash/Python Exercism mentor. Coding, physics, calculus, music, woodworking. Looking for work!
Yeah, that makes sense. You can't beat the productivity and keyboardiness of Vim, especially for editing config files and small scripts and projects. I'll have to keep working at it to get good enough to do larger projects with it.
If you haven't tried VS Code in a while, consider giving it a go, as it's gotten significantly faster.
Thanks for the advice!
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I've seen on your other post that you've tried Vim before, how could you go back and adapt to slow editors again, like VS Code?
Calling VS Code a slow editor seems like a bold choice. Keep in mind that speed is mainly a function of familiarity. I'm not 100% there with Vim -- I'm not even probably 20% there -- and so my progress and productivity are a bit slow. Sometimes I just need to bust something out and get it done, and, since I'm used to GUI's and clicking things, I can still get a lot done that way, fairly quickly.
While I'd love to do more things and be more productive in Vim, right now, I'm most productive in VS Code, especially for largeish projects.
That's fair! I mean you're right! I didn't mean to be that aggressive on that opinion... and it's really true that, once you're used to any editor of your choice, the compete result will come faster than if you've used another editor that you're not so comfortable...
My point was kinda about my own experience of having to wait for considerable seconds when opening large files or multiple files, and some delays when you try to use these modern editors VSCODE/Atom/Sublime with some features like linters etc...
I think that in the end, it's better to invest a little bit of time on vim in the beginning than having to deal with that delays from those editors for ... (I don't know how long)..
Cheers✌️✌️
Yeah, that makes sense. You can't beat the productivity and keyboardiness of Vim, especially for editing config files and small scripts and projects. I'll have to keep working at it to get good enough to do larger projects with it.
If you haven't tried VS Code in a while, consider giving it a go, as it's gotten significantly faster.
Thanks for the advice!