Can we just drop the "mobile" and talk about dynamic layouts instead.
What you're talking about is called a responsive layout, and it's the current best practice for mobile support. It involves using CSS media queries to adjust the page layout based on the size of the display.
(And the Google algorithm does detect responsive layouts and consider them mobile friendly.)
... and if you told me you're using your phone to access the site, I'd get a puzzled look and say "but why?".
Because the mobile device was the nearest available thing capable of browsing the web at the time I wanted to look at the content.
The number of cases where there is a legitimate reason to not support mobile is very small.
Or why when setting up an email account does the mail app send the domain name you enter to apple?
I don't know for sure, but when you set up an email account, based on the address you supply, the Mac does try to auto configure stuff for a wide range of popular email services. I'm guessing it's probably sending off the address to search for that auto configuration information.
This does enable precisely the parametric queries you're talking about.
No, it's more like they were enforcing parametrised queries on top of an API that allows non-parametrised queries.
Considering that the API is to help protect against SQL injection though, it's probably fair to say that version 6 is affected by other issues.
Not really. The API makes it easier for developers to avoid SQL injection vulns. That doesn't mean that code not using it has SQL vulns.
I've seen no mention of whether or not Drupal 6.x is vulnerable; are they?
No, it won't be affected, as the API involved was introduced in Drupal 7.
Well, I've done both of those, and the webpage option is far, far easier.
But people always want you to build an app, because apps are cool and websites are old hat.
If you have 100 hours available for testing, you can use static analysis to find 90% of the bugs and spend the rest of your time on the 10% that require deeper insight. Or you can waste 90% of your time being a human compiler, manually cross-checking symbols. Which is going to result in more reliable software?
That assumes that:
And there are a lot of reasons to believe that neither of those are true.
Yes, as was posted just above: Don't talk to police
Or, to summarise, you are not helping the police catch a criminal. You are helping the police convict you of a crime. Whether or not you actually committed the crime is irrelevant.
I thought it was a simple key-value data store.
Not really. The term NoSQL is used to describe a whole bunch of very different models for storing data, each of which has its own pros and cons.
The Left has become fascist in the name of tolerance. Tolerance will be imposed and all who stand in the way will put against the wall.
Yeah, I mean on the one hand we have people who wish to use the power of the state to deny the recognition of relationships of a minority group because it doesn't fit with their own view of the world, and on the other we have people refusing to use a company's product because they disagree with the politics of the CEO.
OKCupid are clearly the fascists here...
I am sure the three other people who use Netbeans feel the same way...
I'm sure they do, too, given how much better it is than Eclipse...
So, from that I see that you might not need JQuery if everyone is using an up-to-date version of IE (or something that's not IE). Good luck with that.
Why do the worst technologies that are just barely able to solve the problem always make it? Is the developer community collectively really this stupid? I fear it is...
Because the people who spend their time worrying about which is the theoretically superior solution rarely come up with a practically useful solution.
I wish you humans would leave me alone.
