State of project

[droctothorpe]

First of all, this project is amazing. Major kudos. I see that there hasn't been an update to the source in a year. Do you intend to continue maintaining the project?

[bircheve]

Would love to know this!

[Lizzergas]

Pinging @dexterleng

[ucg8j]

+1 - it's a great FOSS project.
Sidenote: I'd be the first paying customer if I knew it had continued support.

[lougreenwood]

Would also be willing to pay @dexterleng - makes for a great companion to KindaVim

[godbout]

Would also be willing to pay @dexterleng - makes for a great companion to KindaVim

there's kindaVim's little brother that is getting born 👀️ https://twitter.com/wooshyapp

[dexterleng]

@lougreenwood @ucg8j @TheScriptan @droctothorpe @bircheve Hey everyone, I've been working on Homerow (the new Vimac), currently with huge performance improvements and workflow improvements.

You can check out the user guide + website and purchase a license if you are interested. I don't have a trial ready (working on it) but there's a 30 day moneyback, just drop me an email.

https://homerow.app
https://dexterleng.notion.site/Homerow-User-Guide-b51b701ba23f4fbbbb75692faef3d994

[yigitkonur]

Oh, this is great news! I don't mind to have whether FOSS or closed source - I will be happy to pay more for better maintained software. Thanks Dexter!

[keithgibson]

@lougreenwood @ucg8j @TheScriptan @droctothorpe @bircheve Hey everyone, I've been working on Homerow (the new Vimac), currently with huge performance improvements and workflow improvements.

You can check out the user guide + website and purchase a license if you are interested. I don't have a trial ready (working on it) but there's a 30 day moneyback, just drop me an email.

https://homerow.app https://dexterleng.notion.site/Homerow-User-Guide-b51b701ba23f4fbbbb75692faef3d994

Oh dang! I had no idea there was a new model of Vimac and that this wasn't being updated any more. Even when coming to the main page for Vimac here on Github I didn't know, as there's no reference to it there. Wasn't until I scrolled through the issues that I found this thread. There's probably a ton of people like me and the others in this thread who are Vimac users (or potential, interested users) who are unaware of Homerow.

I highly recommend updating the main page of this project with what you said here and your link to Homerow. And even pushing an update for Vimac that just shows a message saying the same, that way you capture all of the users who try to update Vimac. At the moment if someone tries to update and they get that message saying they're up to date they're not likely to even navigate to this Git page, let alone go through all the steps to find this thread that I and the few others here did.

Looking forward to seeing all that's new with Homerow! @dexterleng

[Bellavene]

Too sad that Homerow & Whooshy are bugging out when amethyst and chromium based web browser are launched together. For me even vimac itself is perfect, except that I would be glad to have the possibility to change the yellow color on the badges.

[godbout]

@Bellavene care to describe more what's the issue you're seeing with Wooshy? you can open a GH issue here: https://github.com/godbout/Wooshy.docs/issues
thanks.

[Bellavene]

Nothing special to describe, I am surprised that you don't know already.

When you use yabai or amethyst alongside with a chromium browser and one of those two apps, then the auto tiling is broken. Browsers windows will magically get weird animations during tiling and the window will get not in the right place. It starts only when you grant whooshy or homerow permissions to work.

P.S.
Also, as I understand the effort you put into the project, I am very skeptical on the subscription model you offer. And personally believe that for such projects it is better to get most amount of users in long term with a possibility to get a tip, rather than adding a subscription. I am allergic to them, don't use any, nor from big tech, nor from small businesses.

[dexterleng]

@Bellavene this stems from Vimac/old Homerow/Wooshy/Shortcat (not sure which exactly) setting the AXEnhancedUserInterface attribute to enable accessibility on Chromium apps.

The new Homerow doesn't have this issue. You'll close the offending apps, and force quit and relaunch the Chromium browser

https://homerow.app

[dexterleng]

And oh yeah, I've rewritten Homerow from scratch recently 🚀 😎

[godbout]

Nothing special to describe, I am surprised that you don't know already.

