It's shutting off the camera. Switching camera on/off has a slight visual delay.
Slashdot videos: Now with more Slashdot!
At the large company I worked for, hooking up personal computers to the network was a terminable offense. So no, you don't give them a login - you don't set this up at all.
The chief reason appeared to be fear of viruses and hackers, but there are many, many more. The hacker front can be a bit obscure: What if your CEO read the article about RSA getting hacked by an excel file with an embedded flash object, and the CIO assures the board that all computers will have flash removed and tasks IT with identifying and removing flash everywhere? How are they going to look having to explain 'well, we got everything, except for the personal computers that we don't have access to'?
Lets say people start relying on the service you are providing with a personal computer under your desk. What if it goes down? Helpdesk will get called, and need to know what to tell the caller so they don't appear incompetent, and need to be able to address the problem. What if IT is required to certify that all of their computers have X patch applied as part of a compliance audit for certification? What if a corporate policy goes out that no computer can run unecnrypted ftp regardless of port # they run it on? What if your company is obligated to ensure that terminated employees can't log in to servers? What if a lawsuit is served and your company is required to provide copies of all records pertaining to meetings with client xyz, and your calendar server has meeting info on it but your IT department doesn't even know it exists? None of these things are unreasonable, but none of them can be done easily if you're allowed to set up whatever box you want doing whatever.
Sure, it makes your job harder if you have to go through official channels to get the things you need to get your job done. But your company needs to be able to get their job done too, and a bunch of random whatever-somebody-set-up-under-their-desk systems makes that really hard.
I miss doing web work with Tcl, but I don't want to support yet another does-this-client-support-this testing and special casing nightmare.
We had a very different system in the US.
Specifically, banks invented a whole ton of things that don't work like that.
Example: "Interest only" loan (you pay 0 principle for say 5 years, at the end of 5 years you still owe everything and your loan expires. Sounds terrible, but if you think the house will appreciate significantly, in five years you will owe X but it will be worth X * 1.5 - boom you now have a 25% down payment automagically when you refi the next loan. The payment can be a fair bit smaller each month if you aren't factoring in "eventually pay the darned thing off".
Fails miserably if the house goes down or even stays about the same and you can't refi. So people 'walked away' from the house - just quit paying, moved out when the bank made enough fuss. Technically they can still owe money, but if they have no money, and lots of people are doing it, who's to collect what?
They also did stunts like short-term adjustable rate mortgages- give you a introductory rate for a while (a few years, a few months, many variations) to get the initial payment down, bump it up hugely when the time is up. You have probably seen something like this with credit cards, now imagine the same introductory teaser offers but on a half a million dollar house. Sure, if you can make the payment for 30 years you keep the house - but the payment doubles or triples after a little while, and how can you keep paying it?
Finally, even with normal loans, people would participate in taking out way more loan than they could afford on the idea that they will make more money later. Banks were happy to cooperate, encourage, even help them lie about their income, sometimes even lie for them with outright fraud, because the bank was paid only for closing the loan and immediately flipped it on to an investor (often quasi-government institutions Fannie Mae and Freddie Mac) who would divvy the loan up and resell it in packaged slices to other investors. So the person making the initial loan wasn't directly on the hook for any extra risk they took on, unless a court could prove outright fraud occurred. Encourages people to play fast and loose with any rules that might be in place because they judge their personal risk to be very very low, and if somebody else takes on extra risk, well, heck, "Buyer beware" and "sucker born every minute" etc.
BCC was killed by spam filters, not facebook.
You know, Netflix's silverlight player runs great on my Mac. I actually prefer it to Hulu's Flash player, because it can maintain full screen on a second monitor, which is a feature they added after complaints in forums. The Flash player got the same complaints, but no fix. Flash users have to hex edit their dll for that feature.
I was worried about suboptimal multi platform support, but in this one useful-to-me-example, I haven't seen it. Have you seen other features where it's a problem?
I see they are currently #1 on bing for Comforters and #4 for dresses. I wonder if it would be possible for the search engines share data on who is cheating?
I'm actually really surprised by the article, that it took so few sites to affect results and that such obviously off-topic links still helped. I thought the algorithms were already smarter than that.
The chains don't have a good supply either. You can find book #4 and #7 in a popular series, and anything else they will be happy to special order for you. But if I'm going to be ordering and waiting for things, why shouldn't I just do it myself online and save some money and avoid having to drive back to the store?
From the article summary, this is a *500* page book on the topic of using an app framework with a packaging system.
How can that topic take 500 pages? It sounds like it should be a 2 page FAQ? What does a packaging system change so much that it needs 498 more pages?
How does this jive with Google's study that higher temps didn't seem to really cause hard drives to fail in their data center? http://static.googleusercontent.com/external_content/untrusted_dlcp/labs.google.com/en/us/papers/disk_failures.pdf
I'm pretty sure their HR department has a zero tolerance policy on stealing from the company. How much money do I have to be worth before the rules don't apply to me anymore? Do you really think it's only unacceptable to steal if I'm on the bottom half of the org chart?
My 5.7L V8 gets 23 mpg average in daily driving. I figure that's good enough that I don't need to trade it in over green guilt for some lawnmower that might get 5mpg better. Further improvement gets real diminishing returns, cars are only driven so much each year. See for example http://green.autoblog.com/2009/07/23/greenlings-where-are-the-most-important-mpg-increases-at-the-u/
Do you really want them to teach you 140 characters at a time?
Aren't web pages (blogs, RSS feeds, wikis, forums) a better way to actually convey information?
Ships aren't cheap, and marine environments are rather hostile (salt, water), and data centers can already be reasonably mobile by putting it in a shipping container and moving that shipping container somewhere... so what need is this filling?