That operation also needs to be async itself, and ultimately it needs to be implemented as running on a separate execution queue.
Yes, but this is the relatively easy bit. It's writing comprehensible code around and about that underlying async operation that is the hard bit.
Ultimately, `async` and `await` still are nothing but sugar over the Tasks API.
The tone here implies that sugar is not an important thing in programming languages. These keywords do a great deal for you, under the bonnet. Everything is 'sugar over the assembly language API'.
The real problem is that it presupposes thought-crime.
The problem with that is that it's hysterical bullshit, and implies that people will be prosecuted for thoughts. This is a tool for helping to target effort in the screening process.
To be fair, the article itself was guilty of being nonsense first. Mentioning 'ethnicity' as an input to the system was the give-away. Even if true, this would never be admitted by whoever was developing the system in question. When I read that, the red flag went up, and I assumed the entire article was untrustworthy. But then, I wasn't on the lookout for sensational stuff to get worked up about.
> The point isn't that the keyboard is bad, the point is that the keyboard is excruciatingly bad.
You're talking about a device with a D-pad, and no touch screen. That's how keyboards work on such devices. It being bad isn't unexpected or noteworthy.
No sarcasm. I have read good books (I think), but am pretty sure that they didn't modify my personality. Normally they result in a couple of days of thinking "wow, that was a good book".
Don't worry, I'm not going to get all Christina Aguilera on your ass. Anyway, I do admire your ambition at attempting something a little different from the 'guys chatting' norm.
Changes in these traits ... were larger in magnitude than changes typically observed in healthy adults over decades of life experiences, the scientists say.
Clearly most people don't read good books, or scientists would have seen evidence of their radical personality-changing effect.
I tried this podcast once - found it embarassingly pretentious, with terrible musical interludes set too high in the mix. Conery's speaking style really rubbed me up the wrong way. But I'll maybe give it another go. Maybe he's got it under control since then.
Sorry. I've read your comment a couple of times and am unable to make any sense of it. Win32 is a (dated, clunky) API for writing GUIs (in part). "OS-layer" is babble in this context.
And yeah, i would stop signing your posts - it comes across as conceited somehow; like each comment is a big deal.
Well, I guess my digi-wallet asking me if I want to order groceries is slightly less weird than my internet-fridge going ahead and doing it without asking.
Still, I'm not convinced that it makes sense for my 'wallet' to be doing this.
Have you tried the app No I haven't - I've just used the 'standard' Android barcode scanner. So now I feel a bit sheepish given that I may have over-egged the pudding with that little scenario!
I've used internet supermarket shopping in the past, when I didn't own a car. It was reasonably good, and you paid £5 for delivery within a 2 hour window. You would tend to sometimes accidentally buy a weird size of some item though.
And let me explain how Barcode Scanner (or something like it) combined with Google Wallet will make my life as a consumer more productive
Yep, this will really speed things up.
Instead of scanning items on the way out, (i.e. "beep...beep...beep...beep...beep") people will scan as they shop "okay... just line up the cameraaaa... hmm it's not seeing it, turn the phone a bit... oh i beg your pardon hang on [moves out of the way of another shopper who also wants a can of baked beans]... [phone grabs barcode]... ah finally... beep." - one can of baked beans purchased.
Can't wait!
Also, given how fragile self-scanning checkouts are - presumably calibrated to prevent shoplifting - how will scanning stuff yourself and then walking out with it be acceptable to supermarkets?
I remember Google having reported various problems with their app store in the past, so the accusation is not valid, at least with respect to what we're discussing here.
Yes, but this is the relatively easy bit. It's writing comprehensible code around and about that underlying async operation that is the hard bit.
Ultimately, `async` and `await` still are nothing but sugar over the Tasks API.
The tone here implies that sugar is not an important thing in programming languages. These keywords do a great deal for you, under the bonnet. Everything is 'sugar over the assembly language API'.