you are viewing a single comment's thread
view the rest of the comments
[–] 64 points 3 years ago (6 children)

But that's something new to learn and configure. I just want to code why should I spend my time learning another text editor when vscodium is fine

  • source
  • parent
  • hideshow 12 child comments
  • [–] 57 points 3 years ago (3 children)

    Careful. You're in a linux-heavy audience. They're the kinda people who would spend a few weeks setting up systems to use it for a few minutes.

  • source
  • parent
  • hideshow 6 child comments
  • [–] 7 points 3 years ago*

    That's simply outrageous!!! As soon as I finish tinkering with my system, I'll prepare a proper reply...

    On a more serious note though. Don't overlook the role of procrastination in the endless tinkering many put on their boxes. I'm speaking from experience.

  • source
  • parent
  • [–] 5 points 3 years ago

    I'm a full-time Vim and Linux user when writing code. I agree with the statement that "simply switching" editors is very naive. I'm my personal opinion, you should decide on an editor that makes sense to you and learn to be very good at it. If VS Code is that answer, then great. Not everything points to Vim or Emacs.

  • source
  • parent
  • [+] 5 points 3 years ago (3 children)
  • [–] 23 points 3 years ago (2 children)

    Vim and EMACS require tons of plugins and a brain transplant to feel confortable using them.

    And the new personality tends to be somewhat evangelical about the editors 😄

  • source
  • parent
  • hideshow 4 child comments
  • [–] 1 point 3 years ago (1 child)

    But isn't atom and vscodium almost the same stuff?

  • source
  • parent
  • hideshow 2 child comments
  • [–] 1 point 3 years ago

    I'm still using sublime to this day. It keeps getting worse and falling behind VSCode with every new feature that never comes gets to it, but I have so many pet peeves with VSCode that everytime I try it I soon give up. I wish there were more options these days, but as the expected feature sets get more complex the number of options keep going down.

  • source
  • parent
  • [–] 0 points 3 years ago* (1 child)

    Same reason why a carpenter should learn to properly use hand tools, or a teacher should keep up on literature. In other words, master your tools. It doesn't matter which tool you use, provided you can use it to its full potential.

    I occasionally use VSCode, but I mostly use ViM because that's my tool of choice.

    For another reason, if your ever in the situation where you need to work on something on a remote server or an unfamiliar machine, knowing ViM means you can at least be somewhat productive when you don't have your normal tools available.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 1 point 3 years ago (1 child)

    I know vim. I'm using vscodium with a vim plugin. I was coding in pure vim for half a year because my Laptop with 4 gigs of RAM couldn't handle vscode. I just don't want to configure vim so it does all the stuff VScodium does for me

  • source
  • parent
  • hideshow 2 child comments
  • That's fine, use what works best. I think there's value in getting at least the basics working, such as syntax highlighting and linting in case you want or need to use it again.

    The question was why one should learn to use something like ViM or emacs, not why anything else is a poor option. Master your tools, regardless of what they are.

  • source
  • parent