The basic problem is that the permissions model is very leaky; there are lots of ways to work around it, by sending intents to other apps that have more permissions, by relying on certain OS services to call you in a more privileged way, by providing custom notifications that display on top of everything, and so on.
For instance, even if you don't request internet permissions, you can still open a URL, with whatever data you want to send encoded in the URL; and you can even do this in sneaky ways that the user can't detect if you're careful (only doing so when the screen is off, for instance, and redirecting to Google so they don't see anything odd when you turn the screen back on). And you can register a URL handler, that the page can redirect to, to communicate back to your app.
Actually a fair number of shipments by small companies and even Fedex have shipment numbers that total out to 10 or 11 digits which fits a fully dialed international number perfectly and will be highlighted by Android. So the feature is bad and good at the same time.
Source: I made and maintain a shipment tracking progam on Android.
> Some people like the Google toolbar. I don't use it personally (nor would I ever choose to), but that doesn't mean it doesn't hold value for other people.
So, if you don't like the Google toolbar, you simply don't install it in your browser.
With Apture, you don't get to choose. If you like it, it's only available on some websites. If you don't, you have to go through some adblock or privacy block rigamarole to prevent it (and other clones, like yours) from interfering with your ability to select text on the web.
It is a prime candidate for functionality that should be provided by the browser, not the website. Sure, it can be nice to do a mockup in JavaScript to demonstrate and experimenting with the functionality without patching your browser. But it shouldn't be something that random webmasters are enabling on a whim, because they think that their users just might like it. That's akin to bundling Google Toolbar with some random software that someone's downloading, just because you think that they might like it.
I keep on hearing those words with respect to brains. I do not think they mean what you think they mean.
Brains are not "hard wired" for much. They are really quite malleable and adaptable. They are affected by many things in the environment; experience, culture, training. The biggest differences between male and female children will come about from how they are raised, not innate differences. Once they hit puberty the hormonal differences will have more of an effect, though nothing that could be described as "hard wired", it's more a question of predisposition.
You state these things as if they are fact. I disagree. People are born with different strengths and weaknesses. They may have particular skill in certain areas.
If brains are just "general" "maleable" "matter", then why as a man am I attracted to women and not men? I certainly didn't "learn" that. I'm attracted to women, because my brain was hard wired like that.
I actually don't think people are born gay or born straight. I think there are biological factors in sexual orientation but these are hardly determinative. Instead most people are born somewhere along the bisexuality spectrum and end up defining themselves as gay or straight as a way of dealing with unacceptable sexual urges.
The fact is that if you look at male-male sexual relations in a place like Greece or Rome, the differences in structure and approach to gender and sex are markedly in contrast to how we approach things in our society today.
I personally think that one element of the argument that people are born gay, in the context of a culture which aggressively sells the idea that heterosexuality is normal, is to tell people, "you aren't born gay, are you?"
Edit: I could point people to longer write-ups I have done on this subject but the above I think is a fair summary of what cross-study and trans-historical comparisons have lead me to believe.
Sure, different people will have different strengths and weaknesses. But that's different than "hard-wired." You may have some natural talent or predisposition, or you may have some particular disability or difficulty with something. But most of those can be melded and shaped by your environment, your culture, your experiences, your hormones, practice and learning, your desires, and the like.
I've known several people who have transitioned between genders. Were they "hard-wired" the way you claim they are? One of them, who transitioned to being a man, took testosterone as part of the transition (and presumably still does). He reports that the testosterone was significant in changing some of his behaviors to being more masculine; when upset, he has a harder time crying than he did before. Now, is that what you would call "hard-wired"?
I don't pretend to know whether you are born gay, or if it's something environmental during your childhood, or whether it really is more flexible than some people like to admit. Surely there is a predisposition to be attracted to the opposite sex; but that doesn't meet the criteria I would use for "hard-wired."
"Hard-wired" says that something is absolute; immutable. It cannot be changed. There is a binary; you are either this way, or you are that way. And that's just not how people work; at least, behaviorally, for the vast majority of behaviors. Really, there are multitudes of different axes on which people's behavior differs; and while their sex might influence their behavior a bit, the results tend to be overlapping bell curves with slightly different averages, not two entirely different sets of behaviors.
The whole "women do this, men do that" or "hard wired" type of reasoning is an over-simplification, which is amplified culturally.
(sorry for the late followup, I didn't see this comment until just now)
I wonder why they decided to be so non-specific in this article. It would have been more clear to say "Users on XP will be upgraded to IE 8, users on Vista and 7 will be upgraded to IE 9 and later as new versions are released" or something of the sort. Instead, they spent a lot of time talking about why what they're doing is so great, and a lot less time talking about exactly what they are doing.
I really don't mind that sort of phrase when it's pointing out that the cutting-edge features that they are demonstrating, while they are on the standards track, currently work best in a particular browser.
On an actual production web page? Sure, that's awful. Blocking people on other browsers from viewing (like Apple did with their HTML5 showcase)? Yeah, that's bad. Demonstrating a technique that still requires vendor prefixes, and not applying all of the vendor prefixes that work? Well, that's just lazy.
But informing people that the effects you are demonstrating work best in a particular browser because the other browsers don't happen to implement those features yet, or aren't fully compatible yet, isn't bad. It's just preventing confusion for people who come there and don't see the given effect.
In order for web standards to progress, we need experimentation. We need early implementations, that test out the space, and we need designers who try out these implementations and see what you can do with them. And yeah, when that happens, they will be experimenting with features that aren't supported everywhere, and will create examples that only work on one or two browsers.
Complain when you see this in production. Complain when you see people recommending user agent sniffing. But for early stage experimentation? It's not a problem.
I'm torn. On the one hand, I strongly oppose SOPA, and I agree with most of the online protests I see of SOPA and PROTECT-IP.
On the other, Wikipedia prides itself on its neutrality; it is one of Wikipedia's selling points, that they (at least attempt, as much as a collaborative, anonymously edited encyclopedia can) to provide a neutral point of view, keep from giving undue weight to fringe viewpoints, don't allow themselves to be tempted into being non-neutral or appear non-neutral by offering advertising. Making a strong political statement that takes advantage of their popularity would move away from this neutral stance.
On the gripping hand, this is something that would impact Wikipedia directly. Wikipedia would instantly become much more liable for any problematic content posted by users. They would likely have to change their editing policies, add domain blacklists to avoid linking to verboten domains. Many sources of information that Wikipedia editors use and link to may be banned. SOPA is in direct opposition to the open and free dissemination of information that is Wikipedia's mission.
So, I don't really know. I wish there were a good answer here. But there really isn't.
It's simpler than that. Even the most neutral body will be very much pro its own existence. If Wikipedia views SOPA as an existential threat, it is not inconsistent to oppose it.
The problem with Apple's App Store rules is that it's their way or the highway. There is no way to grant your users more freedom than the App Store does.
This, coupled with the fact that you can't install apps other than from the App Store on an iPhone (without jailbreaking your phone or paying extra money to be a developer and building them yourself), is why I will never own an iPhone (at least until they fix those problems).
Except, it's implemented on top of TCP. So you still have the head-of-line blocking problem. In a real-time application like games, if some congestion causes a few packets to be dropped, you don't care about them any more (assuming your protocol gives absolute positions of everyone involved); but in TCP, they will be retransmitted, and later packets queued until it can catch up. As websockets are based on TCP, you can't avoid this. Even if you have a "fire and forget" message based layer built on top of TCP, the head-of-line blocking will still kill your performance, causing people with bad connections to get persistent lag rather than a few dropped frames.
That's true, but in practice networked games built on websockets are doing fine right now, and will until browsers get stable capabilities for more intensive 3D gaming (likely in around 2 years time). I guess I meant they won't be needed yet.
Well, I'm working on a web-based real-time multi-player game, and I'd say that UDP would be very welcome by me. When I'm on a good connection, TCP is fine and things work perfectly. But as soon as my connection becomes just a tiny bit unreliable and packets start dropping, it becomes completely unplayable, as TCP has to retransmit those dropped packets before any new packets are processed.
Since all we get is TCP right now though, you can take advantage of that at least and easily do things like send deltas instead of absolute positions, and even things that depend on reliable order of transmission (which you can't rely on if it were UDP), in order to reduce bandwidth use.
The basic problem is that the permissions model is very leaky; there are lots of ways to work around it, by sending intents to other apps that have more permissions, by relying on certain OS services to call you in a more privileged way, by providing custom notifications that display on top of everything, and so on.
For instance, even if you don't request internet permissions, you can still open a URL, with whatever data you want to send encoded in the URL; and you can even do this in sneaky ways that the user can't detect if you're careful (only doing so when the screen is off, for instance, and redirecting to Google so they don't see anything odd when you turn the screen back on). And you can register a URL handler, that the page can redirect to, to communicate back to your app.