Your thoughts?
Desktops will split into:
- Servers: LAMP;
- Beowulf Clusters: EG: MicroWulf;
- Network Storage Appliances: EG: The BackBlaze Storage Pod;
- Feature phones;
- Tablets: 7 inch, 10 inch, and 11 inch screen;
- Laptops: 15 inch, 17 inch, and 21 inch screen;
- Smart Devices: Roku, Internet capable TV boxes, Internet capable fridge, etc;
- Home-Bots: Security devices, Cleaning devices;
- Gaming boxes: PS3, xBox, Wii, etc;
My guess is that organizations will give employees a locked down tablet that can only access the programs, databases, and Internet sites that company allows. (NSA Android can be customized to this with current Android devices.) For example:
- A wait-person will pick up a tablet when they report to work, and log into the company cloud. That tablet will be used for order taking,telling the wait-person to pick up the food, telling the cooks what to fix, and paying your bill;
- A phone person (Sales, customer service, etc) will report to work, pick up a tablet, and put on the company phone headset, then start taking calls, or making them, according to their job requirements. All data that is needed will be accessed from the corporate wiki, or entered through a program on the tablet;
- Medics in ambulance will pick up their tablet, which contains detailed programs on medical issues, and the ability to read data from the various medical devices in the ambulance, to report probable diagnoses. This data gets transferred to the hospital network, when the patient is admitted;
For reasons I've outlined elsewhere, Biblical software that is cloud based is an absolute no-no. More pointedly, cloud based software is always unacceptable, unless it is in a cloud that you physically own, and physically control.
The hard part of the equation: Developing software that can satisfy the 2009 Bible Software Shootout criteria, and also run on a tablet with 1GB Ram, and also does not go into the cloud.
jonathon
