This was OK but still required a significant amount of configuration and caused the editor to operate almost unusably slow. Next I tried IntelliJ Ultimate which attempts to allow multiple technologies within the same IDE. While they had some level of settings sync it simply wasn’t very good. With this I found myself having to switch editors far too often, even within a single project. First I bought the remaining JetBrains suite. To make it all work together I tried two approaches. While PhpStorm could handle the WordPress code it simply couldn’t handle the others. I got the chance early last year with a new team that had me working on a mix of GoLang, WordPress plugins, Python and a few other techs. Originally I planned to go back to PhpStorm when I needed to work on WordPress code or if I was to switch teams. Within a few weeks I stopped opening JetBrain’s IDEs and relying almost entirely on VS Code to get my work done. I bought JetBrain’s GoLand IDE but it simply couldn’t keep up with what VS Code could already do for free at the time. ![]() I first tried VS Code in 2018 when I started working on a project in GoLang. The issue is that, even a well established paid product like PhpStorm, just can’t keep up with VS Code. I will gladly pay a small team for a quality product and would rather do so that jump on another big-tech bandwagon like VS Code. I say this because, as I’ve moved back to VS Code, I want to emphasize that it wasn’t the price of the alternatives that prompted the change. To get a “real” code editor you had to pay up and that was OK. Editors Like Sublime Text and others could do some of this but just weren’t up to the task of making development easier day in and day out. The ability to easily integrate WordPress coding standards and tools like Xdebug out of the box and without a lot of fuss was so important. In the WordPress world this was definitely true. Price Isn’t Everythingįor a long time conventional wisdom was that a true IDE (VS Code is not a full IDE) was “better” for deep development work. Every time I do I just wind up back on Visual Studio Code (VS Code). I haven’t really used them since 2018, though I keep re-installing PhpStorm every 6 months or so to try it again. ![]() This year marks the final expiration of any JetBrains licenses I’ve paid for since moving to PhpStorm. In many ways PhpStorm was the perfect code editor for WordPress code, or so I thought. I was such a fan that I converted many people to it since I had started using it myself in 2014. Prior to working at WP Engine I was a die-hard fan of JetBrain’s PhpStorm IDE for WordPress code.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |