i'm typing this on a 2009 Macbook running macOS Sierra connected to eduroam and then on the computer lab vlan, with a kerberos ticket so that I can access the department filer using NFS securely.
this is mostly so i can upload the picture below, which is a screengrab of my calendar as viewed in calcurse, a neat app that lets you graphically browse your calendars on a "dumb" terminal, which I often use (well, ok, a terminal emulation running a shell via ssh). The reason i look at my calendar that way is that it is a lot clearer than if I use the fancy calendar apps on OSX or android, or web based ones - this got worse in recent years when I started working in the Turing Institute where, like many "hi-tech" institutes, for mysterious reasons all the admin is done using microsoft office (365/Azure based or with web access or whatever). So I'm forced to use an Outlook calendaring system there. Luckily, it is possible to integrate this with one's Google calendar (yes, I have one of these too) and I can then export all the iCal data to a file and synch it via the filer in Cambridge. I can also synch outlook&google direct.
I also have a simple ascii text file in my home directory, which (derives from v6 Unix days) has a date in a standard unix string form at the start of each line - back in the day, Unix had a cron entry that e-mailed you anything in lines with matching dates for yesterday/today/tomorrow, as a todo reminder (this is 1970s tech, of course - still works, but now I have a perl script that translates the text file daily into iCal, and then I synch it to Google and then Outlook synchs that.
All of this is running in cloud servers running in data centers with millions of cores clocked at several Ghz each, and many petabytes of storage, connected by networks running at 10s or even 100s of Gbps, yeah, even as far as the 1Gbps wired ethernet to my desktop in my office.
That desktop used to be a 17" Macbook pro, which worked fine, but cannot run even OSX Sierra (despite being slightly younger than this Macbook, which can) due to Apple mysteriously not supporting that hardware in that OS version. who knows why - all i needed was the kerberized NFS.
So in a cupboard at home I found an 8-year old 15" Macbook pro which supports High Sierra, so I connect that to eduroam; need signon to the lab VLA; need signon; to the kerberos ticket server; need another sign on; to lab db servers (need another signon) =land now my desktop is ok.
So now on all these machines, with super fast cores (even the 10yr old machbook i am typing on has 100Mpbs and two 2.4Ghz cores) and a nice screen and NVideo GEForce graphics etc
and I mostly type text and look at my ascii calender.
it worked fine on the MHz PdP-11 44 with 2Mbytes of memory, a 10Mbps cambridge ring, and a glass TTY connected to a 19.2kbps serial port.
Where did we all go wrong?
this is mostly so i can upload the picture below, which is a screengrab of my calendar as viewed in calcurse, a neat app that lets you graphically browse your calendars on a "dumb" terminal, which I often use (well, ok, a terminal emulation running a shell via ssh). The reason i look at my calendar that way is that it is a lot clearer than if I use the fancy calendar apps on OSX or android, or web based ones - this got worse in recent years when I started working in the Turing Institute where, like many "hi-tech" institutes, for mysterious reasons all the admin is done using microsoft office (365/Azure based or with web access or whatever). So I'm forced to use an Outlook calendaring system there. Luckily, it is possible to integrate this with one's Google calendar (yes, I have one of these too) and I can then export all the iCal data to a file and synch it via the filer in Cambridge. I can also synch outlook&google direct.
I also have a simple ascii text file in my home directory, which (derives from v6 Unix days) has a date in a standard unix string form at the start of each line - back in the day, Unix had a cron entry that e-mailed you anything in lines with matching dates for yesterday/today/tomorrow, as a todo reminder (this is 1970s tech, of course - still works, but now I have a perl script that translates the text file daily into iCal, and then I synch it to Google and then Outlook synchs that.
All of this is running in cloud servers running in data centers with millions of cores clocked at several Ghz each, and many petabytes of storage, connected by networks running at 10s or even 100s of Gbps, yeah, even as far as the 1Gbps wired ethernet to my desktop in my office.
That desktop used to be a 17" Macbook pro, which worked fine, but cannot run even OSX Sierra (despite being slightly younger than this Macbook, which can) due to Apple mysteriously not supporting that hardware in that OS version. who knows why - all i needed was the kerberized NFS.
So in a cupboard at home I found an 8-year old 15" Macbook pro which supports High Sierra, so I connect that to eduroam; need signon to the lab VLA; need signon; to the kerberos ticket server; need another sign on; to lab db servers (need another signon) =land now my desktop is ok.
So now on all these machines, with super fast cores (even the 10yr old machbook i am typing on has 100Mpbs and two 2.4Ghz cores) and a nice screen and NVideo GEForce graphics etc
and I mostly type text and look at my ascii calender.
it worked fine on the MHz PdP-11 44 with 2Mbytes of memory, a 10Mbps cambridge ring, and a glass TTY connected to a 19.2kbps serial port.
Where did we all go wrong?
No comments:
Post a Comment