I ran a whole IT department by myself with hundreds of servers. Life was great. I used tools that I understood, was confortable with, were tested over time. Everything ran smoothly. Then new management came in, changed everything, now it takes > 4 admins for twice the number of servers, and we're always behind with tickets and our support is worse. So my answer is "it depends".

          Posting this as anonymous coward adds weight to which side of the argument?

What goes on in the back-end is irrelevant. What matters is that your script is single threaded. All functions are atomic and busy waits will prevent any other JS from executing. If an event happens, the browser will wait until the current function is done executing before notifying the callback for the event. This actually makes programming for JS very easy and does not really hinder the event-driven nature of client-side browser scripting at all. At best, I think you can think of callbacks to the server as worker threads (work is being done by the server), though when your client-side code is called back, it will be sequential and it won't execute concurrently with any of your other code.

It's probably coming from people that have done web browsing.

Pick the best tool for the job. While I'm not a big Microsoft fan -- and I'm even less of an Exchange fan -- you don't pick a server platform because it's your pet O/S; you pick a server platform because it's what you need to get the job done. If you need to run an Exchange server, then build a Windows server (or more likely, several Windows servers) and run Exchange.

From the client side, I use a Linux desktop to connect to an Exchange server for e-mail at work, and it works just fine because it supports standard SMTP and IMAPS. I greatly preferred the Postfix server we used to use (because my organization owned it and therefore I had access to it, unlike the Exchange server that our new corporate overlords mandated), but in truth, I don't really have any major complaints from a user perspective.

Interesting, because I was just reading this:

http://en.wikipedia.org/wiki/Argument_to_moderation

Warning: Links at bottom of page are highly addictive.

Actually it assigns it a value of undefined.

Did that joke just go flying over my head?

Did anybody think to check the power cord?

If justice is unavailable, I'd settle for an "accident". Those happen all the time, and can be quite gruesome.

    Totally off the real topic but Bill Gates actually rates well in the percentage of net
worth donated. http://www.businessweek.com/pdfs/2004/0448_philan.pdf

      The above link doesn't reflect my next unsubstatiated statement but Larry Elison has
historically done very poorly at giving significant percentages of his income.

[root@localhost ~]# nslookup slashdot.org
Server: 208.67.222.222
Address: 208.67.222.222#53

Non-authoritative answer:
Name: slashdot.org
Address: 216.34.181.45

I used to do occasional linux recoveries for a place called Reynolds Data Recovery in Colorado. They weren't a mega-huge recovery company, but they got a few dozen drives every day and did good business. They used a collection of software - some proprietary utilities from the drive manufacturers, some commercial utilities. Also, some drives overheated, so they had a freezer that they could put a drive in, so it ran long enough to copy the data off it, also, they had clean rooms, so they could re-seat heads onto platters if they came off somehow, then they'd run the drive "open" until they could copy the data off. Other times, the electronics (controller card on the drive) were dead, so they had a huge shelf of working controller cards from every possible drive that you could think of. They'd pop the old card off, put in a known-working card, then copy the data off. The data would normally be returned on a 'loaner' drive that the customer would return or a new drive that the customer would pay for. RAIDs were hit-and-miss and sometimes they worked and sometimes they didn't. I'm not sure of any of the names of the software that they used, but it varied depending on how difficult the recovery was.

When I had to do linux recoveries, I slowly built-up a little distro of my own which had tons of tools on it. I'd have my 'distro' on a disk that they could plug in when they needed me to work on a linux disk, then I'd ssh into the machine remotely and work on the disk without having to drive in. I'd fix the partitions or the disk if it was possible and copy the data off onto a backup disk. There are some good tools availble in linux to do recoveries of things, but with the newer filesystems nowadays, it's more and more difficult to get anything off now. I'm not sure about SSD. Never had to deal with them yet. :) ext2, fat, vfat and memory cards, easy. reiserfs & ext3, much more difficult.

Or we could put solar panels on roofs and convert the sunlight, that would ordinarily be
converted to heat, into electricity which I am sure we could find a use for.