Re: If you are infectious - stay away from work
Most civilized countries would require sick people to stay at home so they didn't spread any infectious deseases unnecesarilly.
FTFY.
1666 publicly visible posts • joined 20 Mar 2011
To readers of a certain generation, this description will be all too familiar: they are styled like games arcade machines.
It's a marketing thing ... when you've bought more than anyone else you get the high score and can see your chosen 3-letter moniker displayed in lights above the till!
Oh, yeah ... infantile.
Many organisations spent a lot of time and money deleting Solitaire from Windows 95 not realising what a fantastic tool it was to help newbies learn mouse skills.
I vaguely recall hearing that the games in Windows -- it may only have been Minesweeper -- were specially commissioned at Bill Gates's request for that very purpose.
Beer shouldn't be too cold, otherwise you can't taste it. It shouldn't be warm either, of course. As you say, chilled to cellar temperature is ideal.
But you hit the nail on the head with the (American version of) Budweiser remark -- some so-called beers should be served cold, otherwise you can taste them.
The Czech stuff is different.
I'd never thought of volcanic disposal before. You sir are a genius! I salute your perpicacity!
The trouble with volcanoes is that they tend to spit stuff out, up into the air, all over the place.
It's called an "eruption", from a Latin word meaning "burst forth" ... which -- call me picky -- doesn't sound quite like the sort of controlled disposal technique that the nuclear industry is seeking ...
In 1996, Apple Computer bought NeXT for $429 million. On paper it was far too much for what was essentially a failing software company.
I'd have said NeXT was as much a hardware company as Apple.
Tim Berners-Lee's NeXT cube is on display at the Science Museum in London, I saw it last week, I'd never realized how big that cube was.
A work friend of mine had a pony and trap and she and her husband frequently woke up in their stable having been taken 5 miles home from an absolutely cracking pub by the pony.
Which nicely demonstrates that the AI in a Tesla, or similar, is dumber than a pony.
It's nice to have some sort of scale for these things ...
Retirement plans now consisting of having multiple TalkTalk lines installed in a shed.
I hope you don't end up finding that all those TalkTalk lines terminate at the same exchange cabinet, connected to the same backhaul ... which has just failed!
I'd go for one BT line, one TalkTalk, one Virgin fibre, and one 4G celluar from whichever network had the best signal in the area ... that would give a bit more redundancy ...
PS: I also recall the times when HDD's were supplied with front bezels and brackets so that once fitted, everyone could see that YOUR PC had a HDD installed, as opposed to all the other dweebs who had maybe one or even two 5.25" floppy drives.
Nice idea, but perhaps a but old-wifey in itself. You don't think that the reason for HDDs being fitted in a front-facing bay with a bezel might be that PCs only had front-facing bays originally intended for floppy disk drives, so that was the only place they could go?
... and, of course, the bezel is the mounting point for the drive access LED, as there wasn't one on the front of the box, and there's nowhere else for it to go.
I seem to recall that only real reliability problems with 5.25" disks occurred when reading a 360k floppy on a 1.2MB drive. Smaller heads vs larger track sizes.
The problems occurred when trying to read such a disk on a 40-track drive after it had been written on both a 40-track and an 80-track drive. The disk's oxide coating would have a wide track written on the 40-track drive with a narrower track written over it by the 80-track drive. This could be read without a problem on an 80-track drive but a 40-track drive would read both the old and new tracks together and get confused.
Moving such a disk between two different 80-track drives could also cause problems if either or both drives were a bit out of alignment ... but when drives start to lose their alignment you're going to get problems sooner or later whatever disk you use.
[5.25" disks] were physically less robust ...
They were still pretty tough, though.
I recall preparing a software update for a rather specialized bit of kit, which (somewhere down the line) was mailed to the customer. The secretary given the job of sending it out folded it in half and put in in an envelope and put it in the post.
The customer returned it, unsurprisingly, and the guy responsible for the product asked me to make another copy of the upgrade. I was a bit busy, and suggested that he try to diskcopy the folded disk just in case it turned out to be readable despite the fold.
To my surprise and his utter astonishment it copied perfectly!
... we soon discovered that while the floppies stated that they were single sided and the drives were only single side that careful use of a hole punch to add the required holes in the card cover for the rotational position detector and the write enable notch allowed us to double the amount of stroage available by putting the floppy in "upside down" so the drive used the reverse side.
You could even buy a "flippy disk kit" to help punch the hole and the notch in the right place. I may still have a copy of Byte with an advert for one ...
Very few of the secretaries had use the tabulator on the old manual typewriters,...
I rather doubt that ... anyone who'd done a typing course would have been trained to use the mechanical tabulator of a manual typewriter and had to demonstrate that use to get a certificate.
I can certainly believe that the TAB functions of early wordprocessors were not explained well enough (or at all) to secretaries converting from manual typewriters to electronic systems, and I can certainly believe that the electronic analogues of the manual tabulator settings were not sufficiently like them for their use to be obvious.
Anyway, that's all in the past. Now we just type text into a table and set the column widths later, once we know how wide they need to be. Tabulators belong in the manual age.
Funniest thing is, if they only wrote
#define SAFE_LIBRARY_memcpy(dest, destMax, src, count) memcpy(dest, src, (destMax) < (count) ? (destMax) : (count))
Then they'd be at least immune to piss-poor stack overflow attacks, even if using plain libc.
Well, no ... Even if the codebase has been tested as it stands (which may be hopelessly optimistic) the values supplied for destMax in the calls have not been tested and may be meaningless. You still need at the very least to manually sanity-check the destMax value passed in every call, and then retest the whole codebase with the new macro.
... and that assumes that the code won't misbehave because you've truncated the result of a copy operation.
I think that " Scotland/Wales want increased powers locally" must count as the understatement of the year. They want, and will get, full independence and then rejoin the EU, where they will have a lot more influence than they do in the UK.
Methinks they might find it hard to get readmitted to the EU ... other nations (such as Spain) are terrified that their own regions (such as Catalonia) will seek independence from the parent country if they think they will subsequently be allowed to rejoin the EU, and will veto any such application.
Security on Android is such a sh*tshow that I often wonder if the platform was designed specifically to facilitate such.
Security on pretty-much everything is bad, because most people don't understand the issues so and won't spend the time and money necessary to address them.
I'd agree that Security is worse on Android than on many other platforms -- but that's not because Android has noticeably more bugs or exploits, it's because many Android users are unable to get updates for their devices. Even when Google have fixed a problem the update won't necessarily be made available in a timely fashion (or at all!) on the devices people are using, especially devices running older versions of Android (such as KitKat, as cited in the article).
I'm feeling more smug than ever about my decision to install 8.1. Seriously, it's probably the last "good" Windows version.
For some value of "good".
Generally, Windows has slid downhill from the lofty pinnacle of acceptability that was Windows 2000 towards the pit of ordure that is Windows 10. Windows 7 remains a rocky outcrop on the hillside that has not yet been buried under the encroaching glacier of "end of support", with Windows 8.1 visible as a little ridge between the depression of Windows 8 and the plunge into the festering chasm beyond.
a) who is stupid enough to sell a stick they've used?
It beggars belief, doesn't it?
I rather assumed that any USB stick sold secondhand would be stolen (and that the original owner would not have been in a position to erase it before sale) ... but I suppose some may cone from house clearances, and the like.
"It doesn't matter how durable a device is if the user chucks it in a draw"
Dave, what's a "draw"?
[snip]
I presume you mean 'drawer'?
Methinks he must mean a raffle -- or "prize draw" as they're sometimes known -- probably for charity. There's no other way to make sense of what's written.
It'd be a good way to get rid of kit that someone else might value ...
I recall that a friend brought a copy to a party, shortly after it was released, and helpfully read out informative passages for our education and amusement. I can still hear him drunkenly declaim:
Fallout is invisible. If you cannot see anything you may be suffering from fallout!
If we can just break through the idea of having a unique image per arm device and develop a standard "BIOS" for arm, then we might finally get away from Intel.
We have UEFI, which is supposed to be a 'standard "BIOS"' for everything. One of the big drivers behind it was (ironically enough) that Intel wanted a single "BIOS" (and single adapter board ROM images using interpreted code) for both x86 and Itanium, and it can certainly support ARM as well.
UEFI is not known for being clean or simple, and it's certainly not everyone's cup of tea, but it does exist and it is increasingly widely used. It's an off-the-shelf solution that can, in principle, support any processor family.
... so let's not pretend that there's no applicable solution for ARM.
Turned out that the pitchblende sample was WAY more radioactive than the carefully stored and licensed radioactive sources were!
We had two "official" radioactive sources at school. IIRC one was Cobalt 60 (beta and gamma radiation source) and the the other Americium 241 (alpha source). They were tiny samples -- around 5 microcuries each, I think -- enclosed in little nickel cups with convenient handles that enabled them to be picked up with lab tweezers, and each kept in its own special lead-lined wooden box. Each produced a modest ticking from the geiger counter when the tube was held up to the sample.
The physics master also had an old clock dial with luminous markings painted (we assumed) with a radium sulphide/zinc sulphide paint. As that wasn't officially a radioactive source it was kept in a drawer with the blackboard cleaner. That clock face drove the geiger counter frantic when the detector was anywhere near it.
Then again, so did my watch!
That depends on which acid you are using, calcium carbonate reacts to give a coating of calcium sulphate which inhibits further reaction when using sulphuric acid. Use aqua regia as it gets the job of getting rid of the skeleton done.
Calcium Chloride is soluble, and won't form a coating, so hydrochloric acid will do the job.
You cartainly don't want to use aqua regia if you're hoping to sell any gold fillings, afterwards ...
I have taken quite a few YouGov surveys where there is no correct answer to the question.
These surveys are constructed to provide "feedback" that supports the conclusion that is desired by the company that commissions the survey. They're not trying to discover what people think, they're trying to demonstrate that people want/like a specific thing.
As such, there is always a "correct" answer -- for a very specific definition of "correct" that has no basis in reality -- but there is never any entirely "incorrect" answer that the responders might inconveniently select as an alternative to the desired fiction.
It's meant to be like that.
"There's no reason to know [it's using blockchain]," he said. "Why do you care? It should be that you use an application and it works."
One reason to want to know whether a system is using blockchain is that one might wish to avoid systems built on hype and snake-oil, and one might consider the use of blockchain to be an indicator of just such a system.
Trying new things is called "innovation". Sometimes it works, a lot of the time it doesn't (Microsoft seems especially good at this side of the equation), but without it, we wither and die.
True ... but probably unimportant.
.Net was conceived as Java with a Redmondian accent, back when Sun Micrososytems were getting shirty with Microsoft for putting non-portable things in to Java. If there was innovation then it was Sun's not Microsoft's.
Actually, though, I'm not sure there was innovation, as the only "new" thing in Java was that it used an interpreted intermediate code that could be run on any platform -- and, in particular, in a browser ... and the only part of that that was new was targeting the browser, because UCSD did the intermediate code for portability thing with their Pascal P-System 20 years earlier.
Just think what good tooling for C++ we might have today if Microsoft had taken all the resources they threw at .Net and used them to improve the C++ development environment instead! Just think of the fancy debuggers, profilers, refactoring editors, and all the other stuff they might have been able to develop if they hadn't wasted their effort on an unnecessary runtime environment that nobody needed.
Microsoft ended up buying a slice of Sun, anyway, so the spat over Java went away. They didn't need to invent C-Hash and port all their huge codebase of Java to it ... they could have got on with something that produces material benefits for their users, instead!
I wonder if they have Huawei's permission to use their trademark on that banner?
Did you read the part of the article that says that HCSEC is administratively part of Huawei?
I stopped using TomTom after my device with lifetime maps stopped functioning because the maps got too big, and the response from TomTom support was basically "sucks to be you, buy a new device" and they refused to re-section the maps to fit... so "lifetime" ended up being about 11 months.
That is pretty disgraceful. My TomTom did NOT have lifetime maps, so I wasn't quite so shocked as you must have been when they told me, recently, that it was never going to be updated again because the maps had got too big. I just thought "That's why I've been using an SD card instead of the internal storage for the last several years -- I thought that's why they made these things expandable?"
Now I realize that they may have been trying to make me upgrade to one that could count more than 1k weeks, without admitting the laxity of their programming. Time will tell ...
Libre Office doesn't work for anything non-trivial. I wish it DID. But it doesn't.
What's the factoid? 90% of Office users only ever use 10% of the features?
LibeOffice works pretty well for most people, just about all of the time.
Or they want off the upgrade treadmill. Microsoft's traditional model only worked if customers needed to routinely update to the latest version, and so pay for it - but is that still true? Look how many years it took them to drive customers off of XP, and Windows Seven is still in common usage.
There's a piece of wisdom from the Ancients that says: If you want your users to upgrade from version X of something to version X+1, you should try to ensure that Version X+1 is at least as good as version X, that the upgrade breaks nothing, and that using version X+1 will not require re-learning the user interface.
Clever chaps those Ancients.
If version X+1 is widely perceived to be a cartload of turds the users will stick with version X.
Had Vista not been a resource hog requiring a substantial hardware upgrade to equal the speed of XP it wouldn't have been the dismal failure that it was. Had Windows 8 kept the UI of Windows 7 people wouldn't have seen it as something strange and incomprehensible and to be avoided.
Microsoft have only themselves to blame.