Pretty cool with the editor interaction.

Also worth bearing in mind most shells can do this sort of thing easily enough too.

The example from your video with zsh's zmv (bundled: https://github.com/zsh-users/zsh/blob/master/Functions/Misc/... )

  > touch btn_google_{signin,signup}_dark_normal_web{,@2x}.png # create files
  > ls -l
  .rw-r--r-- 0 gaving 31 Dec 10:34 btn_google_signin_dark_normal_web.png
  .rw-r--r-- 0 gaving 31 Dec 10:34 btn_google_signin_dark_normal_web@2x.png
  .rw-r--r-- 0 gaving 31 Dec 10:34 btn_google_signup_dark_normal_web.png
  .rw-r--r-- 0 gaving 31 Dec 10:34 btn_google_signup_dark_normal_web@2x.png

  > zmv -n -W btn_*_sign*_dark_normal_web* *_sign_** # dry run
  mv -- btn_google_signin_dark_normal_web.png google_sign_in.png
  mv -- btn_google_signin_dark_normal_web@2x.png google_sign_in@2x.png
  mv -- btn_google_signup_dark_normal_web.png google_sign_up.png
  mv -- btn_google_signup_dark_normal_web@2x.png google_sign_up@2x.png

  > zmv -W btn_*_sign*_dark_normal_web* *_sign_** # change files
  > ls -l
  .rw-r--r-- 0 gaving 31 Dec 10:34 google_sign_in.png
  .rw-r--r-- 0 gaving 31 Dec 10:34 google_sign_in@2x.png
  .rw-r--r-- 0 gaving 31 Dec 10:34 google_sign_up.png
  .rw-r--r-- 0 gaving 31 Dec 10:34 google_sign_up@2x.png

Interesting to see an article about this, I knocked together a React app the other month for my company based off questions from rands famous "Shields Down" https://medium.com/the-blueprint/shields-down-c291f015618f using this method.

https://github.com/gaving/happy-or-not

Never got around to analyzing the data, too scared.

Are you kidding? Go take a look! Either you feel good about your company, or you get a chance to make it better - you win both ways!

Nothing to hide; nothing to fear, right?

Identity theft would be my biggest concern.

"5 minute drive"? Buy a bike and chuck out 0600-0700!

I very strongly considered it. Or just walking (3 miles). The two hold ups are that I don't want to turn up to work all sweaty (or wet, or frozen etc) and to a lesser extent carrying all my stuff (purse, wallet, coffee, lunch).

Also going home for lunch is highly convenient and I really like that nap.

I wouldn't have to bike/walk every day of course. I am still considering it (clearly).

I'd certainly try it out for a day or two a week, backpack / jersey pockets for stuff.. easier if you have a locker or showers at your work. Hopefully you wouldn't arrive too sweaty after 3 miles which should take you about ~15 minutesish.

Win-win though, exercise and if you get in to it less fuel costs. Could easily clock up 30 miles a week and extend your route on nice days.. no brainer!

The best thing you can do to avoid getting sweaty is use either a basket or pannier bags to carry your stuff.

not for much longer https://www.youtube.com/watch?v=rzclz1seo0g

Neat D3 based globe component, don't suppose the source is anywhere?

I'd like to know as well. Cool ASCII art in the Console.

Aren't most people using neovim now?

I personally use nvim, but most of my coworkers (also vim users) haven't yet switched. There's a surprising number of people that are aware of nvim but haven't bothered switching because vim works fine for them.

The main selling point for neovim when I found out about it was the async plugin support. And I remember reading that the creator of neovim mainly did it because the maintainers of vim refused to accept his patch to add async plugin support for vim.

But about a month ago, vim added async plugin support. So now what? I switched to neovim, and now I am undecided if I should switch back to vim or not.

neovim has a fresh start, cleaner code base but less support/timetested code than vim. What do you guys think?

My understanding was that Neovim's main strength was the fact that it is a fresh rewrite for modern platforms only. Whereas Vim has tons of legacy code in it for all sorts of legacy platforms, which makes it harder for people to contribute code, and makes it harder for the dev team to find and fix bugs, or to add features, etc.

In any case, whatever the outcome of the fork is, this is an interesting experiment : Will the cleaner code base, using more extensively tests and CI move faster than the legacy one ?

Not accounting the number of people contributing to each project, the logic said it should. It will be interesting to see how long it takes to pay the dividend.

No, not at all.

neovim is still lacks stability.

Is this from experience? I've switched back to regular vim from neovim because of platform support, but I've never had stability issues when I did use neovim.

Yes, it's from experience. I'm maintainer of https://github.com/SirVer/ultisnips snippet plugin for vim, and I'm often see issues when people can't get it work under nvim due nvim internal issues.

From experience:

neovim often forgets basic settings for indentation, it's the only flaw I've experienced myself but it's enough that I can't use it.

Not that I know of. I mean, I've been a heavy vim user for years and haven't even bothered trying neovim.

If you don't have to support win32 platforms, I'd say go with Electron.

Other than that, features pretty similar.

Announcement: http://nwjs.io/blog/v0.13.0/

Congrats to the team, I'm dying to switch myself but closely watching Windows support since it's unfortunately my primary work platform.