Or, for those who came in recently, things used to be really old fashioned...
Still... hard problems tend to involve exponential resource costs, and
for those kinds of issues not much has really changed.
--
Raul
On Thu, May 26, 2016 at 8:06 PM, Joey K Tuttle wrote:
> Ironic, but even so the ch
Ironic, but even so the changes are astonishing.
Those Olden Days don't seem that remote, but it is hard to assimilate how
things have changed. I spend a little time trying to make personal sense of it
by tinkering with comparisons illustrated by things like the links to c.1985
IPSA data cente
The irony here is that these "outdated" and "slow" computers are running
just as fast as they did the day they were installed. Then people thought
they were really great.
On Thu, May 26, 2016 at 11:14 AM, Raul Miller wrote:
> [I am taking the liberty of trimming the body and editing the subject,
[I am taking the liberty of trimming the body and editing the subject,
here, to fit the subject change. For people wanting the original
context, http://jsoftware.com/pipermail/chat/2016-May/006994.html
should have it, for at least a while...]
On Thu, May 26, 2016 at 11:31 AM, Mike Day wrote:
> I
Good stuff! I started with Fortran on a CDC 3300. I remember the Punch
Operator was Jennie. We would wait late at the computer bureau for our
results, usually failures, which would require Jennie to punch up a new
deck of cards next day. This was Transportation Modelling, so minimum
path
Scott Locklin's blog had an interesting writeup on fortran code and
some of the implications in the context of modern computing:
https://scottlocklin.wordpress.com/2016/05/26/numeric-linear-algebra-code-an-appreciation/
Some of you here might be interested in that...
Thanks,
--
Raul
--
