since the TO isnt alone there must be something true inside his claim?
i am .not the average joe but the update should be better.
why does the selfupdater didnt make a snapshot (without the db) before updating?
HA is the 3rd App that i am using and all did go the same route
It was nice and simple then more and more features are added until it was a huge mess that nobody could handle maybe where forked from someone (and the circle starts again)
Use (the reason why my ignition cord is involved) the nice Audio Feature.
You cant use audio on the Host that runs HA anymore unless you add a 3rd party plugin that you find after spending some time.
Why the dev team didnt fix such issues the way Linus does it - go back fix it and after the fix we can discuss if your feature will get back to the distri again?
The fact that there is a “fix” and the fact frenck closed issues about that problem because of the fix - what did this tell you?
- The “thing” that blocks alsa&pulse isnt really needed because the fix can fix it and there is nothing wrong fixing the issue by 3rd pary docker addon?
- The Fix is working (in terms of alsa&pulse is usable) but the main addon didnt run anymore?
Since i was using the fix and cant tell you its not the 2nd but the 1st case - how would you explain that fact (fiy is there - fix isnt added to the main distri - fix isnt populated)?
The lack of doku…
well if i would add something in my job without adding the doku first - i would be kicked out of the job asap.
Is it the job of the devs to update the doku or the job of someone else?
Who - other than the devs could know about how it should be used?
Is it a wise decision adding featues after features when there is something wrong with the “stable” version?