Total overkill. If the screen loading is slower than a frame because of... - I/O like file access or networks, you can punt to an async framework like Rust's T

Total overkill. If the screen loading is slower than a frame because of... - I/O like file access or networks, you can punt to an async framework like Rust's Tokio - CPU number crunching like cracking a password, you can punt to a worker thread (like Tokio's `spawn_blocking`) The kernel scheduler is smart enough to give time slices to the UI thread even if the password-cracking thread is trying to eat as much CPU as possible, or, God forbid, the network thread is _sleeping_ until a packet arrives. (Networking is a waste of a thread. Most requests and responses are small enough that the CPU could process them on the UI thread, it's just that sleeping the whole thread until the message shows up is goofy) It's not a lack of processors, it's the fact that good multi-threading and UI totally changes the architecture of a program, and most of us aren't trained for it or incentivized to implement it.