5 ms·
I probably started using vi in 1989. What I learned then I still use all the time. On the other hand, I primarily program Android at work, and in 2009 Android
by Ologn 5y ago
I probably started using vi in 1989. What I learned then I still use all the time.
On the other hand, I primarily program Android at work, and in 2009 Android recommended I use the Eclipse IDE, so I learned how to use that. Then starting around 2013, Android said they were shifting from Eclipse to Android Studio, so then I learned that. Android Studio has odd keyboard shortcuts - on a Linux (or Windows) box you jump to a line by hitting Control-G - on a Mac you hit Command-L.
The vi on my Mac and Linux seem fairly similar in terms of keyboard shortcuts and what I use now on both of them is what I used in 2013 and what I used in 1989 as well, and I have used it for a host of things. Whereas even in the specialty of Android programming, the recommended IDE switched some years back, and it has differences on different platforms.
- voakbasda 5y agoThis is the right perspective. Not “what can it do for me today”, but rather “what will it do for me over my entire career”. The future of vim is more vim. I have been using vi and its descendants for over 30 years, and the core behavior is the same as it has always been. It has done all I ever needed, and it works everywhere and over slow connections. The future of VSCode is at the mercy of Microsoft, and that absolutely will change under you without warning. They control the value of the skills that you learn. Why would you take that risk?
- nickd2001 5y ago+1 And a future job might disallow you from using VSCode for some arcane reason. Why would that happen? well workplaces do weird things sometime.. Whereas they can't really stop you from using vim. :)