huh? i'm not a user of amethyst. and i'm not (yet) omniscient. i hold an App Catalog, but if there's issues with some apps, users can (and do) report easily through the kV/Ws/Sl, and i investigate and come up with a solution, or at least an explanation. that's the proper and most efficient way to do it. whining in a comment and answering passive-aggressively when someone asks you to describe the issue is a waste of time for everyone.

When you use yabai or amethyst alongside with a chromium browser and one of those two apps, then the auto tiling is broken. Browsers windows will magically get weird animations during tiling and the window will get not in the right place. It starts only when you grant whooshy or homerow permissions to work.

not sure about Homerow, but Wooshy doesn't blast apps blindly. there's an App Catalog (built for kV first, because each app has to be independently investigated) that tells Wooshy when and what to blast which app with which special AX Attribute. some are known to break their animation if you blast them with the AXManual shit, most probably due to a bug in macOS that has been reported for 10 years and that Apple doesn't care about (by now i think i've reported about 200 issues regarding the AX). so again, not sure how Homerow handles it. Wooshy avoids the AX Attributes that break those stuff.

I am very skeptical on the subscription model you offer.

lol wth is this post 😂️ are you a troll? 🤔️ skeptical about what??? are you the creator? skeptical about getting a huge number of users??? about making money??? why do you even care about this, you're not the one building it. fyi, i don't care about the money or the number of users. i care about building great, meaningful products for myself, and having a blast doing that. kV was open-source for a while. i made it clear i wouldn't be doing open-source support. people could compile the app themselves, or get a license. result? 100 messages a day from people who had no idea how to compile, didn't want to learn, and even though i would answer all of them and giving them links to alternatives, 95% of the answers were basically they prefer kV because it's better (but they didn't want to pay). do i want to deal with those cheapfuck users? no thank you. i have 100 monthly users currently on kV, most of them are happy. several of them told me they'd pay 20US a month, they just don't want kV to disappear. the few of them who send feedback are always thoughtful, rational, and a lots of their feedback have been digested and implemented. those are the users i want. not the ones whining over 3US a month. if someone doesn't see the worth in my products, that's totally fine. i list alternatives at the end of each README, like for example for kV, and for Wooshy. as far as i'm concerned, my time is very valuable. i wouldn't spend time and energy writing a bitching comment. my time and energy are more worth than this. i would just pay if the product makes my life better 😂️ but that's maybe just coz i'm older.

And personally believe that for such projects it is better to get most amount of users in long term with a possibility to get a tip, rather than adding a subscription.

well, then build one, and do that. not sure if you're a user, or a creator also. and creating a standalone app that just deals with itself is one thing. like the apps you can find on the App Store. stuff like kV and Wooshy deal first with the macOS AX API that is old and clunky, but more importantly it deals with other apps. you have no control over other apps. they may or may not respect the macOS AX. they even change their support between releases. like Telegram was working fine until a few weeks ago, when they make changes that break both Text and Non Text Elements. which means having to research, investigate, find the issue, and contact the developers. etc. this happens constantly. i'm not even trying to defend myself here. you don't need to know anything about this. i'm answering because you're asking the question, and it selfishly helps me to dump my thoughts down and crystalize them. but ultimately ALL YOU SHOULD CARE AS A USER is whether an app saves your day, saves you time and energy, makes you smile, etc. not the amount of work the dev put into it, if it's hard etc. etc. if you're that type of user, then i clearly don't want you. no time for drama and bad philosophical bullshit 😂️

I am allergic to them, don't use any, nor from big tech, nor from small businesses.

yeah well ok. that's on you. don't use or buy them. find alternatives. again, i list all of the good ones in my projects, and i specify if they're free or not, open source, their licenses, etc. i'm doing the work for you already.

hopefully that gives you an idea of where i'm coming from with my work. hopefully you're not offended, as i'm not. but if you feel it's a bit harsh and wanna trash me and my apps around, please do so. should be really fun and let's see where this could go 😂️