I’d go easy with the recommendation to couple components loosely. If you make things that belong together loosely coupled, you’ve created obfuscation, and added complexity to your codebase. Loose coupling makes sense, but not everywhere.
Even if that was true, how is that better than having fascism today, given than genocide will happen no matter what? You seem to imply people will have more willingness to resist if it happens tomorrow (and I doubt it). But are you really willing to take the chance on actual fascism? It really seems like you want it to happen…
You guys have a twisted sense of priorities. You’re willing to trade a maybe for a surely.
It really seems like my options are Fascist Now Party or Fascist Later Party. If the Democrats don’t listen when I vote and don’t listen when I abstain, why should I vote?
The answer is in your question. Fascism later is the better option because it buys you time to do something else. Fascism now means the game is over today. Nothing about that is difficult to understand.
You’ll have ample time (and freedom) to oppose Harris after November, but now’s not the time.
Not my experience. I’ve had the displeasure of having to use Rider at work, and it’s much slower than VSCode, if only for boot times which are a pain in the butt for large projects. You gotta pay for that bloat and feature creep somehow.
And that’s on a Xeon machine.
As for refactoring, yes, Rider has lots of options that don’t work and do half the job. So much so, that I don’t use them at all, because they’re unreliable.
The requirement for Copilot to qualify an IDE is a bit funny. First, VSCode has some support for it, and, secondly, this is super recent, so unless IDEs didn’t exist since last year, I’d say this is not core to the definition of IDE.