"But the flipside is that it means systemd will gradually encroach on even more of your operating system."
BSD gets closer.
40557 publicly visible posts • joined 16 Jun 2014
But what do they mean by cement? My understanding of cement is Portland cement - the calcined mix of clay and lime. Mortar - the stuff that holds the bricks together contains mostly of sand with some cement. Concrete, the stuff your foundation are made of, consists mostly of aggregate, sand and cement. The amount of cement is an order of magnitude less than the volume of the foundations.
There seem to have been very recent changes. Waterfox has escaped from System 1. Basilisk has separated from Palemoon. BinaryOutcast seems to be busy rebuilding the website - it appears to have gone through some sort of trauma; I don't know if the browser has been discontinued and only Interlink is surviving. There also seems to be a new Thunderbird fork, Epyrus on the go related to all this.
The issue for me, and, presumably for many, is that after Mozilla made their changes (TBH I never really followed their Quantum, Australis or whatever it was and all that other branding stuff) they could no longer follow existing desktop theming and just looked as if they didn't belong - not as ugly as GTK4 but certainly not as intuitive to use. The marketing and crayon departments are in charge - both at the browser vendors and the websites - and they want New, New, New whilst a good user interface needs, the opposite: clarity resulting from consistency and familiarity (which is consistency with the past).
"For a while, it remained possible in the Waterfox Classic fork of pre-Quantum Firefox, but today, sadly, that browser is barely usable anymore."
What about Palemoon and/or Basilisk?
Actually an article on the Mozilla spin-offs would be welcome. I've read the long article on the Palemoon site and left with the impression that it's the XUL Liberation Front vs the Liberation Front for XUL or something along those lines. Throw in Epyrus & the Matt Tobin projects for good measure.
"greenhouse gases are a byproduct of an economy wedded to cheap energy in one case, and in the other single points of failure in an industry wedded to huge datasets in under-engineered systems"
In the first case you have to remember that as a result of allegedly environmentally based Luddism use of nuclear was minimised for decades. In the other we have the opposite of Luddism - a rush to either transfer data out of the data centre to somebody else's computer somewhere on the internet or to keep it in-house but insufficiently separated from the internet.
Thanks, a link to a very useful article I may need to read it again and follow up the references. The lest bit - on whether models had developed the ability to reason and that it might not be possible to decide left me wondering about the reasoning of those doing the tests. Did none of them additionally ask the model to explain how it reached its conclusions?
I'm glad you liked the twist.
Sounds like you produced what I call "ravioli code".
If your analogy is correct there would be just the same amount of code there, just packaged differently. The main object of the refactoring was to reduce the LoC and hence the amount of memory consumed at run-time.
I get the impression that some people have been brainwashed by the low resolution of digital cameras and don't realise what photography can actually do with a large format. The information in a large negative would be hard to match in digital although Leica did,as I recall, try setting what was essentially a scanner mechanism on the focal plane of a large format camera. The time needed to set up a shot on a large format means that the result reflects a degree of thought denied to that of a point and click.
"the only way to test the output of a change is to actually deploy it in production."
One program in the system I looked after had been written by a programmer who, thankfully, had left long ago. It always annoyed me because of her odd programming style. It largely consisted of much the same code repeated multiple times. It was ripe for refactoring as we say now but maybe not at the time.
Late one afternoon I decided to tackle it.
One block of code was repeated several times. Copy that into a function and replace all the repetitions with a function call. Very straightforward. This must have shrunk the LoC to about half.
The remainder of the repetition consisted of two similar but not quite identical blocks of code each repeated several times. Not quite so straightforward. Copy one version into a new function adding a switch parameter then add the different sections of the version using the switch parameter to decide which t call.
Replace the repetitions with function calls taking care to use the correct value of the switch.
We now have a much simpler program, a fraction of its original size. It ought to be easier to understand what it's supposed to do which was one of the objectives of the change. But the remainder is still a bit of a tangled mess. Sorting through it to work out just what data would be need to test all the alternative paths would still take ages.
Well it was really all very much a mechanical replacement - the same code is being run, just from one of the two new functions instead of inline. Of course it must still work exactly the same as before.
It was now early evening. Why not put it live?
So I put it live.
Of course it worked exactly the same as before - what did you expect?
"Just like Jansen, Kirkby inherits a massive cost-cutting programme that will see up to 55,000 BT jobs wiped by out by 2030."
I think the target is to reduce staff to board, C suite, an outsourcing contract manager, their PAs and receptionist, a tea-lady an extensive catering staff and a cleaner.
Web applications are missing a lot of the "systemness" we expect from traditional computing environments
It depends on what you consider a traditional computing environment. In my working world that was a multi-user database system. If there were access levels for different categories of user it may well have been down to the application designer to build in safeguards.
If Buildings Maintenance was to be prevented from seeing tenant financial data that might be an administrative matter to ensure that Buildings Maintenance didn't have access to the screens for financial data. If, on the other hand, Crawly Buildings Maintenance shouldn't see data on Coventry buildings and vice versa but Estates Management could see data for both then it would have to be handled by something a bit more complex in the application itself.
What web applications are missing is a lot of statefulness and shoving responsibility for that onto the client.
"An IT director unfamiliar with basic computer operation? Say it ain't so!"
Why should it be so?
IT directors fall into 3 categories:
- Those who have a purely administrative background - maybe a degree in music or whatever - rather than IT.
- Those who have operational IT experience but with obsolete systems.
- Those with operational experience of current systems.
It's not easy to say which category is the most dangerous.
Add the date and time to your note - both the date and time of the request and of the note.
Best to have a procedure in place that instructions have to be written "for the log" so that asking for written instructions for something dodgy can't become confrontational quite so easily.
"I guess Trump has a gift for recognizing corruptibility"
His minions are probably a self-selecting crowd, slow to disabuse themselves of the reality of what's in front of them. They were probably last of their age group to realise there was no Santa Clause.
It seems an effective way of getting a reputation which will lose business in the long run.
With rented houses comes the little matter of leaving the garden in good order. A group of us had rented a house which was actually the property of the parents of another student* who had gone abroad for a year. One of the students was a farmer's son so at the rental he just got one of his father's farm workers sent along to sort it out.
* The student was sent down having been discovered depositing the Greek professor's bike in a lecture room. The bike was in two pieces which he'd just separated with a hacksaw. To be fair the Greek department's bikes were an ongoing problem - I don't think the staff had grasped the fact that they were no longer in Oxford.
"I have little time for landlords not being quick to remedy faults."
It's not necessarily landlords. When we were first married we rented a top-floor flat & had problems getting the leaking dormer fixed because we were dealing with agents. They never did fix the major crack where the staircase block was coming away from the house. It wouldn't have been in the owners' interests to let the property deteriorate to that extent but it would put the agents to a certain amount of effort beyond the collection of rent and deducting their fee.
OTOH The US is having development of a plant put on hold due to shortage of skilled labour. Not my area but I'd guess the skill shortages include preparation of masks, adjustment of the machines and handling of various nasty chemicals involved. I'm sure others here could add to and correct that list.
One thing you omitted to mention is wafer manufacture. There will be a whole lot of specialist skills involved in that.
These are skills of which there are probably not many holders at any age level. I doubt anyone holding them will be unable to get a job at any age but it's not surprising that that they want to concentrate training on those who are likely to use them for longest.