[In-app feedback] #3900
Comments
|
Sorry, this would increase complexity too much for most users, while enabling new workflows for a few users |
|
@lwouis please reconsider this. This is the only tab switcher I've ever used that moves backwards when you only press shift. I need to be able to both alt+shift+tab and alt+shift+` and that's currently impossible. Whenever I try a shortcut like that, it moves backwards twice for some reason which causes the wrong thing to happen and it's so annoying |
Oh BoyThere have been around 20 issues about this in the past:
Yet you still say Not Enough People Want Itit should be clear by now that a lot of people who have used the tab switcher on another operating system and then switched to this one have been surprised by:
there have been around 20 issues reported about it. and that's not including the unknown amount of people who found this annoying but didn't think to open an issue about it. and that's not including the The pull request that literally implements this for youwhich you turned down because basically "Too Niche, not enough people want it, we don't have telemetry ..." you don't have telemetry? AltTab has a GitHub repository where approximately 0.5% of all reported issues are about this.is that not enough telemetry for you? around 20 different people have independently reported this to you and you still say it's too niche and too complicated to support |
|
Hi, 20 people is very little. There are probably between 100K and 300K users, based on the download stats. So 0.0001% of users. 20 issues out of 3600 is 0.006% of issues. It may feel a certain way to you. It doesn't mean everyone feels the same way. Some people use the new shortcuts and thanked us because it helped with their hand pain. It's more ergonomic. I take feedback seriously. I understand Please always keep in mind that:
Thank you |
I don't think so? my mental math was that 20 out of 4000 is 1 out of 200, or in other words 0.5%. not 0.006%... 20/3600 may be approximately equal to 0.006 but then you need to multiply that by 100 to get 0.6%.
The entire basis of my argument is that many people think this way, not just me, so please don't already make it personal.
I only mind that you keep saying you don't add it because it's too niche and not many people want it, when that's not the case. If you just don't like/want to do it for personal reasons, or if the reason you won't do it is because you're tired of being asked (lmao @ the label you added) then it would probably be more transparent to say that instead of painting it like the people who are asking for it are unreasonable. I also don't mean to be rude, sorry if it felt that way, I was just shocked by how many past requests I found for this, it's extremely clear that a lot of people want this. just my 2 cents |
|
You're right about the numbers. They are indeed: 1 out of 10000 users Are these numbers indicating a pressing mater to you? To me they seem pretty low. I've read and managed all tickets on this repo. This gives me a sense of scale and urgency. This issue is about a few users who want to keep their habits instead of trying something new. I'm the first one to be unhappy when the big software companies change my habits, so i empathize with the frustration. The reason i'm not changing things is because i believe using only shift to go backwards is a more ergonomic shortcut. I believe it works well for most AltTab users that don't come here to complain since it works well for them. I'm not doing it for me. I'm not doing it because i'm frustrated with feedback. I've looked at it carefully, and have made this decision that i think is best. I'm the main maintainer of this project. I'm steering it, putting in the hours. If you think my leadership is not correct, you are free to fork this project and steer it in another direction. If you put hundreds then thousands of hours into it, people may refer to your fork as the main one. If you're not willing to do that, then please respect my work and understand that i may not please 100% of people. It's impossible to please 200K people. 20 came here and opened a ticket. There are another 3600 tickets. That's a lot of people asking different things, coming in with contradictory asks. I'm steering the project. You can steer your fork. It's all there for anyone to work on. This is free and open-source software. Thank you |
|
Sorry, I don't know what is going on here, but I think you're interpreting my comments as more combative than how they were intended. I never said I don't respect your project, and I also never said this was in any way pressing or urgent. I only was questioning why you so strongly resist it, even when somebody opened a pull request that did all the work for you. It's not that you're not doing some thing I want, it's that you're actively working towards preventing this thing I want from making it into your software, and you're doing it for a reason that doesn't make much sense, or at least you use that kind of reasoning to explain it. I get that it's your software, and you have final say in what happens to it, I have no problem with that. When you say you won't accept the feature because not enough people want it though, and it's clear that enough people want it that there were 20 issues and even a pull request about it, then I can't help but be a little insulted, especially when you say stuff like:
So is AltTab itself... Yes, it's your project, and you can do whatever you want with it, but it feels not honest for you to blame it on the number of users, instead of just saying it doesn't align with the direction you want to take, or something like that. Some of that's come out before (in the PR comments specifically, you also say that you're afraid the setting will confuse new users, and that you're trying to drastically reduce the number of settings) but it seems like your main argument in issues like these is now that it's niche and almost nobody wants it. I feel like if this is a philosophical thing, if you don't want to implement it just because it doesn't fit with your personal vision of the software, then that should be your main argument. At the very least, it should probably be mentioned each time this comes up, instead of left only in years old pull requests, in favor of the "niche" argument. I hope that makes sense. I guess this is basically "if you're not going to do this because you just don't want to, could you please just say that directly instead of trying to claim that this is somehow objectively niche when it's not". |
Here are the numbers again: 1 out of 10000 users If this is not niche usage, what is your threshold for niche usage? Please share your numbers. I'd like to know your personal threshold numbers. For me, less than 1% is objectively niche. We are not seeing things the same, so I'd like to learn how you approach these numbers to decide what is mainstream and what is niche. Thank you |
This issue was opened by a bot after a user submitted feedback through the in-app form.
From: [email protected]
Message:
The text was updated successfully, but these errors were encountered: