calcopiritus

Just need a bit of propaganda. If half of Americans were convinces trump is a good president (the best even!), they can be convinced that invading Europe is a great idea.

Just tell them that wokeness has invaded Europe and they need being saved by the US.

Already tried that. We hoped that by buying massive amounts of Russian oil and gas they would see that peace is worth a lot more than war.

But they decided war anyways. And suddenly we had to find a replacement for all that energy.

Maybe if American "cars" were actually car sized, they would need a lot less material to be made, and require a less powerful cheaper motor to move all that metal around.

That only happens in the US because of first past the post system. In European countries new parties with significant vote share are created all the time.

In fact, in my country the opposite of what you say happened. First we had a dictatorship with a single party. Then democracy came and we had a 2 party system. No we have 4 major parties, in addition to some minor ones.

Bookmarks are even harder to clear than tabs, since they are more "long term". furthermore, they require more effort. Opening and closing a tab is 1 click each. Bookmarks take 1 click to create at least, but 2 to delete at least.

The browser history requires a lot of effort to find what you want.

Basically I use tabs because they require less effort than any other method.

The easiest solutions to the US problem are already solved in most other western countries. That's why the US is the first (and at this time, the only one) that turned fascist.

Legal guns are uniquely a US problem. Having a system that only allows 2 political parties is a uniquely US problem. Limitless (in the billions!) political donations is a uniquely US problem. Relying on the stock market for retirement is a uniquely US problem.

I'm not saying that the rest of the western countries turning fascist is impossible, but it's much harder. Most fascists are contained to their fascist political party. So until there aren't enough fascist individuals, they can be mostly ignored. Of course, once they are enough fascists, the fascist party will inevitably win, and there's nothing that can stop them at that point.

Simple.

1. I'm reading tab A
2. Tab A links to tab B
3. Open B in new tab, since I know I'm going back to tab A soon.
4. Go to tab A
5. Go to tab B again
6. I'm finished reading tab B so I close it.

Notice how I didn't close tab A. Because at that point, I was not in tab A, therefore I don't think about that tab much so I don't even think if I should close it or not. Tab A will probably stay open until I decide to clean my tabs when there are 50+ tabs on them.

Another common scenario:

1. I'm reading tab C
2. Something comes up that makes me either switch to another task or shut down the computer

From this point there are 2 paths: either I never resume the task I opened tab C for, so it stays there for a long time, or I resume the task when tab C is too far up (I use vertical tabs), so I open tab D that is the same webpage as tab C. When I finish I close tab D, but tab C remains for a long time.

I see you ignored my entire comment.

I don't know what is more explicit about expect. Unwrap is as explicit as it gets without directly calling panic!, it's only 1 abstraction level away. It's literally the same as expect, but without a string argument. It's probably top 10 functions most commonly used in rust, every rust programmer knows what unwrap does.

Any code reviewer should be able to see that unwrap and flag it as a potential issue. It's not a weird function with an obscure panic side effect. It can only do 2 things: panic or not panic, it can be implemented in a single line. 3 lines if the panic! Is on a different line to the if statement.

An unhanded error will always result on a panic (or a halt I guess). You cannot continue the execution of the program without handling an error (remember, just ignoring it is a form of handling). You either handle the error and continue execution, or you don't and stop execution.

A panic is very far from a segfault. In apparent result, it is the same. However, a panic is a controlled stopping of the program's execution. A segfault is a forced execution stop by the OS.

But the OS can only know that it has to segfault if a program accesses memory outside its control.

If the program accesses memory that it's under it's control, but is outside bounds, then the program will not stop the execution, and this is way worse.

EDIT: As you said, it's also an important difference that a panic will just stop the thread, not the entire process.

Replace uncaught exception for unhanded error.

"unwrap should not exist" is true as long as you don't want to ever use the language. If you actually want to use it, you need it. At least while developing.

Some values cannot have a default value. And some cases it's preferable to panic even if it has a default value.

unwrap is not the problem. Cloudflare's usage is.

It's really hard to do without Rc (or similar) or unsafe.