3 ms·
That is very close indeed. If a mobile device could augment its CPU capacity when docked, that would indeed be close to the model I seek assuming you always ha
by bhauer 13y ago
That is very close indeed. If a mobile device could augment its CPU capacity when docked, that would indeed be close to the model I seek assuming you always have your device with you (and you probably do). It may ultimately be the way things go, but if my say mattered, I'd steer in a slightly different direction.
I would prefer that the computing device on my network be a hard-wired, always-on, high-bandwidth, high-compute, high-storage device (a workstation in our contemporary lingo). I want my personal applications to act as my agent when I am not present, possibly doing non-trivial computation and serving on my behalf. I want my data to be shared and federated with friends/family/colleagues on my terms, from my network or a network of trusted peers.
I find it a little awkward to attempt to shoehorn all of that into a mobile device when I'd be just as happy--more happy in fact--for the compute power to be hard-wired and the mobile device to be just an input/output terminal to that compute power.
As a final matter, I'd feel a little more confident with the physical security of my compute engine and data if it were in my house rather than on my person.
But yes, kudos to Ubuntu for concertedly attacking our present-day malaise of multiple first-class devices!
- pedalpete 13y agoYour use case continues to intrigue me. Are you suggesting that a cloud solution where you control who has access to your data is not an option for you? A cloud that could run your 'agents'? As we go deeper and deeper into this paradigm, I'm realising how little we need more CPU. Even as a developer, I could be writing my code locally, but running it on a larger database and leveraging CPU which is not local. For some reason, I still want CPU.