What most people forget when they argue against learning vim is that vim is more that just a text editor, it's a whole new philosophy. Once you learn it, you can find it almost everywhere. Learning vim key-bindings was the first thing I did after learning to touch-type, and now I use the same key-bindings on VSCode, Intellij, a remote server I am SSHed into and with the help of Vimimum, even chrome!

And if ubiquity isn't enough, then I would point you to this article which does an awesome job explaining the really idea of vim, composability.

https://medium.com/@mkozlows/why-atom-cant-replace-vim-43385...

Unfortunately, vim macros don't tend to get implemented when other editors implement keybindings.

This is unfortunate, vim macros are fantastic for reformatting text.

Maybe not all of them, but you can use macros in IntelliJ and VSCode implementations (and, of course, Emacs).

Exactly this. Vim is special because it's what we've all agreed on as a standard for modal editing. Luckily, it's also pretty darn good, but that's secondary. Learning one set of commands that can then be used across editors, operating systems, and even terminals is amazing.

> Vim is special because it's what we've all agreed on as a standard for modal editing.

Well I didn't vote for you...

In all seriousness, Vim's keybinds are only popular because no one has really tried to make a good modal editor with different bindings. It's prohibitively difficult to change the bindings in Vim, and prohibitively difficult to change muscle memory, but I still wish that I had a good modal editor that didn't resemble Vi.

It's a similar story with keyboards and qwerty.

chrome? how?

> with the help of Vimimum, even chrome!

Even though OP made a typo, he more likely wanted to say Vimium.

Also "Vim vixen" for Firefox.

I think he should make it clear who these roadmaps are for. From the looks of it, definitely not a beginner, but probably for someone who has spent atleast some time in the field.

>You may not: use the Programs for any data processing or any commercial, production, or internal business purposes other than developing, testing, prototyping, and demonstrating your Application;

From what I understood, I as a student could still use java 11 from Oracle, as I wouldn't be using it for "production". Is that correct? Or are there other implications that I am missing here?

Yes, that is correct. This trap is for hobbyist and professional developers whose typical workflow involves downloading Oracle's JRE to deploy their app, probably not noticing the new trap clause deep within the license agreement.

My professional advice to a newcomer to the industry: stay away from Oracle. It is a blight on the software industry. Oracle is a monopolistic anti-consumer patent troll that treats its employees like shit and whose only business ethic is "make money by any means available".

Seconded. I only wish it was easier to convince management that the cost of switching from Oracle products is worth it.

Vendor lock in is a real bitch.

I suspect you're right, but does Oracle JDK really add any appreciable value over OpenJDK, for a student?

I'd go for OpenJDK simply to form good habits.

Yea ... and if you do start to build something and decide to release it commercially, you don't want to run into any weird Oracle/OpenJDK weirdness at that point .. so best to start with OpenJDK.

Nothing really, I was just curious about that.