Or arrives with a small trolley, attempts to manoeuvre it so it's parked over the basket shelf and gets it wedged because the basket shelf is about an inch too high up.
Typical joined-up thinking there.
41 publicly visible posts • joined 11 Jan 2016
In the UK I believe that to count as 'being at work' you have to be available and willing to do work.
Whether your employer has anything for you to do or not is their problem.
Reading a book is therefore fine, as long as there's nothing you should be doing and you can put it down if some work does turn up.
It's increasingly the case that applications don't have installers on Windows, and so they don't have uninstallers either. This is because apps like Steam etc.in the simplest case just dump a pile of files into a folder and expect it to work.
If those apps need registry entries then they will add them when they are first run.
There is no uninstaller, and so no way to then later remove them.
looks like the AI has determined that if it flails about at random intervals with the welder going full whack it keeps the meatsacks away.
No operator has made any settings changes for a while, so it seems to be a very stable and hence optimal behaviour.
...because even the threat of possible competition is causing them to reduce their rates.
Therefore, they must have been earning excess monopoly profits up to this point.
If it genuinely was the cost of doing business they couldn't make these cuts.
Ternary is a very neat and easy way to make something const.
int directionMultiplier;
if (goUp)
{
directionMultiplier = 1;
}
else
{
directionMultiplier = -1;
}
... and now directionMultiplier can be changed without warning later on (leaks non-constness)
vs
const int directionMultiplier = ( goUp ? 1 : -1 );
... and now directionMultiplier will not change later on.
You'll also notice it's handy for books because it takes up less space.
No, you have just opened the gate from the walled orchard into the walled garden.
Apple still has veto permission on what you can install by what it allows into the app store.
Apple's great at selling the image of thinking outside the box, but all they do is provide a slightly bigger box. And then tape it shut.
Wrong approach - ask them to switch it off, unplug it, blow on the plug, then plug it back in and switch on in case 'there's a loose wire' or 'sometimes that helps' or 'there's dust in the connections'.
Then they can notice that it's not switched on and fix it without looking like a right numpty.
Nobody is going to notice if the AI gets it right.
They certainly will when it gets it wrong.
There is no safe false matching rate and no matter how hard you try, your system is going to end up making visibly racist/sexist decisions.
Perhaps people should take this into account when deploying an AI system.
A system that makes obvious, but stupid decisions is going to get less flak than one that makes opaque but mostly correct ones.
What the money is used for is irrelevant. Apple uses its monopoly control over the store to force developers to use its payment system. Other payment systems could work fine and cost less, as Epic demonstrated, but you aren't allowed to use them.
This is anti-competitive, but I don't think that's even in dispute.
The dispute is whether Apple's control over its store constitutes a monopoly in 'the market'. Apple will argue that 'the market' is all mobile apps, so because Google and Android exist they aren't a monopoly. Because they aren't a monopoly they can do what they like in their store.
Epic will argue that 'the market' is iOS apps, so Apple are a monopoly and so can't do what they like in their store.
Google is in a similar boat, but has a much stronger claim to not be a monopoly because alternative Android app stores (and alternative payment methods) actually exist.
Yup. It took a wrong turn with templates, and most of the changes since have been trying to patch up the resulting mess.
And the STL is a nice idea but frequently a pain in the arse to use.
You can't debug it, due to second-class compiler and debugger support.
Minor syntax errors take dozens of lines of garbage to basically say 'template problem'.
Debuggers give you cryptic structures to navigate (because STL is a library, not a language feature, so it gives you implementation detail you really don't care about).
Oh, and the syntax of the STL produces barely readable code. eg. the standard idiom for checking if a container contains something reads as 'if, between the start and end items of the container you don't find the not found item'.
cf:
if ( std::find(vector.begin(), vector.end(), item) != vector.end() ) // Actual STL
vs
if (vector.contains(item)) // What readable code would look like
Sounds like a bad idea to turn OFF the self driving when there isn't anyone holding the wheel.
Turning it ON, with some kind of alarm would be a better option.
Anyway, this is all bass-ackwards.
If this was about safety, the human should have to drive all the time with the Autopilot kicking in only if they do something blatantly stupid (with the ability to do a conscious override, a la stability control).