So TIL Microsoft can't stop Teams from making itself auto-start every launch because the option to do otherwise is NotImplemented
:
How does Teams get new features implemented, then? Teams, just like PowerApp, runs on LEAN development so naturally to get anything implemented you need to put it in UserVoice/Dreamland/whatever until it gets enough traction (read: votes) to be picked up by the dev team:
https://microsoftteams.uservoice.com/forums/555103-public/suggestions/33728680-disable-startup-option
86 votes, when the top items are 10k+ votes... Yeah, it's not gonna be implemented for the foreseeable future.
I never understand why would anyone think turning features and roadmaps into a public Battle Royale is even a good idea in the first place. The distinction between a bug and a FR is unclear and entirely dependent on whoever has the final say. Application crashes on your PC! Is it a bug? What if I told you application crashing on your PC is intended behaviour, and so requesting a change would be a FR and not a bugfix? Nobody knows what are bugs and what are FRs because they're all grouped under a single term ("idea" or whatever). It also implies that the urgency of any change is proportional to only the quantity of users (who bothers to register an account to participate in the battle royale site by making their vote) desiring it, which is... absurd? By this metric blocking issues for a smaller group of people is less important than minor improvements for bigger groups of people. So you better hope you aren't those unlucky users who get stuck in the mud, because most likely, It Is Just You and nobody will save you.
Meanwhile, if some product Battle Royale-s the features to be implemented to their product, you can be assure that they don't actually have a concrete roadmap, or what their product should be. It is basically like how JS gets new features via proposals, which means the features have no consistency or cohesion, and they are highly dependent on whatever trends the community is obsessing at at any given point, except it's even worse because at least for JS proposals you need to wait for vendors to implement said features. And we all know how JS proposals suck, so battle royale mode is going to suck even more, with the dev team chasing the top ideas by implementing the most bare bone feature to count as satisfying said ideas.
And holy cow, the list already has 20k+ items? Is it trying to compete with the number of open issues on Minecraft's bug tracker? By extension, you can bet that de-duplication is mostly likely non-existent unlike typical issue trackers, which means even harder to actually measure the votes of various features.
I'm not sure what kind of development is the worse kind of development: discourse-driven development (complete chaos and lack of organization, everything automatically closed after a few days of inactivity), github issue-driven development (depends on development whim and attention-grabbing to get bugs fixed, bumps after bumps to refresh attention), or UserVoice-driven development (aka battle royales). Neither of them is productive, and as users encountering issues (I can find lots of issues and raise lots of them) all of them are very frustrating.