Your rather ill-conceived notion that users merely "follow" code is so reductionist. In reality, users choose which software they want to run, demonstrating their power of choice. If a significant portion of users decides not to follow a certain update, the network will fork, as history has evidenced.
And as for your dramatic allegation that dissenting opinions are "attacked as an enemy," wake up! Open source means open discussions. Just because someone's proposal isnt adopted doesnt mean they're branded enemies. It means their proposal wasnt good enough or didn't align with the project's ethos. Look forward, adapt, evolve, and lets be grateful for the learning opportunities that come from challenges rather than wallowing in misguided cynicism
you might want to check actual events of bitcoin history 2015-2023 and not just repeat a philosophy of 2009
we are no longer in the same network landscape or approach to updates as 2009-2014
users do not update their software and then a new rule activates when the network is node majority ready.
check out the 2015-2023 philosophy about "backward compatibility" but read it with scrutiny about how it causes user nodes to not be part of the network vote.
it will enlighten you
then check out how core in november 2016-june 2017 did not even get 45% accomplishment to activate their feature, then suddenly with the proposal of the mandatory activation suddenly core got an UNNATURAL 100% activation by august
look at the REKT campaigns of 2015-2023 where anything that was different to cores roadmap plans were treated as 'control attempts' and were made into pushing for those branks to 'fork off into an altcoin or else'
even the delusional doomad keeps saying 'anyone can fork the network and create their own altcoin and see who follows them' where he keeps shouting the only path for non-core nodes to make changes is via making an altcoin and seeing if they can populate another network..
so try to read actual code of actual activation methods, and how activations since 2015 have not needed the mass of user nodes to be network secure ready to verify a new feature before such feature activates.. and then realise the security risk of such method