http://mediamatters.org/mmtv/200611150004

Go on, justify it.

Intellectualism is being used as a synonym for elitism, not intelligence.

How can you like a man who raped and murdered a young girl in 1990?

The solution to this is to use a table-valued function instead of a scalar and then CROSS APPLY it to the rest of your data set:

http://www.databasejournal.com/features/mssql/article.php/3845381/T-SQL-Best-Practices--Dont-Use-Scalar-Value-Functions-in-Column-List-or-WHERE-Clauses.htm

Or, as stated, just use a view. Scalar UDFs are good for setting SQL variables based on today's date or a customer ID one-time; not much else. Indeed, a shame.

No, the problem is that the "real issues" you are talking about are things that 99% of your typical DBAs will never see in their lifetime, because they work at a church or a pharmacy or a box factory.

It's great that Facebook and Google and eBay need map-reduce and Erlang and something more scalable than SQL Server Express or Berkeley DB. But they are the exception, not the rule. Excoriating people for pointing that out is, at best, irrelevant and at worst harmful to the idea of alternative data storage mechanisms.

I'm not picking on you directly, I see it as a larger symptom, that somehow because SQL/RBDMS is not ideal for certain projects, that it should be abandoned at all levels, sooner rather than later, even though there's 40+ years of RDBMS architecture manuals, best practices, knowledge bases, 3rd party apps, "SQL for Dummies", and so on to help the involuntary DBA succeed without having to figure out Cassandra.

I guess my concern is that a lot of small businesses and shops will see something like this, will think, "You know, our Access database sucks," and try to port themselves over to this, and guess what? The learning curve here is a lot steeper than SQL (the *academic* side of SQL-alternatives is just now getting into 3rd gear), the business case for it is pretty poor in most cases, and you'll end up with a lot of people wasting time trying to get Erlang processes going instead of just migrating to MySQL and keep on carrying on. There's way too much "Rah, Rah, Death to SQL" being attached to these new things, and to me it seems overblown.

But you know, I'm optimistic. 5 years from now, it may be a different ball game altogether, and then us DBAs just have more things to learn and to do.

Do unto others as you would have others do unto you.

Man, if we come up with one or two more anecdotes, we might have some data!

Yay, I hope a bunch of neighborhood amateurs can come up with Seven Samurai!

This type of thinking will eventually lead to the creation of things whose cost is zero and no higher.

Sounds great!

Wow.

First off, the major issue people have with video game violence is that it leads to desensitization - people who are less emotional about video game deaths tend to show less emotional response when presented with actual real-life violence. So, way to get the basic premise wrong.

Secondly, you get the other basic part of the premise wrong, which is that "brains making disconnects" between video games and real life is a formative experience - you aren't innately born with it - and that since video games are primarily played by children, they're worried that they are short-circuiting that very disconnect that most people develop.

Thirdly, way to co-opt their " the type of people that X" argumentation style, which makes your point just as invalid as theirs.

Fourthly, way to use yourself as a "plural of anecdote is data" fallacy.

C'mon, I know that I personally am not affected by video game violence (I generally avoid those types of games), but that doesn't mean no one else is, or that the CUMULATIVE effect of video game violence might (or might not) lead to increased real world violence.

Being dismissive of that sort of thing because you just can't see yourself doing it means we might as well not have the fields of anthropology or psychology or economics. Why bother trying to learn how other people act, right?

How fucking unscientific.

So ... back to the original point (and the original article): for the most common of those "non-computer computers" (cellphone, camcorder, camera, GPS, music/video player) is 256MB sufficient?

Will a 250GB drive be sufficient in 2020? Most likely not, except as a kind of portable drive. Bandwidth expansion, data preservation, increased resolution and fidelity, customer demands, and the increasing integration and synchronization between devices that you directly acknowledge will push us towards bigger and bigger drives.

Oh, I'm sorry, is 256MB good enough for a gaming console / mobile phone these days?

At least address the original point.

It's called the Gell-Mann Amnesia effect.

The transaction itself doesn't have to be held up, but if the EU rules it violates anti-trust, they won't be allowed to do business in the EU. Kind of a mood-killer, if you will.

Winston loved Big Brother.