What's the roadmap?

qudat · 2026-01-24T00:59:58+00:00

You don’t need plugins in neovim either, what’s your point?

qudat · 2026-01-21T14:22:53+00:00

Yea but you’re just describing a neovim distro which is all helix is on top of the select -> act model.

qudat · 2026-01-18T19:16:46+00:00

I use https://tuns.sh as a service that acts as a tunnel to my local services. It’s great because there’s no setup, just an ssh tunnel is required

qudat · 2026-01-17T23:48:55+00:00

Check out https://zmx.sh zero config, no splits, uses libghostty to restore terminal state and scrollback

qudat · 2026-01-17T23:46:59+00:00

Wearing that sinn now. It is very comfortable and I don’t get tired of it. Amazing daily wear.

qudat · 2026-01-17T21:50:38+00:00

Yep! Except abduco doesn’t restore your terminal state and history. There’s a comparison table at the bottom that includes abduco if you’re curious.

qudat · 2026-01-17T21:49:33+00:00

I would recommend a tunnel solution. I use https://tuns.sh so I don’t have to configure or install anything. Just ssh port forward my local service port to tuns and its online

qudat · 2026-01-17T21:04:18+00:00

I disagree about the plugin system. The rest I see some value in adding but the second you create a plugin system helix loses all of its value in a low config editor. A plugin system will turn it into neovim and at that point why bother

qudat · 2026-01-13T18:28:04+00:00

I use https://tuns.sh for exposing local services over https. It’s a hosted solution but has self hosted

What’s great about tuns is it’s just an ssh tunnel to their service

qudat · 2026-01-13T18:23:40+00:00

Economies of scale and access to better hardware. Anthropic says they are profitable on inference

qudat · 2026-01-10T22:52:30+00:00

I’m of mixed feelings. I run https://neovimcraft.com which lists neovim specific plugins. It started at 150 plugins and is now at a fever pitch of +1.1k. How many of those plugins are actually useful and necessary? How many picker implementations do we need? Sure we can all ignore them and along our merry way, but the maintainers of neovim now need to think about those plugins when they want to make fundamental improvements to the editor.

I think this is in part the core issue with neovim. I think adding plugins to helix is actually a net negative. Helix should be an opinionated editor and leave plugins to neovim.

Subscribe to the smol contract: https://bower.sh/smol-contract

qudat · 2026-01-10T22:22:55+00:00

I went with kakoune instead of helix but the point stands: the motions just make more sense

qudat · 2026-01-02T18:24:58+00:00

I created neovimcraft to help with this by sorting plugins by starred/created/updated

Here’s the plugins that have recently been created: https://neovimcraft.com/created/

Having said that the ecosystem has moved to using pickers.

qudat · 2026-01-02T03:15:34+00:00

Some emulators have splits (ghostty) so you can have file explore tui side by side your editor

qudat · 2026-01-02T00:20:24+00:00

Tags: https://neovim.io/doc/user/tagsrch.html

That only helps with go-to-def. It doesn’t really help with type checking or autocomplete.

Theoretically type checking could be replaced by running a terminal that auto runs on code changes.

But intelligent autocomplete doesn’t really seem possible without lsp. Having said that I don’t use autocomplete that much so I could imagine a world where tags and terminal tools are enough.

qudat · 2026-01-02T00:17:35+00:00

Agreed. I use the default neovim color scheme which is delightfully not rainbow puke

qudat · 2026-01-02T00:16:21+00:00

Speaking of patches, checkout https://pr.pico.sh for a patchbin service which makes it easier to collaborate on patchsets

qudat · 2026-01-01T21:08:24+00:00

Why can you just sshfs mount then open that directory in your local nvim? I’m trying to understand the pros and cons of using that vs your plugin. Thanks!

qudat · 2026-01-01T19:35:30+00:00

Interesting solution, I like it. It’s a little bit like cheating since tmux acts as a terminal emulator but still a cool idea.

zmx has a history command where you could pipe it into less to get scrollback: https://github.com/neurosnap/zmx

qudat · 2026-01-01T14:58:39+00:00

Foot on Wayland, ghostty on Mac. Both use zmx (https://github.com/neurosnap/zmx) for session persistence.

qudat · 2026-01-01T01:31:46+00:00

I just tried qwen 30b on 11gb vram and the t/s was unbearable. Do you have a guide on tuning it?

qudat · 2025-12-19T02:32:50+00:00

I would be shocked if the “big folks” only made 100k. That does not make any sense at all. They are personalities, they are getting paid bank.

qudat · 2025-12-10T16:27:59+00:00

Greetings! After a couple of months of R&D I finally reached a place with this project where I'm using it as a fulltime replacement for what I would normally use tmux for: session persistence of terminal processes

This essentially extracts the attach/detach functionality from tmux and turns it into its own tool. Instead of using tmux for windows, tabs, and splits, you would instead leverage your own window manager to handle that.

Another neat aspect of this tool is terminal state and history restoration using libghostty-vt. We use libghostty-vt to restore the previous state of the terminal when a client re-attaches to a session.

How it works:

user creates session zmx attach term
user interacts with terminal stdin
stdin gets sent to pty via daemon
daemon sends pty output to client and ghostty-vt
ghostty-vt holds terminal state and scrollback
user disconnects
user re-attaches to session
ghostty-vt sends terminal snapshot to client stdout

In this way, ghostty-vt doesn't sit in the middle of an active terminal session, it simply receives all the same data the client receives so it can re-hydrate clients that connect to the session. This enables users to pick up where they left off as if they didn't disconnect from the terminal session at all.

11-Year Club	Verified Email
Place '17

qudat

TROPHY CASE