Re: You want
"because us victims cannot make the change to get away for windows"
Mostly you could. But because Microsoft are skilled at frog-boiling you won't.
How bad are you going to let it get?
42414 publicly visible posts • joined 16 Jun 2014
"When will it change?"
By now it should be dawning on boards and, I hope, fund managers, that insurance isn't really going to cover the reputational damage and general chaos that they've seen the Co-op, M&S & JLR experiencing. They should be asking their IT depts what they're going to do about hardening systems, building in resilience etc. (BTW have any commentards been on the receiving end of such questions?). I do fear, however, that some are going to simply reply "More Microsoft" if comments here are anything to go by.
"The UK is the only country to have developed an orbital-class rocket and then cancelled it."
Developing technology and cancelling it is our national speciality. I put it down to having a political class that doesn't realise that the expense comes upfront which means that the first built appears very, very expensive and they take fright.
"In other words, rather than provide a hyperlink, the author of the page expects the reader to copy the text, work out the abbreviation for their desired architecture, edit the URL to insert the abbreviation in place of the part delimited with a dollar sign, and proceed from there."
Errm - no. Copy and paste "https://pkgmaster.devuan.org/devuan/dists/excalibur/main/" like wot I just did, scan down the index with Mk 1 eyeball and click on the appropriate link. No editing involved.
BTW it's not directly named after King Arthur's sword. It's named after a minor planet with a name starting with "E" and a minor planet named after King Arthur's sword was chosen. Releases are named in alphabetical order.
AFAICS it looks very much like emulating the Windows experience.
Current Linux practice is along the following lines:
libwhatever is used by a lot of executables - low level stuff such as the command line shell and the graphical shell, the command line and graphical file managers and higher level stuff such as a browser, a couple of graphics applications, an office suite and others*. Some vulnerability in it is fixed or maybe some clamoured for extra functionality is developed. The new version is placed in the repository and a user's regular update process discovers it, downloads it, either automatically or by user approval, and everything that needs it just uses it on the next invocation. It's very quick and the only things I've ever seen need a reboot are a new kernel and, on one occasion, a very low level service. In practice a few small updates might pass through every week, a larger batch of programs that work together every few weeks and a new kernel every few months.
As I understand it the immutable version of doing things is that in order to do this an entire snapshot of the core OS has to be created, installed and booted. I doubt this is going to happen just because libwhatever has been changed because it will be disruptive so it will only happen at intervals (monthly? every 2nd Tuesday?). If libwhatever has security issues the core is going to have to live with it unless an out of schedule update is issued. This becomes very Windows-like AFAICS. Maybe this is the intention - make it familiar with a lengthy, disruptive update happening every month. There's also the added detail that AIUI those higher level applications, the browsers etc, aren't going to use the libwhatever in the immutable core, they're going to have their own version in a snap, flatpak or wherever which is a bit of a lottery because they might get the newer version faster than the core if it's released more quicker** or never if the packager never gets round to it.
* In a few cases applications might have their own version for some reason and the launch process has to arrange to use it. It will be stored somewhere out of the way - an application-specific directory tree under /opt is the accepted place or /usr/local if it was locally compiled from source, Like snaps etc it might get updated on a different schedule to the main system implementation. If you're Ubuntu or whatever this suffers from NIH syndrome.
** What would be the schedule for releasing these? As and when ready as per current practice or alongside the immutable core?
"You're going to select or design components with energy- and mass-efficiency as a top priority"
You're also going to select for radiation hardness as a top priority. Is it going to be another of those triangles: energy efficiency, mass efficiency, radiation hardness, choose any two?
"The AFP and FBI stopped using AN0M because it produced more evidence than they could comfortably handle. The AFP, however, still wants access to encrypted communications"
When it's solid intelligence they can't cope but they still want haystacks in which there might be needles. It's just data fetishism.
The difference between an LLM or any other sort of alleged AI, general or otherwise, and you and I is that they cannot experience reality and we have spent years doing so. We have an internal model of the outside world that we spent a few years getting up to scratch and the rest of our lives keeping that way. It gets regularly checked against what we experience. We interact with that outside world. We know - from experience - that it can hurt us sometimes, that it can please us and that it is essential to our ongoing lives. When we look at things increasingly distant from our everyday experience we are less likely to add them accurately to our internal model although it helps if we have learned critical thinking skills.
There are three words I've used there that are critical to the difference between a human - or animal - intelligence and AI: "reality", "experience" and "life". Their only internal model is a set of relationships between words. A LLM trained in French will have different words between which to establish relationships than an English one. Monoglot English and French speakers have the same understanding of, say, a motor vehicle. A program existing in a computer has never ridden in one, driven one or shelled out hard-earned cash to buy one; it has no understanding beyond linking the outer forms, the words together. It is not further forward - more likely many steps behind - than the cargo cultists in Feynman's lecture who thought that, by clearing runways and imitating air traffic controllers, they could get planes to land and unload cargoes.
"On the other hand wasnt offshoring call centres to India tried and then they relocated back because customers didnt like it?"
Usual business cycle.
REPEAT
Cut costs, get bonus, move on.
Repair damage, regain customer base, get bonus, move on.
UNTIL THE COWS COME HOME
I've always reckoned an effective strategy would be cut advertising and marketing costs and deploy the saving into good products and customer service and just gain market share from the others' customer churn.
"The issue I have with Snap and Flatpack is that they are the wrong solution to a problem"
They're a solution to an already solved problem.
If you want to know how it's solved download LibreOffice from the project's download site and run the installer on it. Look at where and how it's installed. (Disclaimer - I'm only familiar with the .deb version but expect the .rpm will behave similarly.) That's been a solution for years but doesn't come with a trendy name.
"The government's idea is that everywhere in England will move towards the unitaries and combined authorities structure."
And the consequence will be that areas with relatively little in common will be squashed together so that decisions will be taken by officials with zero local knowledge.