[Help needed] TWiN’s future

This page summarizes the projects mentioned and recommended in the original post on /r/neovim

Our great sponsors
  • WorkOS - The modern identity platform for B2B SaaS
  • InfluxDB - Power Real-Time Data Analytics at Scale
  • SaaSHub - Software Alternatives and Reviews
  • this-week-in-neovim.org

    this-week-in-neovim.org official webapp repository

  • Either wait for Monday 9:00 AM (or 10:00, I don’t even recall; I’ll check that later), or if it’s past due (which can happen depending on my spare-time activities / work), **directly connect to the machine hosting this-week-in-neovim.org and git pull --rebase to get the updates.

  • this-week-in-neovim-contents

    Contents of weekly news delivered by this-week-in-neovim.org.

  • Moving to the actual action points: I think as a starter we could go with a couple of people requesting write access to phaazon/this-week-in-neovim-contents. The way I’ve been working is pretty simple:

  • WorkOS

    The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.

    WorkOS logo
  • helix

    A post-modern modal text editor.

  • A lot. A fucking lot. Helix was the bridge, and I still am wandering around Helix (I contributed with a PR to add some Kakoune-like normal edits). I still want to write a blog article about my experience but for short: I really loved discovering Helix, and using it. Realizing that, yes, I was right thinking that the direction of Neovim is wrong for me (not absolute wrong; wrong for a guy like me enjoying tools with minimal scopes, easy to think about, and that compose well; via POSIX, UNIX, etc.). And then, Kakoune is just the « take that composision idea, add even more UNIX on it, and add it an orthogonal design. » I read mawww’s great design doc about how Kakoune works and stumbled on the realization that that was the first time I read a design doc I agree on every point with. I really, really advise people to read that document. It’s short, well written, and full of good principles and ideas.

  • kakoune

    mawww's experiment for a better code editor

  • A lot. A fucking lot. Helix was the bridge, and I still am wandering around Helix (I contributed with a PR to add some Kakoune-like normal edits). I still want to write a blog article about my experience but for short: I really loved discovering Helix, and using it. Realizing that, yes, I was right thinking that the direction of Neovim is wrong for me (not absolute wrong; wrong for a guy like me enjoying tools with minimal scopes, easy to think about, and that compose well; via POSIX, UNIX, etc.). And then, Kakoune is just the « take that composision idea, add even more UNIX on it, and add it an orthogonal design. » I read mawww’s great design doc about how Kakoune works and stumbled on the realization that that was the first time I read a design doc I agree on every point with. I really, really advise people to read that document. It’s short, well written, and full of good principles and ideas.

NOTE: The number of mentions on this list indicates mentions on common posts plus user suggested alternatives. Hence, a higher number means a more popular project.

Suggest a related project

Related posts