"Delphia and Global Predictions marketed to their clients and prospective clients that they were using AI in certain ways when, in fact, they were not."
If they actually had used it perhaps they should have been charged more.
32673 publicly visible posts • joined 16 Jun 2014
"I rather suspect some of these acts might be provoked by annoyance over where these cabinets are sited."
Ditto siting of 5G masts. Friends have one of these fuggly monstrosities towering over their garden. It's sited on a verge which had had a bus shelter refused planning permission because it would have blocked the sight-lines of a road junction. A mast and large box doing the same thing isn't so constrained.
You make a fair point but to some extent it would be up to the property owner to make their decisions. My own cabling is underground and was laid before a concreted drive and paving laid in concrete was installed and an orchard planted over the route between perimeter and house. That makes replacing with any other media by the same route fairly unlikely. As FTTC speed is quite adequate for my needs and I don't particularly care to have overhead cabling my considered choice is to stick with that. In the situation the OP described, however, the cable appears to have been at the edge of the flagged courtyard so some sort of protection could have been fitted fairly unobtrusively into the angle between yard and wall. As for laying across a lawn which is what I mostly had in mind....
And your salesdroid sounds as if he well deserved to be fired along with whoever hired him. Grade I listing and conservation areas should be a warning flag that it will cost a lot more. I bet the building owners were amazed to get a quote at a fraction of what everyone else was quoting.
The installation should at least have been done competently. I doubt laying the fibre on the ground surface would count as that. I hate the overhead mess that's being made (or made worse depending on the number of copper lines already strung overhead) but it's at least a reasonably secure way to get the connections to the premises. I'd have thought there'd be some minimum standards for height of non-buried cables and maybe depth of buried ones. Zero wouldn't work for either.
This is why such services get at least some degree of regulation. The guilty here are HMG (other, similar gummints are available) who are in such a hurry to digitalise (sic) that they're not only failing to do that, they're willingly downgrading any existing regulation to get it done.
"There was one national network operator and two threats: nuclear war and terrorism."
There was and is more than that: floods, fires, landslips, JCBs, power outages and, not least, field engineering doing stuff without telling customer service.
By phasing out POTS we're ending the immunity of the domestic telephone to power outages. I'm not expecting everyone to realise they need a UPS, nor of a cheap UPS's chances of surviving a real power outage. What's more the last power outage here seems to have tripped something in the local cabinet as the network went off at about the same time as the power but didn't come back until much later. In the dash to Go Digital the telcos have been handed a free pass to end the old requirement that the phones should just work.
Almost every interaction with a business these days results in a "feedback survey" by email or phone.
If it's an SMS phone message it gets the report and block treatment. If I absolutely have to deal (as rarely as possible) with those who are apt to end such guff I allocate them their own email address and set it to bounce as soon as the transaction is complete.
"infosec teams responding to incidents by attacking them without a rehearsed plan."
No plan survives contact with the enemy.
I've successfully rehearsed DR plans for the systems I was responsible for. I doubt very much they'd have worked in an emergency, not least because I had no idea how the DR centre was to be linked in to the recovery plan of the rest of the businesses. In fact didn't know what the rest of the businesses' plans were or even if they existed. As tot he latter I had suspicions.
"When I see somebody in a Ferrari I always feel kinda sorry for them."
When I saw somebody in a Ferrari I used to feel pleased for my cousin-in-law. He used to service them.
He was also racing mechanic for a local farmer (related to a a cousin-in-law on the other side of the family, as it happens) who raced a vintage car. For a road car he had Lancias. When the V6 Dino came out he bought one of those instead. Callied in to visit one of his mates and got "Yer do, Cec. I hear tha's bought half a Ferrari."
You still haven't said what you were doing to get told to get this and get that at the command line. Were you writing from your own experience or just repeating what somebody wrote on the internet which was repeating what somebody else had written on the internet who'd seen an actual developer working away at the CLI because,as somebody said above, that's what developers do quite a lot of the time?
Or possibly seen somebody like me hacking away to reformat some big text file because Unix, with its CLI toolkit does that better than just about anything else on the planet and has been doing it for decades. You could do that on Windows, of course but you'd either have to install WSL or Cygwin because unaided Windows isn't going to cut it (or paste it or tail or sed it either).
"If you have a geriatric PC that, when it was new, ran Windows 7 reasonably well, then today it will run Zorin OS just fine."
From TFA: "If you have a geriatric PC that, when it was new, ran Windows 7 reasonably well, then today it will run Zorin OS just fine."
I have a cousin-in-law that's been running it on the same PC ever since she got ransomware under W7. It's a couple of miles away so I can't check the spec but it must be a decade or more.
FWIW SWMBO is running full-fat Devuan/KDE on an old HP laptop which I think started life with W2K on it.
"Linux users don't get why I'd use a Mac."
I do. It means you're earning money from it and are prepared to pay accordingly. Before I retired I used to run SCO on a laptop as a stable Unix platform and it was on client's servers as well. If they'd not played silly buggers instead of realising they needed to cut prices so that they could compete with free but, at the time, very immature, I might be doing so still.
From my PoV Mac laptops all seem to have screens too tiny for my ageing eyes.
"You may have to download and run the installer on it from the command line."
Exactly the point I was trying to make.
And the point I was trying to make, if you'd quoted the next sentence: "Alternatively you may have your installer set as the browser's handler for that sort of file." is that you may have the option of doing it from your browser by setting gdebi as the handler for .deb* files.
It would have to be set up to require a password to d o that. Whether you think being able to click and open as root random files from the internet is a good idea is another matter...
Convenience is not everything.
* Or whatever is appropriate for the package manager.
But would ChromeOS work for me? To take an example, for graphics (largely tweaking images of patchwork for SWMBO and annotating maps) I use a mixture of Gimp, Pinta, Gwenview (yes, even that has its uses to do more than just display) and sometimes QGIS. They all tend to have aspects for which they're more convenient than any of the others. I suppose if I had to use just one it would be Gimp but really any single one would be a pain. Maybe I should try Krita but the UI looks as if it's intended for the coloured pencil department and I most certainly wouldn't fit in there. What would ChromeOS offer for that?
AFAICS ChromeOS has its biggest audience in schools where it's possible to tell users that that's what they're getting and they're not likely to be given tasks that exceed its capabilities.
But I agree with you that there's scope for a Linux distro tweaked to online use. Say something like NextCloud as a back end hosting the user's home directory through davfs with server URL as part of the sign-on screen for security (if forced to divulge a "password" the URL might not be the usual working server).
"Windows users still think it's funny to joke that running Linux means learning to build your own OS from sticky tape, glue, toothpicks and cardboard tubes. It's not like that anymore and hasn't been for most of this century"
Not only has it not been the case for most of this century but, as a Linux user, it seems to me that this is exactly what running Windows has become. I have one old laptop with a W10 partition on it which isn't used much but I do tend to force myself to go through the pain of regular updates.
To get from the menu to where Windows update starts to throw dots across the top of its window probably takes about as many clicks but more time than getting from a Linux menu to Synaptic starting to run the actual upgrades. Note that to get there for Synaptic includes having completed the equivalent of that throwing dots stage. Note also that Linux, even using sudo, takes a stronger line on security then Windows and will have required a password to run Synaptic so the time to do that will have been included. (If the inconvenience of a password is what puts you off using Linux, there is something seriously adrift with your priorities.)
If I choose to do so I can review exactly what packages Synaptic is going to upgrade and I can watch the commands streaming smoothly past (Windows is still throwing dots). With Windows I will eventually see a rather opaque short list of updates it proposes to install including the one that it failed to install last month and the month before plus that same Intel display update that seems to get installed every month and comes back next month.
If I'm lucky Windows will install these with only a single reboot needed. The reboot will, of course, take ages to complete because although it also took ages to get to the reboot a lot of the updates are done at the reboot stage. With Linux reboot is almost always confined to kernel updates which, running LTS kernels, aren't that frequent and is simply a matter of restarting as and when is convenient so that the new kernel, which is ready and waiting, can be used. For everything else the executables are simply put in place so that next time a program is executed the new binaries are used. Services are written to be restarted so if a new version of a service is installed that's what happens. In many years I've seen exactly one service that was so low level it needed a reboot but, again, not urgently but just in the normal course of shutting down and starting up again
In practice I find it's even quicker to fire up the terminal emulator, su and run three apt commands than click around menus but if GUI is your preference then that's fine but this elephant in the Windows room has to be addressed:
There's that hanging update on W10 that won't go away. The oh-so-slick, oh-so-clever Windows initial set up created a partition which it has now decided is too small. What's the solution to that? AFAICS you're supposed to shrink your C: drive - assuming it's not too full for that - drop into the command line, look up some info on that too-small partition, take a note of it, delete the partition (no, not your C: drive's partition - did you screw up there?), recreate it to a larger size and run some stuff manually based on the note you took, all at the command line. How's that for string and sealing wax?
"but Linux for consumers needs to be a single desktop environment so users get that constant familar interface with the minimum of bundled apps"
I'm struggling with this. Are you saying Linux uptake would be better if distros just had a minimum of apps so it would be able to do less? Where's the sense in that?
Packages where I can click and install are great, but I grew increasingly frustrated by the regular prompts to use the console with half a dozen "get this/get that" commands.
Can we clarify what you're doing to be prompted with "get this/get that"?
The only time I will see that is in some online article entitled something like "How to install $App on $distro". The first thing to do is to pop open Synaptic or whatever your distro's software manage might be and see if it's there. If it is just select it for installation and click Apply or whatever it might be. If it's not in the distro the next step is to look to see if it has an install option - a .deb file or whatever - for you OS, FlatPak or Snap. If it has, use that. You may have to download and run the installer on it from the command line. Alternatively you may have your installer set as the browser's handler for that sort of file.
Only if neither option is available would you need to resort to hand-knitting and you're probably getting into the realms of somebody's pet project which might be interesting, might get into the mainstream distro repository or might disappear without trace.