Re: I'm pondering how bad "government control" would really be
Now that really would be a threat - if he gets pushed out Harding might be put in to replace him.
42420 publicly visible posts • joined 16 Jun 2014
I remember installing DecNet S/W on an HP-UX box to communicate with a VAX. DecNet packet addressing was based on the assumption that all the NICs were Dec and so had the same MSBs. in the MAC. In order to work the S/W changed the HP MAC to look like a Dec with no warning. This rendered all the users' caches invalid and broke their connections. Fortunately this was in the days of character-based applications with client and RDBMS running on the same box so there were no database connections broken and the user PCs caught up with the change of address pretty quickly.
OTOH - trying to get through to management that the system was designed to set up new products through a proper user interface that stitched everything together properly and not via a list of instructions for the DBAs to execute individual SQL statements that required CC clearance.
"No real problem when you're ... simply replicating transactions to a standby system"
The real problem is getting it past the bean-counters. "We're paying how much for this? And you want to pay the same again for another one just in case?"
Remember that this was all too often sold on the basis that it makes problems like this go away. Of course all it does is make them just go out of sight.
A simple solution. Challenge to granted patents is taken out of patent offices' hands but any patent successfully challenged by negligence of a patent office results in the office being responsible for all the challengers' costs and damages resulting from any lost income.
Just watch the number of successful patent applications fall.
It will likely be peppered with "syntactic sugar", such as the "quotative like", "ummms" and "aahs", and all sorts of syntactical errors which you wouldn't see written in an email, for example.
Sugar is too kind a word.
I've certainly seen one example of the intrusive "like" (fortunately on the decline, not so fortunately being replaced with the millennial "so) in a query on a technical forum. The query was about excessive memory use. I was tempted to suggest the memory was filling up with superfluous likes but I doubt he'd have understood.
"File" is one word that is definitely anachronistic now. Back in the days of punched cards it was meaningful to speak of a file of cards, file in the sense of objects lined up in a row (cf rank and file).
In terms of representing physical objects used in offices a file is usually a folder containing a number of documents. "Document" would be a better term than "file" as used in computing today. XML terminology does refer to documents but they're usually implemented as files.
"It's what you do afterwards that really counts."
It's amazing how reactions vary. I had experience of a fire in the '70s. The fire affected one wing of the building. The top level management came to the decision that those of us who occupied that wing had to remain on the site for security reasons, quickly arranged for alternative accommodation for the others and decanted them out, and arranged for a few portacabins. Almost every department set to work sorting themselves out in their new space allocations, cleaning up, replacing equipment etc. and got back to work ASAP. One department whose equipment had survived unscathed just piled it up in their allocated space and sat there for days, apparently waiting to be told what to do.
"But browser?"
You see the space where you type URLs? Type something in there that isn't a URL. What happens? If I do that with Seamonkey I get a complaint about an invalid URL. If I do it with FF or any derivative I get search results. Doesn't it need the browser to send everything to a search engine to do that that?
With Palemoon I can at least choose DuckDuckGo or whatever as the search engine it sends it to. So far I haven't succeeded with FF although I haven't tried hard because I can mostly avoid it.
Information?
Once the offence-taking industry gets hold of it they don't need information. If they say it's bad then it's bad by definition.
I wouldn't normally be in favour of an Academie Français approach to language definition but it really seems that we need one to stop English from being stolen. Although if there was one I can guess the sorts of people who'd consider themselves entitled to run it.
"Reforms intended to protect the innocent from miscarriages of justice became the focus of BBW's campaigning, with the pressure group arguing the pendulum had tilted too far against victims of crime."
This is a fraught area. Those who are subject to a false accusation are also victims of crime.
IME investigators really do want to do the right thing by the victim but working out who the victim is is far from straightforward.
Whilst I have no enthusiasm for FB and the like the potential for collateral damage is huge. The basic principle of the WWW is that if you post something there it can be linked to. If you don't want that to happen don't put it there. If you don't want it indexed protect it with robots.txt. If you don't like that go off, sponsor some hard engineering effort and invent something that works the way you want but don't forget to make it attractive enough to the public that they'll want to use it.
I can't help feeling that the traditional media giants have come along, decided this was something they could exploit and, discovering that it doesn't work exactly how they want, are now trying to change the way it works.
But SCO - the old SCO, not the litigation machine - had a free or cheap development licence that was only supposed to be used for 6 months but never timed out. You needed a floppy, and CD drive to install it. If they'd just sold the ordinary licences at an affordable price Linux would have been one of those archaic 90's curiosities that you vaguely remember and kids disbelieve. And SCO would have dominated the office server market ever since.
"I kind of miss how insecure we used to be able to be"
Support modem plugged into the back of the Unix box. Dial in from a Nokia brick Communicator. Pick up email (this is one that will get the kids - Unix boxes have the facility for internal email so the overnight jobs email their output to a user who can then read it on a character terminal with elm or pine etc). rsh from one box to another - none of your telnet here!
A client with problems would ring me at my main client's office, then unplug his fax and plug a modem into the fax line and, again, dial in from the Communicator.