The Xcode installation asks you to close iTunes because of iTuneshelper and how iTunes will sync devices (including development devices) when they're plugged in. It makes sense that Xcode asks you to quit itunes (and kills ituneshelper too) to update files. It isn't ridiculous.
• asks user to perform task manually which is trivial to automate: `tell application iTunes to quit`. Apple even has sudden termination API that iTunes could use to make it safely killable most of the time.
• needs to quit iTunes in the first place. Why can't it take advantage of versioning of libraries and frameworks? Why can't it update files in place? (running application should see old version [inode] until it closes the file).
• and the usual ridicule: a music player is a critical piece of device sync and development infrastructure.
I'm doing some early research into starting a brewery or brewpub in a small town in Michigan. I'm hoping to bootstrap as much as possible, but I'm pretty sure I'm going to be taking on at least some kind of loan. Licenses in this area aren't bad. Visit your local City Hall and give your state's Liquor Control Commission (or equivalent) a call.
I do laundry about once a week, and it takes about 2 minutes to load and start the washer, and after an hour (or whenever you get back to it) another 2 minutes to load and start the dryer. After that, you can just get clean clothes out of the dryer instead of dresser drawers. My girlfriend doesn't like this life-optimization.
I've also found that turning off all push notifications of emails to my phone helps me ignore emails until I actually get to them. I pick a few times per day to go through them in batches and immediately take care of anything I can do quickly, and star or archive the rest, depending on whether I need to follow up or not. I do my last check at about 9pm.
I feel like a better approach for that sort of solution would be to use a hash-tag based (#) tagging system. English has so many tenses and people mis-spell things anyways that basing your search purely off of the text of the commit message is always going to be tricky. Anyways, the point of the commit message is that it be human readable, not machine readable.
Personally, I like clever commit messages. They remind me that the project was written by humans for humans.
This G thing has been getting out of hand for quite a while now. A friend was recently telling me how much better his new phone was because it is 4G. He said he didn't really know what that meant, but it was definitely faster than 3G.
Also, a coworker of mine refers to his company provided Nextel Blackberry as "half-G".
It's just a marketing term for marketing to people who don't care about link protocols or multiplexing strategies. The problem was originally started when 1xRTT and EDGE were branded as 3G. This should have never happened, but that's what happens when marketing drives your business instead of engineering.
Honestly, even EVDO isn't really a true 3G protocol, as voice and data are completely separate protocols. UMTS phones don't drop to a voice-only technology to make a call, they use the data signaling, and IP connectivity isn't lost during phone calls. However, the fact that CDMA folks decided to go with a less ambitious, but easier to deploy megabit+ broadband technology meant they were able to beat the GSM networks to the punch. Worse is better.
That being said, WiMAX and LTE are legitimate 4G technologies. They both step up to using OFDMA instead of CDMA, which gives them a much higher theoretical bandwidth ceiling. Yes, HSPA+ networks have been pushing into WiMAX's bandwidth territory by adding MIMO and 64QAM modulation, but that's pretty much the ceiling for HSPA. The only future it has is in multi-carrier or multi-tower arrangements, which don't increase the spectral efficiency and are pointless in dense urban areas.