You don't
specify what "a web browser" is. What most people mean by
that is something that often won't run at all, never mind run well,
on "slow machines" like my SS20.
That is true. But then, there's
lynx :)
There is. lynx is what I use when I have occasion to care about
something Web (which isn't really all that often; I avoid the Web in
general). (That's why I qualified it with the "what most people mean
by that" part. :)
A lot of development these days doesn't get
compiled (e.g. PHP).
Well, doesn't get compiled in the sense we're talking about here; I
think PHP, and certainly many of the "doesn't get compiled" languages,
do indeed get compiled, if only to pcode, when run.
And yes, for big projects, you need to scale up
somewhat. But it's
not as if compiling is what one does all day.
Sure feels like it sometimes - which I suppose is what I was saying.
In between compiles, you need to do what a programmer
does. :)
This is very true.
I moderately
often work with a piece of software that, even on a
relatively modern machine, takes significant time - long enough for
a human to get frustrated - to build. I just now did a test build,
in a ramdisk on a Core 2 Duo at 1.8GHz, and it took a minute
fifty-four seconds.
One source file? Or many?
Many. git. (There are worse - X, and NetBSD itself, come to mind -
but I don't mess with them often enough to feel they're fair examples
for this discussion. Though come to think of it it's been a while
since I did anything to git....)
I think the largest single source file I work with may be my tar, which
is 304672 bytes, 11301 lines (I just checked). I just test-compiled
that on my SS20, and it took 28 seconds - without benefit of ramdisk.
/~\ The ASCII Mouse
\ / Ribbon Campaign
X Against HTML mouse at
rodents-montreal.org
/ \ Email! 7D C8 61 52 5D E7 2D 39 4E F1 31 3E E8 B3 27 4B