Denite.nvim ~The next generation of unite~

by Shougo (English)

slide: gist

He talked about denite.nvim, which is the successor of unite.vim. He said unite.vim was slow and unite becomes too complex to extend anymore, so he developed denite.nvim with learning from unite and uses Python along with neovim’s remote plugin feature or if_python3 for Vim.

He said Vim itself becomes slow if the plugin consumes lots of memory as one of main reason why unite.vim is slow. I somewhat doubt this and asked him the source or something. He said that Vim script is not designed for such purpose and didn’t give me a clear source for this but denite is definitely fast. If the memory consumption was really the problem, I think it’s great to make a reproduction step and report to vim-dev.

I also asked him about other performance problems about unite.vim and it was really interesting to hear.

Go、C、Pythonのためのdeoplete.nvimのソースの紹介と、Neovim専用にpure Goでvim-goをスクラッチした話

(deoplete.nvim sources for Go, C, Python and development of vim-go for Neovim from scratch using pure-Go)

by zchee (Japanese)

The slide itself is Japanese, but you may find interested in his projects.

http://go-talks.appspot.com/github.com/zchee/talks/vimconf2016.slide

I think he is highly talented software developer and I always surprised with his lots of great activity. This talk was one of the most interesting talk in vimconf2016 for me.

He talked about deoplete sources he wrote and demonstrated completion using them. It was really fast! deoplete-go is not a mere port of major go completion for Vim and supports cgo completion.

He also talked about nvim-go, which is Go development plugin for Neovim written in pure Go using neovim/go-client. He developed nvim-go from scratch to learn Vim and Golang. It’s not just a port of vim-go (e.g. supports derekparker/delve debugger) but aims to make it compatible with vim-go.

I’m interested in developing Vim plugin in Golang for Vim8.0 these days, so his talk was really interesting.

エディタの壁を越えるGoの開発ツールの文化と作成法

by tenntenn (Japanese)

He talked about the practice of Go development tools which works in across any editors and how to write such tools. As I already mentioned Go in this post several times, I also think Go developments tools are really awesome and we can develop tools for any editors including Vim by using Golang.

btw, his Gopher images are really cute!

vim-mode-plus for Atom editor

by t9md (English)

If there were vote system for the best talk in vimconf, I would give my vote for this talk. t9md’s idea is always interesting and activities and power for realizing it is really impressive. I always respect his works.

He got a deep understanding about Vim-ish way through the development of vim-mode-plus and implemented original (more!?) Vim-ish feature.

As for the keep cursor position by operator, I back-ported it for yank operator (haya14busa/vim-operator-flashy). Keep cursor position and highlight the object is really useful. But, in order to support this feature by Vim for general operators, it’s difficult because Vim doesn’t expose hook or API for this. We also needs handle special cases for “change” operator like replace(vim-operator-replace).

t9md implemented Vim feature by himself in vim-mode-plus in clean and extensible way with deep understanding of Vim and it enables him to implement interesting feature on top that. It’s really awesome!

Japanese documentation for Vim

by MURAOKA Taro (Japanese)

This talk is about translating Vim documentation in Japanese. He explained how vim-jp manages translation work and call for our contribution. You can also find translated document here http://vim-jp.org/vimdoc-ja/.

I didn’t use Japanese doc personal these days, but without translated document, I assume Vim community in Japan would be small, so I think I should contribute it in my spare time. Development of helper tools for translation maybe interesting.

僕の友達を紹介するよ

by aiya000 (Japanese)

He introduces several Vim plugins which helps development.

Best practices for building Vim plugins

by thinca (English)

slide: gist presented in Vim by his thinca/vim-showtime plugin

thinca has deep knowledge of Vim script and the practice for developing Vim plugins. If you are Vim plugin developer, you must check it out! It’s worth reading it.

I always learn a lot for developing Vim plugin from him and his plugin.

Party (w/ dinner by vimconf)

I talked with lots of vimmers but especially it was interesting that talk with t9md more about vim-mode-plus and talk with kaoriya (MURAOKA Taro) about lua translator, how to write patch which is easier to included, implementing feature in Vim itself or in Vim plugin and Vim architecture. etc…

I personally inclined to make Vim plugin, but some of them might be better to implement in Vim itself. I developed haya14busa/incsearch.vim but some of it’s feature is implemented in Vim itself these days (like moving cursor while searching)…

kaoriya said that it’s easier to ask vim-dev include new feature patches, compile option is useful to enable it optionally.

Conclusion & Next Expectation… :)

I really enjoyed communicating with lots of vimmers in Japan. There are lots of Japanese Vim plugin developer and Vim contributors (C developer).

A lot of plugin developers and Vim users from various background in Japan participates in vimconf. It’s really interesting to communicate with them but I want to hear more from Vim contributors in Japan and from Vim users outside Japan :)

At the end, please let me say thank you, vimconf staff for their hard work! (btw, PA Kuniwak is the developer of vint and manages high quality live recording.) and thank you, mixi, Inc. for providing a place.

I really enjoyed #vimconf2016! It was best vimconf ever :)