You don't have to agree, but don't poo-poo his desire for a unified, simple application purchasing experience in his OS of choice. That's a customer talking about what they want out of a product.
110 karma · joined February 11, 2011
You don't have to agree, but don't poo-poo his desire for a unified, simple application purchasing experience in his OS of choice. That's a customer talking about what they want out of a product.
If it's a test update, why is anyone who doesn't work for a carrier and/or Microsoft aware of the problem? If real live customers are having issues, that's not testing, that's screwed up deployment. It doesn't matter how minor the update is.
And this isn't a technical problem; it's a process and culture problem. MS almost certainly has the technical and financial resources to have prevented this. The fact that they didn't points to an utterly dysfunctional company. Getting out of a market that they're rather obviously too hidebound or screwed up to compete in, is definitely a solution.
And thanks again for the continued cowardice.
Is it because your post is a bunch of poorly conceived bullshit? Is it because you don't really give any time to consider the intent of what's being said and the social context of the terms employed? Is it cause you're looking to be offended?
If you can't provide some analysis of the origins of thoughts and feelings which are presumably your own, maybe you should keep them to yourself till you can.
If you're tired of it, start something else. Or hang out and jump ship when the next great thing comes along. Trying to preserve the golden age is rearranging the deck chairs on a sinking ship.
And it does. And 3rd party plugins that Apple has no control over reduce the quality of that experience, increase support costs, and generally add instability.
Pardon me, but I do have a clue as to what's actually interesting and/or difficult from a CS perspective. I work in NLP research, and I'm actually familiar with other research systems being developed IBM, as well as other organizations.
I wasn't particularly impressed or surprised.
2) Use spoon to extract the ice from their glass
3) Put ice in coffee
Also, you may need to threaten the person with the spoon to get the ice.
I'd be curious to know more about how the system works, and how they trained it and/or curated the knowledge base it worked from. Maybe they'll write a more informative paper or something. But as it is, this wasn't a particularly surprising or impressive technology demo.
Also, don't give advance warning and don't give reasons. Warning just creates risk for you and stress for him. Giving reasons is legally problematic, and he's not going to believe what you tell him anyway.
Just tell him that it's not working out, that you wish him the best, and hand him a final paycheck. Severance might be nice, if you can afford it.
As someone that works in NLP and information extraction research, I've gotta say that unless there's some massive technological upheavals, we're not getting to thinking machines for a good long time.
Mostly, it was about keeping crappy flash apps of iOS. And from a platform perspective, that did actually make a lot of sense.
2) Amazon's VOD service provides DRMed video, too.
Then what's the issue?
We'll see how it shakes out. Maybe it'll be like the "nothing but objective-c" thing. People freak out too much about this kind of stuff.
You misspelled vaporware.
Apple announced something they're gonna roll out in the next rev. of iOS. Google put out a press release.
Microsoft most certainly did have one during the browser wars, and were leveraging it to get people to increase IE marketshare.
With Windows on the desktop, you didn't really have much of a choice but Windows if you were going to use pre-package software, play games, or do business. With the iPhone, you've got tons of competition - Android, RIM, and WP7. If you don't want to work in that model, nothing forces you to, either as end user or VAR.
The select for update thing, though, sounds like a table type selection issue. Doesn't innodb handle locking at roughly row level (maybe db page)? Seems like that one is for people who stick with MyISAM. If you're doing concurrency sensitive stuff, pick a better storage engine (or more robust db).