FWIW most european countries allow 1-6 months probation periods (for non-temp jobs, temp jobs have either no probation or much shorter ones). During probation, either side can terminate the contract without most of the restrictive clauses applying, it's essentially a short period of "at-will" to check fit between the company and the new employee.
The main reason I view it that way is because Facebook hires a lot of fresh college graduates who don't necessarily have much (if any) money saved up. To work for Facebook, they're going to have to find a place to live in one of the most expensive areas of the United States. I think it is quite disrespectful to put young people with little money in a situation where they are signing extended leases only to be let go within six weeks.
Granted, Facebook gives out pretty good signing bonuses, so that softens the impact a bit, but still if I knew that the first six weeks were effectively a probationary period I'd make a special effort to find a housing situation where I could pay on a monthly basis rather than entering a six- or twelve-month lease.
Moreover, if I had a family, I'd definitely think twice before going into a sort of six week interview, no matter who the company was. I wouldn't want to put my family through the difficulties of moving there only for me to get let go soon after arriving.
If it's not clear that's the case, which seems to have been the case in these anecdotes, it would be pretty unacceptable.
Telling people "Welcome to Facebook," having them quit their old job, and have them relocate just so you can smoke 'em and throw out the trash might be efficient, but it sure isn't kind.
I think, though, if I was running a company, I wouldn't have hack weeks or 20% time - I'd try, for as long as possible, to give people extreme latitude to work on whatever they think might be useful/fun/interesting for the company - more like the Valve model, I guess.
There's another way to do whatever you want at work, and that's covertly. During the times you're meant to be doing other things. Depends where your desk is I suppose, or if working remotely.
On the other hand, those rejected will always have hurt feelings, and at some point their failure will be sealed by the lack of confidence/patience/charity established engineers have for them.
Probably the incumbents are often failing to appreciate the body of domain (FB procedures + code) knowledge they've accumulated, and that a new initiate likely lacks. Engineers are often poor communicators in that sense.
They seek candidates with strong engineering skills, and only do a little culture fit at interview time (this was my experience at least). The real culture fit test happens during bootcamp, where they try for 6 weeks to break any misfit. Now that isn't going to work for everyone, but their strategy is to go all-out and try get a strong candidate to work well in their culture.
It didn't work out for me. I constantly reflect on what made me decide to accept their offer, what I could have discovered that would have made me realise it wasn't going to work out for me. I take interviewing far more as a two-way discussion, trying to find out what a company sees in me that they like and sometimes I tell them they misread me rather than risk ending up in the same predicament.
There are a number of things not directly in my control that lead to me leaving though. I had some bad luck with many of my bootcamp tasks, e.g. task owner on vacation for a couple weeks, task owners not being responsive if I didn't get back to them with working code really fast (I was working on other tasks at the same time), etc. I was drawn in very strongly by a manager who recognised that my skills strongly matched his team's requirements. I felt uncomfortable around that team from day one and never really tried hard on their tasks, and that reflected very poorly on me. At the same time, teams I took the initiative to approach would setup an initial meeting and then I'd never hear back from them. It wanted to dig into stuff I was excited about, while my bootcamp manager wanted me to complete the boring tasks I was assigned. Other things at hackathons drew me in, and I spent too much time on those projects only to be told a week before being fired that those were not being counted in my evaluation so I had to scramble to work again with the team I didn't get along with. Soon after that, that team didn't want to give me new tasks and I was left with nothing.
If I was to go through the process again, there are a few things I'd do differently. I would avoid letting the side hackathon projects take up too much time in the early days until I was firmly settled in. I would get more clarification on tasks as early on as possible. I would focus on one or two tasks at a time, rather than trying to churn through five or six in parallel. This way turn around time with task owners would be faster making them happier to help. I would forget about looking for a team until week four at the earliest - focus on tasks instead. I wouldn't take their advice to pick any team, even if you had no experience in the area, too strongly. It's good to get a strong start, and take the other roads once you've proven yourself.
I found a new job within a month. As an H1-B holder, I needed to be quick, so I settled for what I could get. Companies reacted differently to me being fired. While I'm sure all of them take it as a negative, some seemed to sympathise. I'm now interviewing again, and depending on whether Facebook comes up I have told some companies what happened and not told others. It doesn't seem to make a huge difference, since I've proven myself at my current company, but some keep prodding to try find that fatal flaw in me that lead to the firing (which I don't believe exists). I'm considering removing Facebook entirely from my CV after my next job.