Given that much more hidden spy cameras are available for far less than the $1500 cost of Glass, what will it take for general acceptance to finally take hold?

First of all, I don't get the link between these two things. "Cheap, easily-hidden spy cameras exist, therefore there should be general acceptance of expensive, hard-to-hide spy cameras"? Is that the basic thought behind this sentence? Huh?

Secondly, you forgot to explain why I should give a shit about whether Glass is accepted or not. What's my interest in it? I don't want one. I don't know anybody who wants one. The only people I ever read about who have them are jerks. And I don't work for Google.

So to answer your question: general acceptance will happen when Google cancels the project.

You... you do realize this is a forum all kinds of people can read right? That I wasn't actually saying that message to you specifically?

Your situation aside, my *point* was that now you can buy a relatively sexy car that has great gas mileage, which is an option that didn't exist in any form 5 years ago.

(Although now I'm a little curious-- where can a Echo go that a Fusion can't? Is there some kind of weird parallel universe Twilight Zone road that rejects cars over a certain weight? Or are you going to make some ludicrous claim, like the Echo can drive through 4 feet of mud?)

Now you can buy a Fusion Hybrid which beats the Echo on mileage and still has enough interior space to seat all your friends and doesn't hurt with the opposite sex either.

More expensive outlay though.

If SQL Server isn't being used (no connections), the OS'll just swap it out and there's no wastage. Ditto all the other things you mentioned. If you're going to be writing software, maybe you should learn the old adage about premature optimization.

My advice is:
1) Install everything you need
2) See if a problem actually occurs
3) It won't so stop worrying

I bought 3 of those and put them in a closet. They're also fucking tanks, so I figure I'm set until 2025 or so as far as keyboards go.

Ok so let's take Stoss' argument at face value, even though he was obviously being sarcastic.

You're arguing that the solution to them cheating on taxes is to adopt a currency where EVERYBODY will cheat on their taxes? How does that improve things, exactly?

The law accomplishes nothing and makes every food item more expensive. That alone is reason to oppose it.

You know your TV? It has this thing in it called a "V-chip". It blanks out the channel if the content rating is too high for the parental controls. This functionality is required by law, and as a result, every TV is slightly more expensive. Have you ever seen someone (intentionally) turn the V-chip on? Ever? In your entire life?

No. It made TVs more expensive and accomplished nothing else. Same with this GMO labeling law.

But I'm amazed that no one is constructively talking about POD in these "future of books" discussions, even at the risk on the store side of the big chains folding. (ProTip - why would I even order from amazon if I could get my copy in my hand at lunch?)

e-readers have made the entire POD market obsolete. (Mostly obsolete-- there's still "vanity press"-like operations, but they've always been small-beans.) Why would I print a book on demand when I could have it on my Kindle faster and easier? Oh, and cheaper, too, once you have a dozen or more books being printed.

I don't want to fund a *lot* of things my federal tax funds on moral grounds, I still have to pay it.

Sorry, I don't have a lot of sympathy here. If they get to weasel out of buying contraceptives on moral grounds, then I get to decide where my income tax money is spent on moral grounds. No special privileges.

GUIs have safety features like the recycling bin (or trash for Mac users) and the Undo feature.

The saddest thing is that there's no reason CLIs couldn't have these same safety features, except that the people who develop CLIs are (generally speaking) grumpy old codgers who hate change and want computers to behave exactly the way they did in 1974.

That's why all the software was written in THINK C or THINK PASCAL. (Or CodeWarrior later on.) MPW had a relatively small marketshare.

That said, THINK C did have a CLI for C apps that required one, but that was just to be compliant with the relevant C standard-- they didn't really have a choice.

And yet everyone at some point has had to do a task like this that could have been performed much faster on the command line. The problem is that many people do not know that there is a faster way to do it. That ignorance is what the article is trying to address.

Right; but you're talking about a task that people (easily) go *years* without ever needing to do. And it takes *months* to learn the CLI. And since the CLI is so unforgiving (no recycle bin, no "undo" command, etc), learning it could easily cause you to lose your data.

Does that trade-off sound worthwhile to you?

The sad fact is that there's no reason the CLI couldn't have those safety features, other than the people who prefer (and develop) CLIs also hate change. Generally speaking.

If computer science students are unwilling to learn something, then fail them. End of story.

What if they don't have the memory for a CLI? What if they're dyslexic? What if those people love computers and want to write software?

You know the great thing about GUIs? They spend a lot of effort being accessible to everybody. They have tons of features to help those with disabilities, no matter how minor or severe. They have a handy "Undo" function so minor screwups don't become major disasters.

It's grossly unfair to fail someone because they can't easily use a particular interface, when the job can be done equally-well using another interface. If you're teaching programming, teach programming... don't fail your students because they can't use a particular UI. If the student can complete the assignment perfectly using an IDE (with its accessibility features), but can't wrap their head around the CLI-- well, what's wrong with that? They completed the assignment!

Should we refrain from teaching the multiplication table because we have calculators now to do it for us?

Yes. ...oh were you looking for a "no" there? Because the answer is obviously "yes". Sorry.

Any CS graduate who hasn't worked with the CLI during his/her studies is simply not worth hiring and indeed should not be permitted to graduate.

Discrimination is wrong. That is what you're proposing. That's really what everybody in this thread talking-up the CLI is proposing.

Fucking Minecraft is a Turing-complete GUI app. One of dozens. Did you even briefly think about that statement? It's so obviously proven wrong it boggles my mind.

The problem is that tasks that are fast on the CLI are always contrived-as-hell examples. "Rename every file with the word 'dog' in it!"

Hey here's a thought: I'll rename your files and time me. Now how about you do some non-linear editing of this video for YouTube and I time *you*. Oh... oh... you can't do that on the CLI? At all? I might be a bit slower but I can do your task and you can't do mine at all?