I think most people have an issue with "friends" forking out time and/or money to play these crappy games all day and subsequently posting all kinds of nonsense about them and suddenly you have to block a torrent of useless shit from the news feed to get Facebook close to being back to the communication medium the rest of us intended it to be.
I don't care if you need more knights, or you have too many turnips, or you want to trade for an orange starfish. Facebook was so, so much more pleasant to use before they opened up that stupid developer API.
If only you could start something like a "transaction", which you could then "roll back" after finishing the test, leaving the database in its original state.
...which means you now can't test transactions.
SQL Server supports nested transactions. I'd imagine other vendors do as well.
...because on every application I have ever worked on, the Database has always been the performance bottleneck.
What alternative have you seen that handles the same workload more efficiently? Flat files? I've seen plenty of database-related performance issues, but it's almost never inherent in the database - it's the idiot that wrote the lousy table-scanning code that's reading a couple rows out of a table with millions that's the problem.
Testing of DB applications is always a problem, because the running of tests generally changes the database, rendering tests unrepeatable without reseting the database.
If only you could start something like a "transaction", which you could then "roll back" after finishing the test, leaving the database in its original state. And if you could somehow "back up" the database and "restore" it on a test server, or under a different name. That would be awesome.
And don't get me started on stored procedures and the difficulty of using source code management with stored procedures.
Checking your create/change scripts into source control is no more difficult than checking your C source in prior to compiling it.
SQL is fixed in a syntax and written with naming conventions and styles that can best be described as neo-Cobal.
While I don't totally disagree on this point, calling SQL "fixed" is a bit like saying C# and Java are the same. I promise you any meaty SQL Server code will not run on Oracle without very significant changes that will have to be done by someone that will cost you a lot of money (and likewise with Oracle to SQL Server). The capabilities vary wildly by platform, and the syntax is only identical for the simplest of CRUD statements.
Last gripe: A traditional Relational database imposes ACID overhead on every application, even if you don't really need it or use it. This is like a programming language that imposes a SORT overhead on all your data structures even if you rarely or never need to sort them.
I have to give this one a LOLWUT. If you're using a big RDBMS, it's likely a multi-user system. If you've got multiple users and connections, you want ACID. This isn't like imposing sorting overhead on data structures, it's like imposing the basic memory protection, process isolation, and filesystem durability you find in any competent operating system. If you want to see what it's like without those protections, go use Mac OS 9 for a week or so, or an Access database used by a few dozen people over a network.
This must mean it fixes the problems with the d-pad being too stiff, having too much travel distance, having vague tactile feedback, and being too large to move freely around the tight recess it's placed in.
Oh, it doesn't? Well, nothing to see here, then. Maybe we can start some kind of benefit fundraiser to buy these guys a couple GBA SPs so they can see how to do it properly.
It's a bug in the font rendering component, which apparently lives in kernel space.
Not necessarily. Every iPhone has the same default root password out of the box, so I would think any user code stands a pretty good chance of being able to escalate permissions and start running kernel-level code.
It's probably largely due to the fact that until around the time the iPhone hit the market, US smartphones were mostly limited to ugly hunks of plastic like the Treo 650, Blackberry 8700 series, or various Symbian bricks, and they generally didn't have particularly remarkable web browsing or media playing capabilities.
It wasn't until Apple came along and thrust style (and admittedly, usability) to the forefront of smartphone design that the non-business market really started to pay attention. Say what you want about Apple's products, but they have taking full advantage of a style-conscious market down to a science. In standard follow-the-leader fashion, other handset makers have clued in on this, and now we've got a much more lively market, and it seems that plain old feature phones get very little hype around here anymore.
I think that would be the machine operating the machine that's operating the ATM. It brings the level of automation to where you only have to subconsciously think of money, or anything that rhymes with money in order to make a withdrawal.
So... there aren't any flight sticks for flight sims, steering wheels for racers, arcade sticks for fighters, or turbo settings on 3rd party controllers because players shouldn't be allowed to get an advantage because they've bought an extra peripheral?
Perhaps there is an actual, consistent argument for not permitting a mouse to work with a console, but that most certainly is not it.
Especially considering you can get a decent mouse for under $20. It's not like they're reserved for the elite or something.
I'm guessing the real reason is more along the lines of "We want to keep selling you $50 gamepads".
I like the Microsoft process:
* Steve strolls out, throws some chairs.
* End of discussion.
Simple and direct.
Sadly, I think I'm starting to prefer Microsoft's process too. As a corollary to Hanlon's Razor, I think it's generally easier to forgive stupidity/incompetence than it is to forgive malice.
Will be really hard to acknowledge a defect after all that hype.
Which is why it won't happen. Here's how I predict things going down:
Steve strolls out, makes some remarks about huge sales of the iPhone 4.
"Bound to be a few issues reported when you have such a large share of the market", etc, etc.
Some tap dancing about real-world performance, estimated signal strength, "every cell phone does it", and an assortment of contemptuous remarks or outright lies, much like the explanation of why apps aren't approved at the iPhone 4 reveal event.
White model ship date announced, bumper cases quietly go on sale for $20 with no announcement, and Steve wraps up with some feel-good piece hoping to bury the issue(s).
Apple's board of directors make a few phone calls to Steve's health care providers to see if he's up to date on payments for that liver he bought, hoping not to have their front man degrade into the next Ken Kutaragi.
...Which may or may not work if the acceleration is in fact caused by a very faulty ECU, which also happens to be controlling your automatic transmission.
And if you didn't have that 10% that is eventually needed, you'd be totally screwed. Do we really need to play the 20/20 hindsight game every time somebody thinks of something like this?
They can't even afford mechanical engineers with the skill-set to design a robust replaceable-battery-compartment into their products. (the most recent attempt I can remember is the battery compartment in the Newton, and almost every Newton I have ever seen has a broken battery compartment)
I don't know if you remember Apple's financial situation from around the Newton era, but it was substantially different from how they're doing now.
Slashdot Mirror
I think most people have an issue with "friends" forking out time and/or money to play these crappy games all day and subsequently posting all kinds of nonsense about them and suddenly you have to block a torrent of useless shit from the news feed to get Facebook close to being back to the communication medium the rest of us intended it to be.
I don't care if you need more knights, or you have too many turnips, or you want to trade for an orange starfish. Facebook was so, so much more pleasant to use before they opened up that stupid developer API.
I'd argue it's more Skinner than Pavlov, but my sentiments about them are basically the same.
NoScript seems to block PDFs by default, which you can then click to load.
iTunes is a nice OS, but what it needs is a decent media manager.
If you weren't at +5 already, you'd get all my mod points.
Imagine if the American judicial system more closely resembled the uptight strife of a stereotypical HOA. The prospect is genuinely unpleasant.
SQL Server supports nested transactions. I'd imagine other vendors do as well.
What alternative have you seen that handles the same workload more efficiently? Flat files? I've seen plenty of database-related performance issues, but it's almost never inherent in the database - it's the idiot that wrote the lousy table-scanning code that's reading a couple rows out of a table with millions that's the problem.
If only you could start something like a "transaction", which you could then "roll back" after finishing the test, leaving the database in its original state. And if you could somehow "back up" the database and "restore" it on a test server, or under a different name. That would be awesome.
Checking your create/change scripts into source control is no more difficult than checking your C source in prior to compiling it.
While I don't totally disagree on this point, calling SQL "fixed" is a bit like saying C# and Java are the same. I promise you any meaty SQL Server code will not run on Oracle without very significant changes that will have to be done by someone that will cost you a lot of money (and likewise with Oracle to SQL Server). The capabilities vary wildly by platform, and the syntax is only identical for the simplest of CRUD statements.
I have to give this one a LOLWUT. If you're using a big RDBMS, it's likely a multi-user system. If you've got multiple users and connections, you want ACID. This isn't like imposing sorting overhead on data structures, it's like imposing the basic memory protection, process isolation, and filesystem durability you find in any competent operating system. If you want to see what it's like without those protections, go use Mac OS 9 for a week or so, or an Access database used by a few dozen people over a network.
This must mean it fixes the problems with the d-pad being too stiff, having too much travel distance, having vague tactile feedback, and being too large to move freely around the tight recess it's placed in.
Oh, it doesn't? Well, nothing to see here, then. Maybe we can start some kind of benefit fundraiser to buy these guys a couple GBA SPs so they can see how to do it properly.
Well I suppose that's one way to keep your blood sugar down.
No kidding. The only reason he's predicting that is because it's better for their increasingly creepy business model.
Not necessarily. Every iPhone has the same default root password out of the box, so I would think any user code stands a pretty good chance of being able to escalate permissions and start running kernel-level code.
It's probably largely due to the fact that until around the time the iPhone hit the market, US smartphones were mostly limited to ugly hunks of plastic like the Treo 650, Blackberry 8700 series, or various Symbian bricks, and they generally didn't have particularly remarkable web browsing or media playing capabilities.
It wasn't until Apple came along and thrust style (and admittedly, usability) to the forefront of smartphone design that the non-business market really started to pay attention. Say what you want about Apple's products, but they have taking full advantage of a style-conscious market down to a science. In standard follow-the-leader fashion, other handset makers have clued in on this, and now we've got a much more lively market, and it seems that plain old feature phones get very little hype around here anymore.
Probably not. You have to manually initiate the process once the page loads.
I think that would be the machine operating the machine that's operating the ATM. It brings the level of automation to where you only have to subconsciously think of money, or anything that rhymes with money in order to make a withdrawal.
It's a machine that operates the ATM for you. It also goes by the name Automated ATM.
Especially considering you can get a decent mouse for under $20. It's not like they're reserved for the elite or something.
I'm guessing the real reason is more along the lines of "We want to keep selling you $50 gamepads".
And Google doesn't have the balls to move out, apparently.
Sadly, I think I'm starting to prefer Microsoft's process too. As a corollary to Hanlon's Razor, I think it's generally easier to forgive stupidity/incompetence than it is to forgive malice.
Which is why it won't happen. Here's how I predict things going down:
...Which may or may not work if the acceleration is in fact caused by a very faulty ECU, which also happens to be controlling your automatic transmission.
And if you didn't have that 10% that is eventually needed, you'd be totally screwed. Do we really need to play the 20/20 hindsight game every time somebody thinks of something like this?
Which means it's time to start reversing this thing into as many humorous/offensive phrases as possible.
"Tell Roger to have a Coke and a smile and shut the fuck up."
I don't know if you remember Apple's financial situation from around the Newton era, but it was substantially different from how they're doing now.
Interesting. I've been running it on a 3GS for about a week now and haven't noticed any stark differences in battery life so far.