So then it isn’t actually that feasible then, otherwise you’d do more than just whine about it on the Internet. Especially when there are valid reasons to not support that method.
it isn’t actually that feasible then, otherwise you’d do more than just whine about it on the Internet
So let me get your logic straight: you’re saying that it isn’t feasible because if it were feasible then a person who could do it would necessarily do it? LOL that makes no sense.
Well, yeah. Especially when you’ve already been given reasons why it isn’t. But clearly you know better than the devs or people familiar with the product.
Why do you think that because a person could do something they necessarily will?
I don’t, but in this case, we know it’s not because they got rid of that option. Why? Because the task is infeasible to support. Kinda like you’ve been arguing against this entire time in the face of multiple reasons why people aren’t doing it.
You’re far from the first person to want this, and the devs no longer offer it as a supported method for a reason after all. No one is saying it is impossible, just not something that’s feasible to create and support. This really should not be this hard of a concept to understand.
Then go do it.
I’m not a Debian Developer and won’t become one: http://settrans.net/~rah/why-not-debian.html
Also, I’m not a Home Assistant user so I’ve no interest in contributing.
Then do if for your distribution then. It’s clearly not that difficult, you’ve all but explicitly stated as much.
I use Debian.
I have not said that, or anything like it.
Perhaps you missed the fact that I’m not a Home Assistant user and have no interest in contributing?
So then it isn’t actually that feasible then, otherwise you’d do more than just whine about it on the Internet. Especially when there are valid reasons to not support that method.
So let me get your logic straight: you’re saying that it isn’t feasible because if it were feasible then a person who could do it would necessarily do it? LOL that makes no sense.
Well, yeah. Especially when you’ve already been given reasons why it isn’t. But clearly you know better than the devs or people familiar with the product.
Why do you think that because a person could do something they necessarily will?
I don’t, but in this case, we know it’s not because they got rid of that option. Why? Because the task is infeasible to support. Kinda like you’ve been arguing against this entire time in the face of multiple reasons why people aren’t doing it.
You’re far from the first person to want this, and the devs no longer offer it as a supported method for a reason after all. No one is saying it is impossible, just not something that’s feasible to create and support. This really should not be this hard of a concept to understand.