Switching to VS Code


#21

The lack of solid code highlighting in php makes this a non starter for me. After seeing this thread I hoped it changed. It didn’t.


#22

I’ve been using it to replace Atom for the past two weeks and I’m enjoying it. Took a few settings to get shortcuts and other behaviors back to what I like, but it’s much faster and smoother than Atom.


#23

Perfect timing. Unsatisfied with Sublime after 5 years, and PHPstorm not resonating, I’ve been contemplating Atom vs. VS Code. All recent chatter has pointed toward VS Code, especially this discussion. Just installed today. It seems vastly superior to Sublime in every way: extension system, GUI, git integration, “just working”. Perfect balance between text editor and IDE, for me. I get my new Mac today: I’m going to force myself to switch to VSC by not installing Sublime and see if I survive.


#24

Hardest part of the switch is removing the muscle memory to write sublime / and instead code . in the cmd line :smiley:


#25

I found the git integration a bit hard to use. I use git-plus on Atom and it seems much easier to add files, commit, and push them. Don’t need a separate screen for it. Does anyone have a good guide for git with Code? Overall, it does seem faster than Atom.


#26

@romero2k Try the GitLens extension


#27

This thread has almost interested me enough to give VS Code a try.

I have to say though that currently I’m firmly welded to Atom. I’ve used it since it first appeared and it’s been a fascinating journey. It may have a reputation for being slow but things are improving with every release. I’m running Ubuntu on a powerful Dell portable workstation and it honestly flies.

Text editors have a vaguely religious whiff about them. In the church of Emacs they say that the use of vi is a penance, not a sin. Not sure the same could be said of VS Code. :laughing::laughing: