When Google couldn't figure out a functional use for Wave, and kind of threw it out for the public to find a use for it, the writing was on the wall.

Real time typing... Awesome you get to watch people hunt and peck, correct spelling, rethink what they are writing, etc etc. Does any of that help their communication? No.

Drag and drop files. Useful, but no auto-verisioning / checkin checkout makes it no more useful than emailing the file.

Open to develop widgets. Awesome, now I can add 25 different choose your own adventure bots to add into your wave. Still widget writers can't find a functional use.

People talking about it being great for communication that needs to be more formal than IM, yet more real-time than email, and more dynamic than a wiki. So there is a use. How much of people's daily communication would fall into this category? I don't think the percentage of most people's daily communication that could fall into this category made it worth their time to learn wave.

New Technology with no practical application may be cool but it's not technology.

or you know you could just be a good unix admin and use ssh.

Why can't I do a print preview, print selected, or adjust orientation in Chrome? This is basic functionality that every other browser does just fine. I'm glad that 18 months after print preview being requested in chrome, that it's been catagorized behind things like domain specific zoom level memory. Way to prioritize things Google....

http://www.google.com/support/forum/p/Chrome/thread?tid=29ea05faa34bade4&hl=en

This is not true. How useable would Facebook be without requiring a password to log in? Yes it would be easier to get in, but you would lose any trust in the application as anyone could be posting as anyone else. A system should be as secure as the data you are trying to protect within it.

Enterprise Single Sign On projects always starts with this same (what I would argue flawed) logic.

It would be very convenient for me if my house key also started my car, opened hotel doors and my rental car when I travel, and opened my safe deposit box at the bank. Does this sound like a good idea? Moving systems to a single authentication system can make sense, but most of the time getting a true single sign on requires you replicate password changes to systems that cannot change their authentication source and then you end up with the weakest link (say a messaging client that stores the password as an md5 hash) having the key to accessing your most guarded systems (i.e. payroll systems).

You are only looking at one factor to a password policy. The effectiveness of a password policy is the correlation of all of the factors.

Password composition (min characters, character set requirements) - Helps make dictionary attacks more difficult.
Password expiration (change your password every x days) - Helps eliminate shared accounts, prevents compromised accounts from staying compromised forever.
Authentication Lockout (temporarily locking an account after x number of incorrect attempts) - protects against brute force and dictionary attacks.
Attestation (verifying account is needed and authorizations associated to it are correct every x months) - protects against abandoned accounts.

While you can argue whether some of these policies in and of themselves are effective, when combined into a single policy they are far more effective than the sum of their parts.

For example, your argument that automated hacking tools make password expiration useless is only valid if you don't also have a password lockout policy as well.

Hmmm... proxy settings button is greyed out??? Beta Safari, you are dead to me...