Although this article is written in Vim, I am far from the most efficient user of the text editor in existence — between my memory and Google, I've managed to get by over the years.
So when I came across VimSpeak, I expected a world of schadenfreude to appear. But no, the Vim grammar actually translates very well to spoken language, as you can see below.
From the point of view of a beginner, I think users are far more likely to remember "change surrounding brackets to parens" than the "cs])" keystrokes that are needed. Or until they type that command out a dozen or so times to get it remembered properly.
In case you think it is just for silly toy examples, here's a VimGolf challenge to turn XML into JSON:
However, the really unexpected part of this whole VimSpeak project is that it is written in F#, by Ashley Feniello, a Microsoft-employed developer. That's the reason for the Visual Studio project files on GitHub, and the fact that it needs to use the .NET's speech recognition system.
Feniello wrote on the project's GitHub page that he has only tested it in Visual Studio, Sublime Text, and Vim, on Windows 8.
If nothing else comes of this project, it is yet another sober reminder that there is always more Vim to grok.
Some would say that it is a long way from software engineering to journalism, others would correctly argue that it is a mere 10 metres according to the floor plan.During his first five years with CBS Interactive, Chris started his journalistic adventure in 2006 as the Editor of Builder AU after originally joining the company as a programmer.Leaving CBS Interactive in 2010 to follow his deep desire to study the snowdrifts and culinary delights of Canada, Chris based himself in Vancouver and paid for his new snowboarding and poutine cravings as a programmer for a lifestyle gaming startup.Chris returns to CBS in 2011 as the Editor of TechRepublic Australia determined to meld together his programming and journalistic tendencies once and for all.In his free time, Chris is often seen yelling at different operating systems for their own unique failures, avoiding the dreaded tech support calls from relatives, and conducting extensive studies of internets -- he claims he once read an entire one.