• 3 Posts
  • 72 Comments
Joined 1 year ago
cake
Cake day: July 18th, 2023

help-circle

  • I wouldn’t call it a bug, just that a naive ranked ballot naturally favours the centrist voices. I don’t even mean this in an extreme way: in Canada we basically have three centrist, neoliberal parties running parliament, and this would mean that the Liberals just win a majority almost every time. NDP voters generally won’t vote Conservative, Conservative voters won’t vote NDP.

    This can turn into a bug because it ends up pushing other voices out: if the popular vote suggests equal support between left, right, and center candidates, you would typically hope the make-up of the government reflects that, but more likely it would look like a center majority. There are ways to mitigate this (large number of parties, electing multiple candidates on a ballot, proportional components of the vote, etc) but ranked choice on its own tends to be a centralizing force, not a way to get a more representative democracy.

    Again, not a bug, and I definitely wouldn’t call it worse than FPTP, just making it clear that it has its own biases that are worth taking into account.



  • Honestly? Bash. I tried a bunch a few years back and eventually settled back on bash.

    Fish was really nice in a lot of ways, but the incompatibilities with normal POSIX workflows threw me off regularly. The tradeoff ended up with me moving off of it.

    I liked the extensibility of zsh, except that I found it would get slow with only a few bits from ohmyzsh installed. My terminal did cool things but too slowly for me to find it acceptable.

    Dash was the opposite, too feature light for me to be able to use efficiently. It didn’t even have tab completion. I suffered that week.

    Bash sits in a middle ground of usability, performance, and extensibility that just works for me. It has enough features to work well out of the box, I can add enough in my bashrc to ease some workflows for myself, and it’s basically instantaneous when I open a terminal or run simple commands.








  • If the bad guy hears rumours about someone asking the question, does anything change?

    When a clock fills in these contexts that should indicate that something needs to happen, and that something likely requires PC response. So if it isn’t going to significantly impact the PCs until the third clock, it may as well be one big clock with stuff happening in the background as it fills. But if each clock has an impact and the PCs can do something to impact future clocks, stacking makes sense.

    Regarding handling the consequence: it definitely depends. I’ll sometimes use a clock if they’re trying to overcome some major obstacle, so filling it means that they have less to deal with and that’s probably going to be an RP exercise. But most of the time it’s going to result in a change in position, or a need to resist something, or even a material change in their crew’s territory that requires some response. In the example above, especially for such a large clock, I’d probably have the consequence be something like the bad guys invading their territory targeting the PC asking questions, which requires more than a mere change in position to resolve. That could involve a full-on heist to thwart.