4 ms·
Hmm. That's an interesting idea. How would the phone and the PC work together, though? I could see it work if they were all the same architecture. Then you're j
by lj3 10y ago
Hmm. That's an interesting idea. How would the phone and the PC work together, though? I could see it work if they were all the same architecture. Then you're just adding more ram and cores.
Actually, the ram could be an issue. For example, say you're running a video editing program that's using 15gb of ram and you want to undock. You'd need some way of storing the state of the program and the ram its using when it's not docked. Either that or you'd be forced to shut it down completely.
- protomyth 10y agoStorage was a solved issue with the Newton Soups in the 90's, but other systems won. Memory could work the same way. Run the programs that required the high ram on the machine I docked to (using local dock storage replicating what I need from my phone) and when I unplug save the state. Perhaps back it up to network in that state in case I plug into a different dock next time.
- Jtsummers 10y agoThey wouldn't need to be the same architecture, but use a common means of communicating for coordinating tasks. There's some precedent in the design of the Transputer plus daughterboards. Borrowing from the latter to handle the heterogenous nature of phone/PC pairings. Making it hot-swappable would, of course, be a challenge. Using physical mechanisms to hold the device means that boards/phones/whatevers could be ejected safely only once various conditions (state saving, rerouting of data, etc.) were met.