It's been this way in the Windows vs Mac world for a long long time. Who cares if manufacturers only have a small piece of the pie. Google Market is sitting on every one of those phones....putting money right into Google's hands.
Finding a decent way to look through GB of logs to find something that happened a week ago is going to be MUCH more of a challenge than just arguing with any client to get the information you need. Not to mention, the only way you're going to trace any random malfunction back to any random source is if you have so much logging that half your computation time is spent managing your logging system and the needed disk writes....and let's not talk about the volume of log data THAT would produce.
Logging can, and should, only do so much. You can't, and won't, catch everything with it.
Definitely not hopeless. The main thing is that you have to set expectations. They will do what you let them do. If a bug report is inadequate, it's bounced with a request for more information, highlighting specifically what is needed.
Our company has also instituted a layer of BA's that sit between the devs and the clients and have thankfully done a fantastic job of training the clients what they need to provide when they submit a bug report. Our BAs also know what we developers expect and nothing gets passed along to a dev until there's enough information to get started on it.
It's also very important that if a client is just complaining, their complaint is either rejected due to lack of "whatever's missing" or it's turned into a new feature request.
Even more important is letting the client know, with all due respect, that if they can't get you what you need, then they aren't going to get what they want. They need to understand that they can be wrong too, and all the arm waving and shouting in the world won't help if they don't give you what you need to do your job.
You need to do a little research. Everything in the industry is pointing right at HTML5 as the future of application programming...especially with cross platform applications.
Evan as a fanatical android fan, I can tell you that you're dead wrong. webOS has a tons of great ideas both in the interface and underlying app-system that would be very useful in a combined scenario. The ability to write apps in the webOS way, for an android device, would be fantastically awesome.
And please understand that my reference to the future versions of tegra is not to be taken literally. Simply meant to be an example of the progress that will take place during the Vita's lifetime.
The reason the kindle fire is sluggish is the semi-botched android fork that amazon developed. Similarly specced honeycomb tablets run like a bat out of hell. the 6.2 patch from amazon also solved a plethora of the performance issues, so it IS getting better. Not there yet, but I've noticed a marked improvement.
In any case, the iOS line has always been sluggish. I owned several of them (Three iphones and an ipad) and always had freezes, overall sluggish behavior, and generally "meh" performance....especially given how incredibly simplistic their overall interface is.
As I previously stated, the only thing going for the Vita is the pretty graphics...aka the "hardware."
Of course next year you'll be able to buy a Tegra 3 powered phone with more "prowess" than the Vita for less than the Vita by a good $100.
Not to mention the Tegra 4, 5, 6, 7, 8, and 9 which will all come out within the lifetime of this single gaming system, and will offer graphics laughably beyond anything the Vita can do.
The problem is that in today's market, with so many viable alternatives for mobile gaming entertainment, the insane cost of memory is going to be a deal breaker for most users.
Sure it has pretty graphics, but that's almost certainly going to be the one-and-only thing going FOR the Vita. I can't think of a single other argument in support of buying one of these.
I had the same set of thoughts. There are a ton of long standing solutions to these sorts of problems that would have served their needs far better than storing crap in a database. I don't get it either... If inode limits became a problem, there are lots of ways around that as well...
Are you really comparing being a parent to owning stock in a company? You're either not a parent or you're hoping I'm not.
Selling stock of a company/product is hardly the same thing as dumping a loved one off at an orphanage...and only a blithering idiot would make that comparison.
When you buy stock in a company, you gamble with money. If you lose on that gamble, it's your own fault, and you lose your money. Money != a life.
If "no one else" agreed with me, MSFT wouldn't have ANYONE buying stock...and that's not the case. Obviously these people don't agree with you, or they would have sold.
If people with stock don't like the performance of the stock, they need to sell or shut up. They are in this situation because they put themselves there. MSFT really doesn't need them at the end of the day anyway. MSFT has a solid, consistent income, and more than enough money in the bank to deal with a loss of a large number of shareholders.
Also, in the next 10 years I'd bet on MSFT's products to significantly turn the tide against the apple growth. Their next generation of phone/tablet/pc OS's is exactly the direction they need to be heading, and they're going to beat apple to market with it. (WORA apps across all windows devices, pc & phone alike)
The (sizable) company that I work (on the development team) for implements the facebook login & commenting systems. It's a free service facebook offers to anyone who wants to use it. You get $0 from facebook for using it.
The reason THEY want to only use it is the same reason WE only use it. Maintaining 6 points of entry and keeping up with changing apis for multiple networks is a huge pain. Best to pick the one with the widest possible audience and just maintain that one. Facebook's api and customer facing interface is also super simple and reliable.
This is basic...and anyone spouting some corporate conspiracy theory needs to get a clue.
Except having worked with things like this, i know that facebook does no such thing. Facebook gives you nothing at all in return for using their services. The upside is that your content gets out, and shared on facebook....which drives users to your site. I'm sure facebook mines that data for all kinds of fun things though.
Even so, this is very much a defensive move. Ever heard of a defensive force NOT shooting back? Apple opened a can of worms, and now they are paying the price. They should have left well enough alone.
And by the way, google's android keyboard has supported voice input in place of text input in ANY application for a very long time now. It's built right into the keyboard so this supposed new feature apple offers is far from anything innovative or new. For all the screaming Jobs did about Android ripping off features, he should have stood back and seem how most of the iPhone's user interface/experience now is a direct ripoff of something google has been doing for years.
You are apparently confusing "talking to" vs "talking on."
Standing in a public place and announcing your text message or telling everyone about the meeting your just scheduled (or declined) goes beyond just making you look stupid. It's privacy invading and it's something almost no-one would be caught dead doing.
And I can only imagine how annoying it would be to be in a public place and listen to some idiot jovially text with someone...via voice. Google has supported voice texting for a long time now and no one uses it for the same reason.
I work in an apple centric workplace. I said when they announced Siri that the only time I would ever see anyone use it would be to demo the feature to someone else. It's proven true. I've NEVER seen anyone use it in public, and the ONE time i did see someone use it was just a demo in the office to someone else....and Siri completely misunderstood what they were trying to do.
It's a useless gimmick. Nothing more, nothing less.
True, but all modern cars have brake reserves as well as rev limiters. Even if it did over-rev and didnt get limited...and the engine blew, you'd still have a brake reserve...and not die.:-P
In any case, even if the brakes didn't disengage the CC, you should still be able to overpower the engine with braking power and come to a stop.
There are a million and one ways out of this scenario. It really comes down to the amount of time the driver has, as well as their state of mind.
"government subsidized loan." The banks would still be welcome to loan you whatever they wanted. The major difference is that the government wouldn't be subsidizing them anymore, and banks wouldn't be FORCED to loan you money.
Slashdot Mirror
It's been this way in the Windows vs Mac world for a long long time. Who cares if manufacturers only have a small piece of the pie. Google Market is sitting on every one of those phones....putting money right into Google's hands.
That's a cop-out....and completely unrealistic.
Finding a decent way to look through GB of logs to find something that happened a week ago is going to be MUCH more of a challenge than just arguing with any client to get the information you need. Not to mention, the only way you're going to trace any random malfunction back to any random source is if you have so much logging that half your computation time is spent managing your logging system and the needed disk writes....and let's not talk about the volume of log data THAT would produce.
Logging can, and should, only do so much. You can't, and won't, catch everything with it.
Definitely not hopeless. The main thing is that you have to set expectations. They will do what you let them do. If a bug report is inadequate, it's bounced with a request for more information, highlighting specifically what is needed.
Our company has also instituted a layer of BA's that sit between the devs and the clients and have thankfully done a fantastic job of training the clients what they need to provide when they submit a bug report. Our BAs also know what we developers expect and nothing gets passed along to a dev until there's enough information to get started on it.
It's also very important that if a client is just complaining, their complaint is either rejected due to lack of "whatever's missing" or it's turned into a new feature request.
Even more important is letting the client know, with all due respect, that if they can't get you what you need, then they aren't going to get what they want. They need to understand that they can be wrong too, and all the arm waving and shouting in the world won't help if they don't give you what you need to do your job.
Please explain the logic behind that statement.
You need to do a little research. Everything in the industry is pointing right at HTML5 as the future of application programming...especially with cross platform applications.
Evan as a fanatical android fan, I can tell you that you're dead wrong. webOS has a tons of great ideas both in the interface and underlying app-system that would be very useful in a combined scenario. The ability to write apps in the webOS way, for an android device, would be fantastically awesome.
And please understand that my reference to the future versions of tegra is not to be taken literally. Simply meant to be an example of the progress that will take place during the Vita's lifetime.
The reason the kindle fire is sluggish is the semi-botched android fork that amazon developed. Similarly specced honeycomb tablets run like a bat out of hell. the 6.2 patch from amazon also solved a plethora of the performance issues, so it IS getting better. Not there yet, but I've noticed a marked improvement.
In any case, the iOS line has always been sluggish. I owned several of them (Three iphones and an ipad) and always had freezes, overall sluggish behavior, and generally "meh" performance....especially given how incredibly simplistic their overall interface is.
As I previously stated, the only thing going for the Vita is the pretty graphics...aka the "hardware."
Of course next year you'll be able to buy a Tegra 3 powered phone with more "prowess" than the Vita for less than the Vita by a good $100.
Not to mention the Tegra 4, 5, 6, 7, 8, and 9 which will all come out within the lifetime of this single gaming system, and will offer graphics laughably beyond anything the Vita can do.
There's another couple "apps" called "iOS" and "Android" that already support all those features and far more and can be had for far cheaper. ;-)
The problem is that in today's market, with so many viable alternatives for mobile gaming entertainment, the insane cost of memory is going to be a deal breaker for most users.
Sure it has pretty graphics, but that's almost certainly going to be the one-and-only thing going FOR the Vita. I can't think of a single other argument in support of buying one of these.
I had the same set of thoughts. There are a ton of long standing solutions to these sorts of problems that would have served their needs far better than storing crap in a database. I don't get it either... If inode limits became a problem, there are lots of ways around that as well...
Are you really comparing being a parent to owning stock in a company? You're either not a parent or you're hoping I'm not.
Selling stock of a company/product is hardly the same thing as dumping a loved one off at an orphanage...and only a blithering idiot would make that comparison.
When you buy stock in a company, you gamble with money. If you lose on that gamble, it's your own fault, and you lose your money. Money != a life.
If "no one else" agreed with me, MSFT wouldn't have ANYONE buying stock...and that's not the case. Obviously these people don't agree with you, or they would have sold.
If people with stock don't like the performance of the stock, they need to sell or shut up. They are in this situation because they put themselves there. MSFT really doesn't need them at the end of the day anyway. MSFT has a solid, consistent income, and more than enough money in the bank to deal with a loss of a large number of shareholders.
Also, in the next 10 years I'd bet on MSFT's products to significantly turn the tide against the apple growth. Their next generation of phone/tablet/pc OS's is exactly the direction they need to be heading, and they're going to beat apple to market with it. (WORA apps across all windows devices, pc & phone alike)
ICS is meant to run on tablets AND phones. Google has been more than upfront about this...
This is intended to be satirical and sarcastic, right?
The (sizable) company that I work (on the development team) for implements the facebook login & commenting systems. It's a free service facebook offers to anyone who wants to use it. You get $0 from facebook for using it.
The reason THEY want to only use it is the same reason WE only use it. Maintaining 6 points of entry and keeping up with changing apis for multiple networks is a huge pain. Best to pick the one with the widest possible audience and just maintain that one. Facebook's api and customer facing interface is also super simple and reliable.
This is basic...and anyone spouting some corporate conspiracy theory needs to get a clue.
Except having worked with things like this, i know that facebook does no such thing. Facebook gives you nothing at all in return for using their services. The upside is that your content gets out, and shared on facebook....which drives users to your site. I'm sure facebook mines that data for all kinds of fun things though.
-RV
Google doesn't own Motorola Mobility yet...
Even so, this is very much a defensive move. Ever heard of a defensive force NOT shooting back? Apple opened a can of worms, and now they are paying the price. They should have left well enough alone.
And by the way, google's android keyboard has supported voice input in place of text input in ANY application for a very long time now. It's built right into the keyboard so this supposed new feature apple offers is far from anything innovative or new. For all the screaming Jobs did about Android ripping off features, he should have stood back and seem how most of the iPhone's user interface/experience now is a direct ripoff of something google has been doing for years.
You are apparently confusing "talking to" vs "talking on."
Standing in a public place and announcing your text message or telling everyone about the meeting your just scheduled (or declined) goes beyond just making you look stupid. It's privacy invading and it's something almost no-one would be caught dead doing.
And I can only imagine how annoying it would be to be in a public place and listen to some idiot jovially text with someone...via voice. Google has supported voice texting for a long time now and no one uses it for the same reason.
I work in an apple centric workplace. I said when they announced Siri that the only time I would ever see anyone use it would be to demo the feature to someone else. It's proven true. I've NEVER seen anyone use it in public, and the ONE time i did see someone use it was just a demo in the office to someone else....and Siri completely misunderstood what they were trying to do.
It's a useless gimmick. Nothing more, nothing less.
Not in the traditional sense, but diesels are all fuel injected. Turn off the key, fuel injection stops.
True, but all modern cars have brake reserves as well as rev limiters. Even if it did over-rev and didnt get limited...and the engine blew, you'd still have a brake reserve...and not die. :-P
In any case, even if the brakes didn't disengage the CC, you should still be able to overpower the engine with braking power and come to a stop.
There are a million and one ways out of this scenario. It really comes down to the amount of time the driver has, as well as their state of mind.
"government subsidized loan." The banks would still be welcome to loan you whatever they wanted. The major difference is that the government wouldn't be subsidizing them anymore, and banks wouldn't be FORCED to loan you money.