Fujifilm FinePix S200EXR digital camera
RRP: $799.00
RRP: $799.00
I have the above Belkin and am able to configure it as an access point, but I want ...
Hi there We wish to purchase a multifunction colour printer/copier/scanner/fax - ...
I have recently loaded Windows 7 using a clean install after formating my HDD. I ...
Hi Looking at buying a laptop in the $1500 to $2000 range. I like the Toshiba ...
I hope someone can help with this. I bought an HP C 309a in September and installed ...
A chance to win with every
Samsung Consumable purchase*
Historical Neccessity
These changes come around every 30 years or so, and developers being clever and adaptable people learn the next best system and transfer their focus to new customers.
There will be those that can't change but most of these will find jobs maintaining legacy systems for quite a while. People still find work in Cobol even today.
Similar sentiments were expressed when the industry migrated from expensive mainframe system and equally expensive software licenses, over to UNIX.
Everything was different. Users had to learn new interfaces. New macros had to be written. Forms and reports had to be redone. Documents had to be translated to new data formats. Support staff had to learn new routines.
Yet it happened despite the initial expense. The key factors were long term license cost savings. Hardware optimisation. Interoperability. Less support staff.
Looks like the same thing is happening again. This time with Linux vs legacy Microsoft systems on the software front. What'll it be on the hardware scene?