The problem with this approach is that the next target will be XML based services, JSON services, and whatever else that is out there that accepts user input and turns it into a map. Feels like yet another pointless rule that developers will have to remember till the end of days (and will probably keep ignoring in 99% of the cases). Processing input from users? Use String objects with a cryptographically strong hash. Pay the price, keep track of them all the way downstream.

Actually, there is absolutely something "they can do to eliminate your commute" - they can pay him (her?) more money to make up for the (likely) difference in rent or inconvenience of relocation expenses. This argument in general is highly unreasonable and perpetuates the "fuck everyone" attitude. Meanwhile, even in very big cities individual industries in IT have a relatively small pool of people, and a good % of jobs are found via former coworkers. So while the company might not think twice before fucking you, you should think twice before fucking your colleagues - in a few months, when you interview in some other company, your resume might be on their desks.

dividends and capital gains are double taxed

Because before you steal stuff, you discover the whole. Unless you know it is there because you left it, there have had to be this "aha" moment when some dude logged into *his* citibank account and tried it. ah, its too late to respond, this post is too stale

Seems like the website required to have *some* authenticated sessions. Even though they probably used some stolen credentials (at least one would hope), they must have used their own when they *discovered* it. So the way to find them is to look at the logs and find people who accessed diff acct urls under the same auth token prior to this massive theft. I bet there are not going to be that many of them.

Seriously, they offer credit protection for 1 year??? Like the your personal information that they had stolen from them EXPIRES in one year or something? With all those millions of records at hand, chances are whoever has their hands on this data will not even get to you until 3-5 years from now (good luck proving then that sony had something to do with it:( )

Anyone implying that science is harder than law is probably neither well equipped to do science now knows what law involves. Unless you have an Ivy MBA and are willing to work 100 hours a week for several years, you will NOT be making anywhere close to what junior it personnel makes, "financial mumbo-jumbo" or not.

So what happens then if a particular "open" standard is abandoned and the existing viewers for the content grow insecure?

But back when flash was doing it was asked to do pretty well on relatively crappy hardware, JavaScript was not capable of doing these same things even close to as efficiently on the same hardware.

This is not true, flash was doing much more than mouseovers, and doing it very well on my 1Ghz Pentium 3. The only thing that it was not doing back then is decoding video - ppl were actually publishing vector animations back then. Of course youtube has killed it, and now we get to watch them in low quality.

How come Flash was fine on hardware 7 years ago, but is not suited for modern low power hardware?

No one goes into climate science to make tons of money, so I would guess majority of climate scientists value other things, like making a difference and being right. I do not see how such motivation would make people less inclined to cheat (just a bit!) than one to make more money? especially if the perceived enemy has $$ interests, something that poor grad students do not.