The runoff voting downside is incorrect, the “drag the voters up to yellow and watch how it makes red win” example. This is not “see how making yellow more popular makes yellow lose”. It’s actually “see how making red more popular than yellow makes red win”. The movement of the voters is not for yellow, but for red and yellow in a way that gives more voters to red.

There is no way for yellow to be the only candidate to get a boost of voters in the demo. If there were, it would only demonstrate further that yellow would still continue to win.

Runoff voting is the way.

After watching Pocahontas for the first time in many years, it shocked me that anyone could value personal wealth over coexisting. The antagonist only cares about mining out gold, looking at the hills as having potential as opposed to perceiving them as implicitly valuable as they are. Nature is worth protecting.

Oh, okay. Thank you for clarifying. So doesn’t that mean we should never have a compiler written in the same language that it compiles? Why would we ever choose to make the mistake of using the same language? Is it ever not a mistake?

Why would a Rust compiler written in C be more trustworthy than one written in Rust?

If the idea is that, in an ideal world, we would compile each layer of compilers from assembly-up-to-Rust for each build, that seems even more risky as then you have to trust each compiler instead of just one.

I’m still lost on why they’re doing it.

The idea that someone would introduce the verbiage “garbage collection” in the context of Rust is crazy to me. I hope they change that to “file cleanup” or… anything else.

So long as they’re not trying to put solar panels literally in the road but instead as coverage above the road (blocking rain, snow, sun, etc.) then that sounds great.

Oh, yeah, vim motions are wonderful. I started using them when I installed Linux on my Chromebook due to the lack of a good keyboard setup (I still don’t know where the Delete key is on that thing).

vim (or better yet vim bindings) is great. I’ll never go back.

Neovim. I tried to use it a year ago, but I felt like I was fighting it every time I just wanted to make progress on my project. VSCode doesn’t get in my way. I’m going to give it another shot in a few years.

I don’t know how to get everyone I know to really understand this. Every time I bring it up in conversation, the other person just puts their hands up and explains that they’re powerless to address it, so it’s not even worth talking about. I don’t know how to respond to the apathy.

Yeah, if it’s purely a Sqlite implementation detail to create temp files, that’s on them to own and fix. I thoroughly dislike that the files are obscured from users.

Oh, I thought that the temp files were named by the user. If that’s not the case, that these are not databases created specifically by McAfee in the temp directory, then I’m not sure what the appropriate solution should be. Obscuring the file type and how the file is used from users is still a bad practice.

I love how the solution didn’t involve changing the prefix to “mcaffee_”. Now users don’t know who to blame. Great. That’s so nice of them.

I personally think that unwrap and the question mark operator were a mistake.

Your team needs to have a coding standards meeting where you can describe the pros and cons of each approach. You guys shouldn’t be wasting time during PR reviews on the same argument. When that happens to me, it just feels like such a waste of time.

How does it handle multiple potential outcomes? Example: unformat!("a {} b {} c", "a x b b y c") Would it return Some(("x b", "y")) or Some(("x", "b y"))?

Thanks for the suggestions. I appreciate it.

Every so often rust-analyzer in VS Code doesn’t use the latest code after a cargo update and the only way I’ve found to fix it is a cargo clean. This means that I have to wait 5 minutes for the next build, painful. Just because of one project update. I would LOVE a faster build.

Extra info: the updates come from my dependencies that utilize my private repositories via a git = "[path]". The rust-analyzer is pulling from a cache or older version for some reason and I don’t know where it is or why.

I love any reduction in build times. This is great news.