

you misunderstand, I think. The number of people who voted for 47 is a product of the current voting system. changing the system will do a few things:
some people who voted for 47 may have still selected them as their first choice, but in a different system with ranked choices, one of their second or third choices may have been elected instead, if that candidate had more support overall from a greater majority of the voters (depending on the system uses to select the winner) but basically: better to have a large majority’s agreed second choice than a tiny majority’s first choice
secondly, some people who voted for 47 may have chosen someone else as their first choice if they did not feel it was the only way to make sure their least favorite candidate wouldn’t be elected - a ranked system removes the “spoiler” effect.
so if you see that people who voted the way they did, did so because of the FTTP system AND importantly how the FTTP system can be manipulated with certain types of propaganda, meticulously targeted, to elect an extreme candidate, then it’s not a matter of first “changing their minds,” and more a matter of having a system that elects the representative that most represents most of the people. that is an effective tool against extremism.


After being a vanilla vi then vim user for a long time before switching to neovim, I find folke’s which-key plugin to be very helpful. If i begin a key shortcut combination (or press my leader key), it shows me all the keys I can press next, and again after each additional step of a multi key sequence, and what each key sequence does. it works for mappings Ive added (usually basically the defaults for a new plugin) but also the standard built-in preset keymappings (see the ‘built-in’ plugins for which-key) for things like window mamagement and motions, using/viewing the registers (what did I just yank?), even spelling corrections, which helps you learn and build muscle memory. Often I dont use a specific mapping for a while and this helps me find it, especially when I group mappings by plugin, and/or prefix all mappings for a particular plugin or task with an additional prefix letter, so they all appear as options when I get as far as rembering “all my debugging mappings start with my leader key, followed by d.” By grouping tasks and plugins that way, I can press my leader key and see a list of where to go next, almost like browsing a menu hirearchy. “i dont remember which button to press after leader and d to toggle a breakpoint, but I know that’s where I’ll find it”