I'd guess that on average, men work more hours per year than women with the same jobs, because women tend to give birth and take care of children more than men.
I can't help but wonder if this is significantly influenced by an imbalance in compensation.
When my daughter was born, my wife and I decided that one of us would stay home, and income was certainly a large factor in determining that she would be the one to stay home. If our incomes had been reversed, then I would have become a stay-at-home dad.
The way you frame it is a catch-22 but data shows that when matched for age, marital status, and children single women with no children make more money than their male counterpart.
As soon as a man becomes married this switches. A man is more likely to take on extra hours/responsibilities and a woman is more likely to work part-time at this point. It's the over-time and hazard pay that is associated with the wage gap. A person working 80 hours per week should not have the same hourly-wage as someone working 30 hours per week regardless of gender.
Marco's "what will be different in 6 months?" question gave me a chuckle when you consider that native development for the iPhone is only about 3.5 years old and the rapid pace of change in the industry.
Anyway, Schmidt enumerated some differences:
- he thinks the software (ICS) has caught up to iOS
- Google has made it a core objective to get all the hardware vendors on ICS
- the Android Market has improved and now offers carrier billing
- volume favors Android
I don't know if he's right, but it's certainly a reasonable argument and not at all threatening or arrogant.
To me, Marco reads something nefarious or coercive into the "whether you like it or not" phrase which I don't think was intended.
Not to mention ICS unifying "phone" and "tablet" apps and the growing impact of hybrid devices like the Samsung Galaxy Note. The sooner people realize that the right way to do an Android UI is to have a flexible framework that scales from from a 2.5 inch screen to a 10.1 inch screen with varying pixel densities, the better.
"""Marco's "what will be different in 6 months?" question gave me a chuckle when you consider that native development for the iPhone is only about 3.5 years old and the rapid pace of change in the industry."""
I don't see any disruptive forces to have emerged those 3.5 years. The iPhone retains the lion's share of smartphone profits, and still is where the lion's share of mobile app profits are made. Trending upwards. Android expanded mostly in the low margin, bottom of the barrel, market category, and that's why they have a problem with apps.
Do you see anything TODAY that would challenge that in 6 months, or do you believe that something will magically emerge in, say, 3 months to do it?
All this "rapid pace" of the last 3.5 years is because a reaction to the iPhone, not something inherent in the industry.
The 10 years preceding the iPhone the smartphone industry was boring, with very slow evolution, and marginal differences between models. I know because I was there, using some monstrosities of the era (by Nokia, Sony, etc) and hoping someone would come and build a better f&%^n phone.
You are forgetting about existing phones upgrading. Admittedly, it can be a long process for the hardware vendors to certify ICS for their phones, but 6 months is probably a reasonable time frame.
One thing that has changed about the relationship between Google and the hardware vendors is that Google now has it as a core objective to get the vendors onto the latest platform. In the past, I don't think that it was a high priority on Google's part.
You're currently downvoted, but you're correct. Apps targetting older sdks will need to opt-in to make use of the acceleration, even on ICS. But it's an easy switch to flip, assuming it doesn't cause visual glitches, which it can in some cases.
Of course, they would have made it a default if it didn't have some incompatibilities; and looking into it a little more deeply, it does look like there may be:
The opt-in is basically saying, that either recommended or minimum OS version for your app is Ice Cream Sandwich. You do not switch the acceleration on or off, you say in the manifest, that you are aware of the platform.
I think hasanove is talking about destroyallsoftware.com, which is a pay site, but it's hard to tell from the landing page.
I also think it's the response (i.e., railscasts.com/pro) that is being called awesome in the root comment, even though the wording is somewhat ambiguous.
Hi, Laurent. I don't use CCW much, though I do have it installed. Mostly I hack Clojure in Emacs.
Nevertheless, I sent a few bucks your way because I think it's a great thing to be able to introduce Java developers to Clojure via Eclipse. Your work helps to build the community, and I appreciate it for that reason.
One of the things that Reto Meier talked about at Google I/O this year is building apps that are "Psychic," e.g., using things like Contacts on the phone to make the user experience less painful. However, he cautioned against being too psychic because it might make users uneasy about what else is being accessed.
One of the things I like about the Facebook Android app (and by extension any Android app) is that you can go to the settings and see what permissions you granted the app when you installed it. In contrast, you can't tell whether an iOS app can access your contacts list.
Given the recent history of Facebook with respect to privacy, I'm not surprised that this bit of software magic was considered by the user base as something nefarious.
> However, he cautioned against being too psychic because it might make users uneasy about what else is being accessed.
This is a theme I've come up against before. I worked for a company that did e-billing. When you signed up, it would go through the list of bills it was pretty sure were yours (because the billers would submit them, and it would match them against your profile information), display those, and then a list of bills that you PROBABLY had (companies that had a monopoly in your area, bills from companies that people LIKE you had, bills most people get, etc.) and display those under a different heading.
People FREAKED OUT. They'd call and wonder HOW THE HELL DO YOU KNOW WHAT BILLS I HAVE!?, in no uncertain terms.
Eventually, we had to "mix them up" and put ALL the bills into one big display, including bills that we were pretty certain you DIDN'T have (like Florida utilities for a Nebraska customer), just to give the customer the feeling that we weren't THAT psychic.
I don't understand why anyone would call the XOOM heavy in comparison to the iPad. The comparisons I have seen list them both at 730g.
I have them both, and I would say that the XOOM is more comfortable to hold. The two big factors are the texture of the back and the fact that I so often hold them in portrait mode. The widescreen form factor of the XOOM makes it easier to handle in portrait mode.
I love my iPad, but I think memory is a pretty big deal, especially if you want to do real multitasking. The numbers might not matter to the average consumer, but the experience will.
Open up several tabs in your browser and look at the memory that's being consumed, then tell me you won't care about 256MB vs 1GB of memory on a tablet that most people are going to use to surf the internet.
Not having to constantly reload pages was probably the most eye-opening thing for me using the XOOM (tabbed) browser versus the Browser in my original iPad.
He's recommending to read/watch SICP and do the examples, which are in Scheme. I think it's good advice to have a Scheme REPL to follow along so that you don't have to worry about the additional overhead of translating to Clojure.
This would actually be an interesting way to learn Clojure: Follow SICP, do the examples in Scheme/Racket and immediately after that the same example in Clojure (the differences should not be abysmal).
At some point though, as Scheme and Clojure diverge, this method would start to become less useful. But at that point, I would argue, you already know enough to take off in Clojure.
I can't help but wonder if this is significantly influenced by an imbalance in compensation.
When my daughter was born, my wife and I decided that one of us would stay home, and income was certainly a large factor in determining that she would be the one to stay home. If our incomes had been reversed, then I would have become a stay-at-home dad.