... should the surface reflect significantly more than a current roadway does. There's a non-trivial amount of glare that comes from existing road materials, the question is whether this surface has *more* reflection than that...
/. to python or node.js t...
Nnnnnnooooooooooooooooooooooooooooooooooooo (breathe) ooooooooooooooooooo!
He's missing the point. Everyone knows that the post office handles all your mail, but it's still not allowed to tell the police what you're receiving without a warrant. The existence of a record does not imply the availability of that record to law enforcement or the government.
This is essentially a distro, of android-x86. That would be like asking what licence Fedora was under... Different parts are under different licences.
Yep. Trolling by Betteridge effect
Welcome to 2008?
Not knowing the likelihoods is not the same as claiming that the likelihoods are equal.
If you present me with a biased coin that you've made, I don't know whether when we toss it, it is more likely to come up heads, or more likely to come up tails. Pointing that out doesn't mean that I think they're both equally likely, just that I have no way of knowing at this stage which is more likely. Notable points:
1. There is a correct answer.
2. You know what it is.
3. I don't know what it is.
4. I don't believe that they're equally likely, but I can't tell which is more likely.
Not particularly - then the hash becomes the new password. You'd need a client side hash with a nonce, and even then, the server needs a way to be able to validate the client-generated hash without storing the password in plaintext.
And the Australian allocation is half of the US band: 915MHz to 928MHz as per http://www.acma.gov.au/Industr...
(The US 900MHz ISM band is 902 to 928 MHz).
But similarly, you haven't heard the average person talking about wanting native apps either.
Developers and tech bloggers haven't realised that they need to balance conflicting desires (universal availability and version uniformity vs offline access and access to local hardware/services/data) which would induce preferences either way. What you are seeing is the tech community noticing the features they are missing, building them, and throwing away the features they already have in the process, then repeating again in the other direction.
The average person has no idea about any of this, and doesn't care as long as they can still send selfies and cat emojis to their friends. If a native app allows them to do it, they will use that; if a web app does, then that's where they will go. As long as they can click an icon and send the picture, it's good enough for them.
What is the difference between "business rules that need to be validated and checked" and "sanitize your inputs"?
(Hint: "this field should not contain semicolons" is just as much a sanity check/validation as "this field contains a latitude entry and thus should be between -90 and 90".)
Who said anything about databases?
You need to sanitize the inputs before you:
I don't care about your fucking database and your fucking parametrized statements, you still need to verify that your inputs are sane.