|
|
|
|
|
by wredue
1010 days ago
|
|
Yeah. In a normal work day on a brand new i7 w/ 32 gigs of ram, I would say I get frustrated by the computer not doing what I tell it to in a decent timeframe more than a few times a day. Now we’re saying “hey, let’s take a slower device with even slower pieces of shit applications on a foundation that worse at multi-window multitasking and make it what people use” I’d probably blow my own brains out if this actually happened. The technology is there for this to be usable. The dogshit development practice of “well, the hardware will catch up to my dogshit eventually” is meaning that “the technology isn’t there”. Edit: Case in point. This very laptop just spent 15 MINUTES cold boot till it allowed me to join my Teams meeting. Granted the phone will stay on, so wouldn’t run in to cold boot issues. But also, I don’t want my work phone on all the time. That’s just letting work invade my personal time. |
|
But it'd always have the unavoidable downside of meaning that your phone was effectively tethered (even if just wirelessly) to your desktop. And at that point, why not just have a decent CPU in the desktop?
I guess it'd work well in a world where you constantly traveled between workstations and also couldn't bring your laptop. I've never lived in that world.