Skip to content
0:00 / 0:00

#neovim#vim#decoupledui

We can have nice things

vim-jp

3.2K subscribers • 3 videos on Hallway

YouTube
  • Recommended by 2 people: 2 in engineering communities.
  • Presented by Justin M. Keyes, Neovim lead maintainer
  • Linked in the descriptionSlides on slides.vimconf.org
  • An opinion. It argues one side of a question engineers disagree on.

Intermediate. Assumes working knowledge.

25K views6 years ago2 recommendations

Software designTools and practiceVim, Emacs and editorsSoftware architecture

Justin M. Keyes discusses the philosophy, design, and decoupled UI architecture of Neovim at VimConf 2019.

Speaker: Justin M. Keyes Slide: slides.vimconf.org/2019/justin.pdf Official Site: vimconf.org/2019/

Why it's here

2 people recommend this

What people say. Recommended to Emacs and Vim developers for its insightful discussion on text editor design and decoupled UIs.

u/dericbytesin r/emacs • Recommends

Emacs Decoupled UI vs Neovims - Talk by Neovims Lead Maintainer Thought some emacs devs might find this interesting. Or it might provoke some interesting discussion that would enlighten us mere motrals that can't contribute to the emacs core development. "We can have nice things too" by Justin M. Keyes Relevant section starts at time 40:00 [video

u/Desmesurain r/emacs • Recommends

"We can have nice things" - Neovim talk I want to share a talk I've just found that I think could interest a lot of you here. It's done by one of the developers of Neovim. [video It doesn't talk only about Neovim. It also talks about the philosophy and design behind text editors and UI in general. Some key points I found really compelling about it: * Evolutionary/genetic development. And how this relates to "Browsers vs. OSs", and how OSs have "lost" the battle. * Embeddable, not having to choose a text editor or an IDE, having both (or many!). * Legacy code. * Invoking computers, not functions. * Moving to Github (instead of mailing lists) made the project advance. * Decoupled UI (and…