here in Seattle: the at-large City Council seat (district 8) between Tanya Woo and Alexis Mercedes-Rinck
Woo ran for a different city council seat a year ago, and lost. in the same election, a sitting city councilmember (Teresa Mosqueda) won an election to the King County Council, so she resigned her city council seat. to fill that vacant seat, the other newly-elected city councilmembers appointed Woo, even though she had just lost.
by the rules of the resignation and temporary appointment, the next regular election (now) elects a permanent replacement.
this leads to an unusual scenario - normally, Seattle (and all of Washington state) holds its municipal elections in odd years. the current mayor was elected in 2021, the most recent city council election was 2023. this leads predictably to much lower turnout for the municipal elections, which leads in turn to conservative business interests having an easier time buying the local elections.
Woo is aligned with the "business-friendly", conservative (by Seattle standards) councilmembers who were elected in 2023. Mercedes-Rinck is significantly more progressive.
based on the primary results and subsequent polls, Woo winning seems pretty unlikely - but the margin of Mercedes-Rinck's victory will still be interesting, because of what it says about Seattle politics in elections with high turnout. voter turnout in the 2023 elections was a dismal 36%. this year is likely to be in the ~80% range.
it's also an opportunity for something very funny to happen - Tanya Woo may set a record that will likely never be broken, becoming the first candidate in city history to lose 2 elections in consecutive 2 years, for a seat that normally gets elected every 4 years.
you read a post about how awesome C is, asking why more people don't use it and instead gravitate towards replacements.
you ctrl-F for "security" - no mention
"buffer overflow" - nope
"memory safety" - nothing
"undefined behavior" - nada
this is sort of a reverse Chesterton's Fence situation. the fence is getting replaced, and you're talking about how great the old fence was, without understanding any of the actual problems it had.
you wrote some C and found it simple? OK, great, congratulations.
go work on a C codebase that spans 100 or more engineers all contributing to it.
go write some C code that listens on a TCP socket and has to deserialize potentially-malicious data received from the public internet.
go write some C code that will be used on an aircraft and has to comply with DO-178C.
and so on. after you've done that, come back here and tell us if you still think it's "simple and effective" and "applicable everywhere".
there is a reason C has stood the test of time over many decades. but there is also a reason it is being replaced with more modern languages.