What’s the Big Idea? PhpStorm for VIM Users

By Eric Van Johnson

I started my IT career in system operations. I spent many days in a cold data center, racking and stacking servers, installing operating systems, and configuring routers. That’s when I started using Vim. It was nice to sit in my cubicle outside the data center and access my servers to do everything I needed in a terminal, including editing files. I didn’t put any real thought into why Vim. It was just an option available on the command line to allow me to edit files. There were others—Nano, Emacs—and today, I couldn’t honestly tell you why I didn’t opt for one of them instead of Vim. But Vim did the job well, so I stuck with it. by Eric Van Johnson

This article was originally published in the May 2024 issue of php[architect] magazine. To read the complete article please subscribe or purchase the complete issue.

Responses and Pingbacks

I have just started using VIM motions in my IDEs phpstorm and vscode. One issue I constantly run into is slowness in PHPstorm (our company has a large monolithic architecture), I think once I am proficient in VIM motions, moving to vim as an editor would increase productivity.

Leave a comment

Use the form below to leave a comment: