Recent submissions

Comment · 1 year ago
Do you have any plans on launching a Swift framework?
Comment · 3 years ago
Major differences are that (1) Homerow does not show search results in a command palette fashion. YMMV but I prefer the UI to be minimalist. (2) you can disable search and have it work almost exactly like Vimium.

I would also like to note that the Shortcat dev plans on adding licensing. Homerow has licensing, but there's no blocks on features. So they are both "free" in the same way.

Comment · 3 years ago
Comment · 3 years ago
Comment · 6 years ago
Haha, I wrote that on a whim. I'll come up with a better line.
Comment · 6 years ago
It actually technically could support Firefox/chrome, but I have disabled it because enabling accessibility on chrome breaks window managers.

Also vimium will always be faster than vimac due to how slow the accessibility API is.

I would recommend using both for now.

Comment · 6 years ago
Yes, you can do so!
Comment · 6 years ago
It's very much like Vimium, which is nothing like Vim, so no. I see Vimium being referred to as "vim bindings" for chrome which I never got. Maybe someone could enlighten me on this.
Comment · 6 years ago
Comment · 6 years ago
The app is written in Swift, not Electron.

Vimac had major performance issues previously when traversing the UI Element tree of Electron/Webkit apps.

Comment · 6 years ago
I'm glad you like it!

> cursor return to its old position after an action

Will do!

Comment · 6 years ago
> it taking quite a lot of CPU

Yes that is fixed.

The reason for slow performance + high cpu usage on electron/webkit apps was just the sheer amount of mach ipc calls (from the many many <div> layers) needed to be made to fetch the entire UI element tree.

This has been fixed two days ago Heres the solution for those interested: https://github.com/dexterleng/vimac/pull/190

I was also using a bunch of async queues instead of just a single NSThread which likely contributed to high cpu usage, and that has also been fixed.

> warning that I am using a screen reader.

Nope, you should get this warning, although it was a one time prompt for me. This is because Accessibility is opt-in for electron apps for performance reasons, and I have to ask for it through setting the AXManualAccessibility attribute (see https://electronjs.org/docs/tutorial/accessibility#assistive...), which I guess triggers the prompt.

Comment · 6 years ago

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton