@lproven @theregister

That was very interesting - and brought back memories of porting MS-DOS 1.25 from the PC to the close IBM Clone of Future Computers.

All in assembler too 8(

@Extelec

First offered fast broadband where we live in March 2013 - still waiting!

There are lots of systems (medical/fire/personal alarms etc) that rely on powered telephone lines. Recent 3-day power outage here left POTS lines as the only communication system still working when mobiles went off as well.

A very backward step I think to get rid of the analogue lines (but it will, of course, save Openreach et al a lot of money in the long term...)

@tychotithonus

Indeed.

Y2K was, however, a chance for some companies to (attempt to) offload the responsibility for compliance onto their customers.

I well remember one supplier to the shipping firm I worked for (as IT manager) insisting that WE certified that all our other suppliers and freight customers were Y2K compliant or they would no longer deal with us. With over 10,000 customers and suppliers there was no way that we could possibly do that...

@lproven @jmmv

Oh, and I still use vi on a regular basis today (on VMWare ESXi console and Linux machines) having learned it back before SCO Unix existed.

With the exception of some programming techniques I don't think anything else I have learnt in my long career has lasted as well or been as useful!

@lproven @jmmv DOS days it had multiple edit windows (tiled or switchable) etc.

I used SideKick myself for a while, but as an outliner, not a program editor...

Although I was never a fan of EMACS (some people are as committed to it as Liam is to LISP!) it was very powerful and could be 'programmed' to do almost anything - so you could compile in the background, review errors, all whilst also editing email, doing sysadmin etc - IMHO it tried to do too much really.

vi (and EMACS really) (...)

@lproven @jmmv - I still have the manual)!

Horses for courses... 8)