It’s been some time since I first got my fingers on VIM. My first impression was - as everyones I guess - pretty bad. VIM is not that easy to understand, yet a powerful, shortcut-based, distraction free editor. I’ve already written about turning Sublime Text into VIM mode and my very first VIM impression, but back then I just copy & pasted everything I found on the Internet into my .
View full postSince I’m still trying to really get why so many (Front-End) Devs love VIM I tried to find a “good” way to integrate it into my daily workflow. Since I’m working in a relativley small company it’s most of the time stressy to get all things done and to keep an overview - so long story short: There’s not much time for new tools that don’t increase my workflow directly. VIM is one of these tools that don’t fully support my workflow at the moment.
View full postWhen I first looked at Vim it was a very short experience that was literally as follows # from the command line vim test.md *vim opens* "What's that?" *CTRL + C* "How do I even close this?!" *opens browser, googles "how to close VIM"* ESC + :q That was it and that was my Vim experience for quite some time. However, lately I see more and more people talking about Vim being the single best editor for everything - no matter what language one writes.
View full postI first tried Brackets back in my Windows time. It was a very early version, kinda heavy and wonky and not what I wanted from an editor I use on a daily base at all. Just today I decided to give it a second look because beside VIM it is the editor I read quite a lot about latly. My first impression was: “Wow, that’s a simple, clean editor!” - exactly the thing I liked so much about Sublime Text 2 which I’ve been using for the last two years or so.
View full post