Not suing others for millions or billions and spreading misery. Nothing can bring those kids back.

Maybe the government could have offered education and employment guarantees to the families?

> only country

Want to list some other things only the US has?

The people who are responsible are dead.

They didn’t though. Holding a rifle manufacturer liable for a shooting makes no sense, unless applied universally.

A journalist writing a book did not cause the shooting.

This is greed and lashing out in pain. I’m sure members of the community have ruined their life in pursuit of these things.

> Your program needs one million threads that sleep for 2 seconds, read some data and then finish.

I have yet to see this problem, but yeah I agree that millions is about when there will be problems.

- school administration

- rifle manufacturer

- the shooters mother (home insurance)

- other journalists who wrote about the event

I don’t know exactly what compensation they should get, but this does not seem like a healthy or sustainable way for our society to deal with tragedy.

Surely chairman mao agrees with free speech that doesn’t harm his society and social programs

I’m making fun of the notion that blocking = slow = unresponsive.

What does run out mean?

If you’re talking about the course where you prove the runtime of an algorithm using mathematical induction techniques, well that’s more of interest to mathematicians and researchers. Learn what you can, know where to look back if needed, but it’s ok.

Wow you mean the whole program becomes unresponsive? Crazy!

To address your main point, yes, scrolling, hover, etc can continue to work. But now you genuinely have two things your program is doing at once, and these must be coordinated.

A gui framework typically handles this, with a separate thread (or separate OS process). So your thread that responds to events can block while the render/refresh continues doing its thing.

With this design the problem goes away. Instead of writing code that disables the ui, issues a callback, waits to respond, you just literally write:

If (!file.delete()) { Showerror() }

This is the kind of code you can read, and put breakpoints on.

Hang implies there is something you are not responding to.

Let me ask again. What are you imagining your main thread should be doing while it is waiting for essential data?

responding to new inputs means changing state. But your program is already in another. Two separate program execution states are best described by two separate threads.

> crash

Crash early, crash often. If invariants can’t be maintained, don’t pretend otherwise.

It works and is far more responsive than what we have today.

> Disks are certainly not quick enough to have File.Delete(...) be blocking

What if you invoke a delete and then it fails and you want the user to respond? What will the state of your UI be when that happens?

What is your program going to work on while it waits for the task? Usually nothing. You need to read some data before analyzing it, etc.

While you wait the OS can switch to other threads.

The only question here is whether you want to return that time to the operating system or to your language runtime.

> they’re just hiding the complexity

async/await feels helpful because you can write normal code again! If else, for loops, etc.

Oh wait that’s also what the UNIX operating system does. It abstracts away all this blocking and context switching so you can write normal code.

> If adding async to a function is too much

The authors point is a good one. You essentially have two languages and classes of functions. The regular version and the async version. Lots of duplication and a tendency for everything to become async.

> a skill issue.

I think you don’t understand process scheduling.