Fork me on GitHub

Subject:*
Name/Email:*
Message Icon:*
Message:*
url email imgsrc image php hide code quote
SAMPLE
alignleft aligncenter alignright bold italic underline linethrough   


 [more...]
Options:*
 

 

 
View requirements*
Reply No requirement
Confirmation Code*
  The code is case-insensitive  Click the image for a new code. | Maximum attempts: 8
   
Re: VS Code

by fiammybe on 2019/5/3 6:47:52

I tried it on and off over a period of a year more or less, and I think I'm just too used to the way PHPStorm is working. I had a very hard time with the way VS Code handles its Git integration, and a few other things that I just didn't want to invest time in to figure it out

If PHPStorm isn't available though, VS Code would be my second choice in a heartbeat. The plugin system has a wealth of functionalities, something that has been on the backburner a bit in PHPStorm lately.


VS Code

by Madfish on 2019/5/2 19:18:14

Just a short note to say if you haven't tried the VS Code editor yet, it's well worth the effort.

I have always used Netbeans up until recently. It's ok and does the job, but it has a few issues that never seem to get fixed like needing to force FTP transfers and popping up huge tooltips over the line I'm trying to work on. And the interface kind of hurts my eyes (well, being Java based you kind of expect that).

I don't like changing editors but I eventually got annoyed enough to give VS Code a go and wow is it good. It's not that it does anything new, it just gets so many of the little things right that you actually end up getting more work done, because you aren't fighting the editor.