|
|
|
|
|
by fay59
1383 days ago
|
|
Yes, but your 1995 Windows NT 4.0 PC ran a 640x480 display at 60Hz and graphics compositing had, at best, one-bit transparency. It took 3 minutes to boot. Websites could bluescreen it with `<img src="con">`. A malicious attachment could trick your email client into deleting your whole hard drive. |
|
The "img src=con", and to a lesser extent, the "malicious attachment" thing could be solved on the same PC by running something not-Windows. 1995 might have been a bit in the teething era for Linux and BSDs but maybe some commercial Unix would have been viable?
The "3 minutes to boot" would be largely ameliorated by using a SSD and by the fact the phone is largely a fixed hardware tree that doesn't require significant probing and dynamically selecting drivers at boot time.
Getting to a higher resolution and colour depth-- okay, maybe you need to advance to say the specs of a decent 2005 PC (1Gb memory, early x86-64 CPU, DirectX 9 class GPU) to get there.
But beyond that, I think we're paying mostly for poor software design. How many apps are loading big full-featured browser engines when all they need is libcurl and some minimal optimized rich-text system? How many apps are relying on dynamically loading content that could have been permanently baked into the bundle (i. e. a shopping app's category tree?)