Recent submissions

Comment · 1 year ago
Humor must be! Boring otherwise!
Comment · 1 year ago
I'm not planning to work on plugins on the near future. But yes, I have some ideas. mainly: golang compliled plugins or lua. I'm leaning more to go complied plugins.
Comment · 1 year ago
Hey fellow vim enthusiast! I wish you all the best with vimgolf.ai
Comment · 1 year ago
That was most "dumb" and simple yet fast approach to get it done. Other ways of implementing it are more time consuming. I've saved a lot of time on it. Like "one day" and it was done.
Comment · 1 year ago
Hey wyclif! I'll take your idea! amazing! really really like it! wig let it be!
Comment · 1 year ago
Hey hit8run, appreciate your feedback. I was also running Helix for a couple of months. great editor. performance is phenomenal.
Comment · 1 year ago
it is not more effective than vim nor it will ever be. it "just" a text editor with no intention to compete with vim or any other great editor.
Comment · 1 year ago
Ctrl-c will spawn process defined in header and will send all subsequent commands to it. E.g; spawn psql, run sql queries from editor.

For now I have no plans for plugins. Need to finish "base" first and good. And yes, intention is to keep it minimal.

Comment · 1 year ago
Hey Paddy. Vim uses horrible vimscrip, neovim - cool lua. I have two idea for plugins: - 1. Rich events system on backend side. e.g. write golang code for plugins, recomplire editor. done. pros: good performance, autocomplete for plugins out-of-the-box. golang. cons: feedback loop is lonfer. recomplier, restart, repeat. - 2. Use lua. pros: fast development cycle. cons: harder to implement. two languages, communication overhead.

I also use Emacs, btw.

Comment · 1 year ago
I appreciate your feedback!

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton