Re: Access Fan
2) might also count as a con.
42402 publicly visible posts • joined 16 Jun 2014
"Funnily enough, the stuff we send abroad has to comply with US regs.... or it does'nt go
we have no say on what those regulations are, nor any vote on who gets to set the regulations in the first place, and yet we trade with the US very successfully
...
If the product goes into the EU (which it does), then it has to comply with EU rules,"
What you don't say is that whilst there was no say on the US regs we did have a say on the EU rules. Since last year we haven't.
The US market was your export market. The EU was your home market. Now the EU is an export market and your home market has shrunk to just the UK. If the UK deviates from the rules the EU makes then you have three sets of rules where previously you had two. If it doesn't then the home market rules are set by the EU with no UK input into making them. It's called "taking back control".
I'd be somewhat surprised if the outdated bits are still applied in practice. If you know what you're doing when you write this sort of stuff you might make references to "best current commercial practice" or state they're minimum requirements knowing that as time goes on the norms will change. Alternatively specify an ongoing process that can keep the specification up to date without it being in the main document. I worked on a job for some time where extra products kept getting added to the contract; the workflow involved data transfer by XML and while some stuff was necessarily dealt with at sales and management level the XML additions were organised at working level.
This has PHB interference written all over it and I'd be surprised if hadn't been left in the dust long ago. As I pointed out in another post, key management is ignored; if the folks who knew what they were doing felt that encryption had to be specified they'd surely have included it.
Long experience of project teams & the like is that you roll up at the first meeting, look round, spot one or two people and know that between you you'll be doing the work. Some will be problems and some dead weights. A few may be new but you'll come to categorise them as the project proceeds.
The sub-set doing the work should bear in mind another rule: it's easier to ask for forgiveness than to get permission, especially when it's up and working.
It's unlikely that they will diverge. No govt. is going to want to do that. Any rational govt. will understand that this is already the best of a bad job and no Brexiteer govt. is going to want to expose the hollowness of the whole thing. Meanwhile we've now got a boundary in the Irish Sea (imposed by a PM who professes to be unionist and promised such a thing would never happen) and over time the little problems will creep out; the fact that Scottish producers can't sell seed potatoes to Europe nor, it's reported, to N Ireland.
It illustrates at least two well-known principles: (a) there's [at least] one on every committee and (b) nobody gets round to updating the documentation.
It's not too difficult to visualise the sort of thing that must have happened. A working group is appointed and deals with all the techy bits around data representation with the actual communication being dealt with on a level of "Just email it, encrypted and signed". Then some pedant says "No, you need to specify that" so some poor soul gets the job of writing it up.
The draft of that addition goes back to the committee and some PHB pipes up with "Ooh, that sounds very complicated. Won't it cost a lot of money?". It gets explained that Outlook, Netscape or whatever he's using handles that already. "Well put that in, then." And so the document ends up with an explanatory paragraph that didn't need to be and shouldn't have been in there and which has aged to the point of ridicule. But, of course, nobody wants to revisit it to take it out; as the article indicates, when the documentation is an international agreement the inertia is a few orders of magnitude worse than what most of us experience in this respect.
As to levels of encryption maybe reality has already replaced that specified. Presumably keys will have expired and been reissued using later releases of PGP the S/W. Of course, as diplomats will have been involved there might have been undue influence of the US who don't like the rest of the world using encryption at all. And on the subject of keys - the document is, as far as I can make out, quite bereft of any mention as to how these will be managed. That's consistent with the committee considering that the whole communication issue was outside its scope.
Netscape Navigator, of course, lives on. It's now called Seamonkey. It's what I'm typing on right now.
"If Amazon wants to have an e-commerce platform, it can't sell on it itself."
I think this concept needs a but more thought. It's like saying you can't own a shop or even a market stall and sell stuff there.
Providing a 3rd party sales platform isn't in itself monopolistic because it has a rival, eBay.
Having its own product lines is not, in my, admittedly limited, experience, a problem providing it sells them under its own name. The one such product I've bought is far superior to the once-prestigiously branded article it replaced*.
Moving into areas such as grocery isn't monopolistic either - there are some big beasts there who've used their own resources to move into e-commerce on the one hand and into other product areas on the other.
In fact Amazon may well have got too big for comfort but it's difficult to pin down this part of it on sufficiently objective grounds to put up a plausible case for the prosecution.
* Why this should be is an interesting question in its own right. The famous brand got bought up. The predatory buyer can shove out crap and be able to sell it on the basis of the name. By the time they've trashed the brand image they'll have made their money back and a profit and go stalk another prey. Maintaining bought-in brand reputations isn't their business plan. Somebody like Amazon, trading through a single brand has an interest in maintaining that reputation.
Amazon has a number of more obviously separable chunks such as AWS and the video operation than separating 3rd party sellers from the main store and these could easily survive as independent operations. From a customer's PoV removable of the endless nagging about Prime would be an improvement: there's no way I'm going to sign up for a subscription for something I don't want so not having it constantly shoved in my face would most definitely be an improved user experience.
I've mentioned before the time, about 50 years ago, when a scintillation counter was delivered to QUB. About the same height as a typical rack but half as wide again and largely occupied by a complex sample changing mechanism. It arrived in a van without a tail-gate lift. It must have been loaded with a fork-lift but nobody advised we'd need one to unload it. It was eventually unboxed in the van, lowered onto its side and slid down a long plank. I don't think we'd worked out whether we could get it through this door and the narrow passage way behind it but it did just fit. https://www.google.co.uk/maps/@54.5858855,-5.9347162,3a,75y,165.71h,80.43t/data=!3m6!1e1!3m4!1st90JWAEKBeh2W1l4YPAH_w!2e0!7i16384!8i8192?hl=en
A cousin's new wireless HP printer had a set-up disk for his W10 laptop. It insisted in trying to set it up with a 10.x.y.z address even though the laptop itself was on 192.168.x.y. Fortunately it also had a USB connection so I could configure it via CUPS from an old Dell he had which ran Zorin (relatives ask for IT assistance, they likely end up running Linux).
"Zoom is a pretty good way to deliver healthcare"
Really?
Overkill in one sense: a telephone call is sufficient to discuss symptoms.
Insufficient if a physical examination is needed.
The gap between the two cases seems to me to be vanishingly small. In fact, the only effect I can see would be to rule out health case for those patients not equipped for it
"He commuted to work on a motorbike he never owed a car always had motorbikes."
As did my dad. Back in the '30s a driving licence was just a driving licence - no differentiation into classes so when those came it it just got renewed into all classes so whether you could drive a car or not you were licensed for one. I'm not sure if dad ever had to take a driving test to get the licence.
"The Wayback Machine?"
Erratic in coverage. All too often you find that only part of the site was archived. I just tried one old site which lapsed some time ago. A friend offered to take it over from the guy who didn't want to - or maybe couldn't - maintain it but the offer was declined. The domain is in the hands of a reseller and although the Wayback machine tells me unarchived pages are still available on the web they now resolve to the reseller's advert.
The document argues that China’s 2017 National Intelligence Law is a primary source of risk, as it “compels all PRC firms and entities to support, assist, and cooperate with the PRC intelligence services, creating a legal obligation for those entities to turn over data collected abroad and domestically to the PRC.”
That seems eerily familiar but some other country was mentioned, not China.
the "visitor flow" was poor
As far as I could make it it was arse about face. You walked past all the things done with the product of the Big Melt before you actually got to see it. And the flow of trying to get back to anywhere recognisable by following the signage when driving away from it was another nightmare.
I couldn't seen the point of the classical elements except to point to the educational background of the designers but the Water bit was fun.
"the actual business model doesn't work."
From the Wikipedia article: !In 2012, Red Hat became the first one-billion dollar open-source company, reaching US$1.13 billion in annual revenue during its fiscal year. Red Hat passed the $2 billion benchmark in 2015. As of February 2018 the company's annual revenue was nearly $3 billion."
I suppose the takeaway from that is that if you have a business model that doesn't work then fail big.
"I have changed between distro's more often than I want to count. "
That may be easier if you're predominantly a Unix/Linux user because then the similarities outweigh the differences. For a mostly Windows user it would probably be easier to move from Ubuntu to Debian than to something Red Hat based. Very likely Centos/RH users would take a move to Ubuntu in their stride although if I were in that position I'd probably think more in terms of Debian.