>I nevar had a MAC, just a successian of Windoze machines.
>
>But here's one stoary.
>
>Lonesam Cowboy Dave brought his Windows 3.1 PC to me once a coupal years ago
>to fix. Symptom was, it wouldn't boot.
>
>I looked at the hard drive. One gig. The WINDOWS foldar, the whole fucking
>thing, was like 35 MEG.
>
>I panicked and thought he wiped the WHOLE OPERATING SYSTAM AWAY SOMEHOW.
>
>But then some nerve cell which had lain dormant for years fired and reminded
>me, at one time THAT'S ALL THERE WAS OF WINDOWS! Indeed, it was all there
>and all he needed was somebody to restore the file that had the WIN command
>in it to start Windoze after DOS booted.
>
>And someone around here DARED questian why Windows 7 needs 780MEG of memory
>just to get to an idal state.
Try running something that requires a 64-bit function in the Windows 3.1
environment and then get back to me on that one, "genius".
--
Rob Cypher
http://robcypher.livejournal.com
http://www.myspace.com/robcyphercollective
http://www.facebook.com/robcypher
http://www.youtube.com/robcypher
http://www.twitter.com/robcypher
*
Music Reviews:
http://apps.facebook.com/visualcdrack/people/1713595594
Book Reviews:
http://apps.facebook.com/facebookshelf/people/1713595594
Movie Reviews:
http://apps.facebook.com/dvdshelf/people/1713595594
TV Reviews:
http://apps.facebook.com/livingsocial-tv/people/1713595594
Video Game Reviews:
http://apps.facebook.com/videogamerack/people/1713595594
*
WARNING - THE SHROOMERY IS FULL OF RACISTS. Proof is presented here:
http://robcypher.livejournal.com/68904.html
> On Sat, 19 Dec 2009 20:34:20 -0500, "iDRMRSR the Reclined Mastar"
> <idr...@myspace.com> wrote:
>
> >I nevar had a MAC, just a successian of Windoze machines.
> >
> >But here's one stoary.
> >
> >Lonesam Cowboy Dave brought his Windows 3.1 PC to me once a coupal years ago
> >to fix. Symptom was, it wouldn't boot.
> >
> >I looked at the hard drive. One gig. The WINDOWS foldar, the whole fucking
> >thing, was like 35 MEG.
> >
> >I panicked and thought he wiped the WHOLE OPERATING SYSTAM AWAY SOMEHOW.
> >
> >But then some nerve cell which had lain dormant for years fired and reminded
> >me, at one time THAT'S ALL THERE WAS OF WINDOWS! Indeed, it was all there
> >and all he needed was somebody to restore the file that had the WIN command
> >in it to start Windoze after DOS booted.
> >
> >And someone around here DARED questian why Windows 7 needs 780MEG of memory
> >just to get to an idal state.
>
> Try running something that requires a 64-bit function in the Windows 3.1
> environment and then get back to me on that one, "genius".
> --
> Rob Cypher
Actually, the size of the OS files on disk has little to do with 64 vs 32 bit. I
don't know Windoze, but on OS X the language support takes between 0.5 to 1 GB
by itself. Printer drivers are another disk space hog. Closer to the core, the
tendency to use higher-level languages and object-oriented programming to build
system & support programs does not help either, I suspect.
It's called progress. The lifetime of a system release is too short to write in
a relatively low-level language and to optimize its code the way one may have
done in earlier days. OTOH processor power & memory/disk space have doubled
every 1.5 years, roughly speaking & to a certain degree the hardware has finally
outrun the software (at least as far as system & ui are concerned).
Or, to put it more succinctly, you can't afford the smaller systems of yore
anymore if you want today's ui & features etc.
Mac Dude.
>>> But here's one stoary.
>>>
>>> Lonesam Cowboy Dave brought his Windows 3.1 PC to me once a coupal years ago
>>> to fix. Symptom was, it wouldn't boot.
>>>
>>> I looked at the hard drive. One gig. The WINDOWS foldar, the whole fucking
>>> thing, was like 35 MEG.
>>>
>>> I panicked and thought he wiped the WHOLE OPERATING SYSTAM AWAY SOMEHOW.
>>>
>>> But then some nerve cell which had lain dormant for years fired and reminded
>>> me, at one time THAT'S ALL THERE WAS OF WINDOWS! Indeed, it was all there
>>> and all he needed was somebody to restore the file that had the WIN command
>>> in it to start Windoze after DOS booted.
>>>
>>> And someone around here DARED questian why Windows 7 needs 780MEG of memory
>>> just to get to an idal state.
>>
> Actually, the size of the OS files on disk has little to do with 64 vs 32 bit. I
> don't know Windoze, but on OS X the language support takes between 0.5 to 1 GB
> by itself. Printer drivers are another disk space hog. Closer to the core, the
> tendency to use higher-level languages and object-oriented programming to build
> system& support programs does not help either, I suspect.
>
> It's called progress. The lifetime of a system release is too short to write in
> a relatively low-level language and to optimize its code the way one may have
> done in earlier days. OTOH processor power& memory/disk space have doubled
> every 1.5 years, roughly speaking& to a certain degree the hardware has finally
> outrun the software (at least as far as system& ui are concerned).
>
> Or, to put it more succinctly, you can't afford the smaller systems of yore
> anymore if you want today's ui& features etc.
>
> Mac Dude.
I was pondering the stuff you just pointed out one day and it occurred
to me that if hardware development stopped software would/could keep
getting better for years...
p.s. Look how smart some birds are considering the size of their SquishyWare
--
John Cook
Reality is not Democratic
stop off-topic.