Drat. That rules out my plans for an anti-gravity drive based on a magnetically bound pot of antimatter.
Now what am I going to do with it?
5385 publicly visible posts • joined 15 Mar 2007
Freedom of speech is not the same as having any rights to public amplification via the media.
So what gives someone the right to silence anyone?
Legal precedence. For example, if I found out your real name and address, employer, etc, and started posting rumours about you and $shock-story-de-jour it would put you and your families safety in jeopardy. Should my right to talk like an asshole trump your right to safety?
Very true, but most folks search using Google and buy using Amazon and just don't care.
The simple low-support aspect of a Chromebook is great for them, give them anything more complicated and they will make your job MUCH harder. These days I simply won't do Windows support for friends or family, as it is just so much pointless trouble. Linux is easier, but again, they still find creative ways to screw stuff up.
I did give a friend a Chromebook years ago for that reason. Eventually they broke it by standing on it with the power cable ferrite lump between keyboard and monitor. Doh! Worst thing was they told me "It was OK the last time I did that" FFS!
People didn't switch to cloud to save money, at least no one with any sense did.
How many did it with sense, or on the promises of some slippery salesman to the CFO?
The points you raise about backup/redundancy/etc are all very valid, but the UPS & redundant A/C side would be the data centres responsibility. While cloud providers promise a totally stress free and safe system, we still see them going down with outages or strange data losses from time to time. When it happens, take a ticket, you are 10,451th in line for support. And then we get to the locked-in aspect...
What this article raises should be considered - your costs might be much less keeping stuff on-premises, but of course that only works out well above a certain size of technical staff levels when you have your own folks to take care of it. There are other cases where cloud makes a lot of sense, for example rapid scalability.
But we do have no-execute options on memory segments, and other containment approaches such as AppArmour, but using them is just kind of hard so developers generally don't. As always, it comes down to the fastest/cheapest/easiest route. And so orifices are left gaping...
Power generation is largely out as the temperature difference is too small, and your usual heat engine's thermodynamic efficiency limit is based on the ratio of absolute temperatures so a 10-20K difference on 280K or so would lead to really low efficiency of extraction.
District heating, where you just want to take a chill off rooms in winter, etc, is another matter and only issue is the cost of infrastructure - i.e. pluming in homes.
50 years ago.
In the mean time most of the world has gone metric and ditched stupid old units with bizarre multipliers and units that are not constant across regions. What size of gallon are using today, Winchester, old English (Liz 1, or Anne), Irish, imperial, US, or US dry? Do you annotate which one is actually used?
True, the UK Brexit folks would like to bring them back, but that is even more stupid than retaining them for whatever legacy reasons.
"Earth fault" as in to-dirt? Can't happen here.
Here earth = ground = CPC (circuit protective conductor). Most UK installation are on TN earthing so a fault to earth is essentially close to a fault to neutral (=cold in USA parlance). To protect against contact with true Earth (as in some poor sod touching a live cable) we use RCD = GFCI as they (in the UK) are usually 30mA trip threshold (actual spec is 15-30mA).
I don't think ANYbody tests Interrupting Current on site. My sub-breakers are rated 22,000 Amps. That is a MAJOR arc-flash. Not a problem here because with my long line I can not pull even 1,000 Amps at my dooryard. But in Texas you can find four homes clustered within 20'(7m) of a 100KVA transformer, which is why they don't make 10,000A-interrupt breakers any more.
Nobody tests actual fault current intentionally, out side of approval laboratories that have controlled sources of many kA and a means to contain the usual explosion that follows!
Here in the UK we have less of an arc-flash risk in general due to a love of HRC fuses at the incoming point of most small-medium sized installations. They do a much better job of limiting fault energy that most MCCB/ACB style of breakers. In domestic UK it is unusual to see above 3kA fault currents, except in some cities where the LV grid is actually a grid, most LV networks here are deliberately smaller and isolated to keep fault results down. Our domestic panel = CU (consumer unit) is designed to be safe to 16kA fault current by the combination of the supply company's fuse (typically 60-100A) and the MCB used. Basically the fuse limits the peak current to that of something like 4-6kA equivalent even for underlying supplies of 16kA or a bit more.
Fuses are good! Cheap, reliable, with excellent fault energy limiting. But one-time, and usually need skilled replacement.
Of course electricians (proper ones, not DIY-Dave sort) have the equipment to measure the supply impedance, works by switching a load of a few amps on/off and correlating the voltage shift. If you try it on a cabin with a site cable feeding it you see the lights flicker during the test.
Such testing ought to be done so you know that (a) enough current will flow during an earth-fault the the protection will trip fast enough to avoid a shock risk and/or cable burning out, and (b) too much current won't flow beyond what the fuse/circuit breaker is rated to interrupt safely.
From a cited article:
However, the Samba team has moved active development of the project to the more strict GPLv3 license, which prevents Apple from realistically using the software commercially.
Given samba is a stand alone program, why is this an issue? Do Apple want to change it in some way and make it run only if signed and deny anyone from running an unsigned version?
"yes, we discussed it in the break room"
If it is important you make sure it is communicated to all and written down.
Also there are tools like a phone and video conferencing that let you talk to those on and off site as well.
but what happens when they need Susanne or Robert who are also 'working' from home?
Oh, good point! Maybe if someone could invent a gadget that allows you to speak to someone remotely?
Or maybe some sort of space-age computer system that would allow you to talk AND show moving pictures at the same time?
Gee, this could be a good market opportunity!
Has anyone actually produced an independent analysis of worker productivity remote/office to back this up?
I can see good reasons for being together as a team during certain aspects, but equally I can see that many jobs, especially software, can be done just as well, if not better, at one's own home with few distractions and less of one's life wasted commuting.
Sadly I have to agree with this from my own experience of otherwise sensible folks ending up as raving right-wing USA nutters, in spite of having no connecting to American issues it real life.
Yes, there are left-wing nutters as well, but it seems the right has a far bigger stake in this.
I was wondering the same, if this is specifically Apple, or part of some larger ban and it is just iPhone that gets the news headlines.
I can't see the Chinese being happy with Android either, given its Googly parents and less than impressive history of security and privacy. I think most likely is the Chinese spooks are doing exactly the same as USA/UK/EU/Aus spooks in telling the politicians that phones are just a bad thing to allow anywhere secret.
I would imagine most corporate systems have mostly Windows for common software plus the odd specialist application like CAD, and if managing a large network you would stick with Windows for servers, especially if doing something horrible like supporting Exchange.
Globally I expect most servers are Linux for web use though, and some other places are mostly Linux or maybe FreeBSD for the likes of TrueNAS storage systems. In fact probably most NAS are Linux or BSD based?
But really the reason that anyone would target Windows as #1 is most non-technical staff use it, and Office, so your first entry point in compromising a system is likely to follow from targeting those folks and their systems. We are mostly Linux, but don't imagine for a minute we won't be targeted at all, and of course the most common vulnerability is the person sitting at the keyboard...
The No. 1 flaw on the list was patched in November 2017, a code execution hole in Microsoft Office's Equation Editor we'd have hoped had been mostly mitigated by now.
What you omit to report is the "patch" breaks any ability to edit older documents that use the previous equation editor.
Yes, exactly. they DID NOT FIX the editor, they disabled it and told you to use the new editor, which cannot edit/migrate older equation objects in to a manner you can use.
The microVM abstraction is a great idea - for cases when host & guest are cooperative.
My most common use-case for a VM is running older OS for software support, or to build binaries for running on other old machines, and there the traditional hardware emulation is more or less a necessity as such OS never even contemplated virtualisation.