"We look to unleash the power of digital engineering and agile software yada yada
Don't much about U2s or K8s for that matter, but I still score pretty high when it comes to bullshit bingo!
175 posts • joined 19 Mar 2007
Since lock-down, I've used (for work and leisure) FB messenger, Google meet, MS teams, Skype and Zoom. Zoom for me is head and shoulders above the rest: simpler to set up, better audio and video quality, and more reliable (of course your experience may be different)..
I think it's telling that this is from a start-up who focus on doing one thing and doing it well, as opposed the the offerings of various mega-corps who see something new and want to add a slice of the action to their portfolio.
I guess it's only a matter of before Zoom get bought by someone much larger, and I'll have to start looking for an alternative.
I got that from a Fred Fish PD library floppy. The developer actually had his personal telephone number in the docs, I rang it once and a slightly fed up sounding better half answered it and shouted up the stairs in a rather resigned tone of voice "Stevie, North C!".
You tell that to the youngsters today and they won't believe you.
There was a free compiler for the A500 called NorthC, gcc was available for the A1200, but I'm not sure about earlier Amigas. With either, it was a problem getting hold of the header files to access various OS and UI functionality. I seem to remember that the price of Lattice C with a full set of header files cost more than the hardware itself, and can't help wondering how much this had to do with the Amiga's ultimate demise.
Hensa sure brings back memories, also from a poly, although I don't remember it being blacklisted. I seem to remember accessing it via ftp. One of the great things about was a good selection of Amiga software. I downloaded both gcc and LaTeX for the Amiga, (split over about 10 floppies if I remember correctly).
Dowsing a mast, or any other large object with petrol, especially by *spraying* petrol FFS sounds like a great way to get yourself a Darwin award.
As Frank Zappa said:
"Physicists say that hydrogen is the more abundant than anything else in the universe; they're wrong - it's stupidity"
Around the same time when EVERYONE in the building having their OWN personal computer was really rather exciting. One (fairly senior) chap, complained that his PC would spontaneously turn itself off at random intervals. Cure the usual visits from BOFH types. No hardware problem, but as this only seemed to happen two or three times a day at unpredictable intervals, a bit of nightmare to diagnose.
After a couple of weeks of to-ing and fro-ing the cause was finally identified: the machine was in a tower format, and installed under the desk at the back. The power button just so happened to be at almost exactly knee height ...
The only only advantage the ~15yrs has given me is to reinforce the message always stick with the defaults unless you are absolutely sure you need to do something different, you understand why you need to do something different, you understand how the alternatives work, and then try it out on non-production system first.
14.5 years ago, I only had 6 months experience with apt, and I'd never seen a dependency problem. That is why I now have 15 yrs experience. 99.9% of what I have ever installed has come from the standard repo's.
PS when I mentioned apt in my OP, I meant the overall packaging system, not necessarily the command line. The synaptic package manager provides a very nice gui and is what I use most of the time, and would certainly recommend to noobs.
To be honest, I think you might be installing things wrong.
In ~15 yrs of administering a small network of Ubuntu and/or Debian machines, I don't think I have ever seen a dependency problem installing from apt, and any other problems are as rare as hen's teeth.
Of course the situation is different if you are installing stuff from tarballs, in that case dependency problems are not unknown, and are, I agree, a PITA. However, given the range of software available in the standard repositories, it's pretty unusal to need to do this.
Likewise always assume that temporary means permenant.
This includes locations of downloaded files that have been placed in a temporary directory until I can think of somewhere better, temporary one-off scripts to fix an imediate problem, and the temporary location of last weekends curry that I was planning to reheat.
Biting the hand that feeds IT © 1998–2020