WorkerBee

I'd believe that when I hear that - I'd be flabbergasted if he can convince me in more than one of the three main accents of Cape Town, South Africa.

Hollywood actors have tried and failed to do a convincing South African accent. the only one who came close enough was, surprisingly, Leonardo Dicaprio

Do you find that this trade-off is in the iPad's favour? i.e. that you never read in strong light, but all the books that you read require animation?

The next time anyone offers a homoeopathic drug, ask them how long the medication is good for. There is no sensible answer to that question, because homoeopathy is gibberish.

Even if water could absorb influences from the homoeopathic medicine, what about all the other things that this water has been in contact with over the centuries? It's not even internally self-consistent.

In the words of W.CV. Fields "I never drink water, fish fuck in it."

This sounds like a good description of Silverlight out-of-browser applications. I wonder why he didn't mention them.

Except that it wasn't. Germany 4, England 1. The wrongly-disallowed goal would have given England 2.

And Argentina 3, Mexico 1.

This is because interop with OpenId, OAuth, RDF et al is hard so hey, lets go shopping! ...I mean, lets roll our own from scratch, that always works.

But what about openness? http://news.cnet.com/o-reilly-amazon-must-open-the-kindle/

That's the official line, anyway. The whole issue of who is a citizen, and who has merely been there for years is part of it.

They were desperately poor before they went to Saudi Arabia, the Saudis merely gave them a marginally better option.

the Saudis gave them what looked like a marginally better option.

Do they? The Saudi Arabian ruling classes do very well indeed, but how does the average Saudi do? Hint: google "Saudi Arabia inequality" and "Saudi Arabia oppression". It's the resource curse at work.

In summary: "If it's a core business function -- do it yourself, no matter what."

Building runtimes (and a web browser is a runtime for web apps) is a core business function to Microsoft.

But no, it's not easy, unless things like OAuth and OpenId implementations are easy to you, which puts you in a very select group.

What about all the other distributed social media experiments, which have been around longer, done more, and are working with established protocols? I still think that this is the real way forward.

"When I last thought about it, I became convinced that we don't need an single implementation, we need standards for multiple implementations to interact. Stuff like RSS, OpenId, OAuth, etc. It's a lot less glamorous to work to these, and to try to push them forward, but it's a lot more useful."

When I last thought about it, I became convinced that we don't need a single implementation, we need standards for multiple implementations to interact. Stuff like RSS, OpenId, OAuth, etc. It's a lot less glamorous to work to these, and to try to push them forward, but it's a lot more useful.

- operates on lists of objects, not database queries.

- operates on small quantities of data. It doesn't matter if there are only five items in a list. If you have to filter them, you have to filter them

- is not that complex.

We use foreaches as well, or a combination. LINQ is great for automating simple things, e.g. turn a loop to find an item into a .FirstOrDefault(x => x.SomeCondition). It would be interesting to see if, as our grasp of LINQ improves, we run into any of these supposed corner cases. But it hasn't happened yet.

var foo= new List<int> {1, 2, 3};

var bar = foo.Select(x => x*2);

Entirely subjective. To me, "#(= (:" is pure line noise.

I disagree entirely. I know when I'm using LINQ to SQL, and when I'm using LINQ to objects. My experience is that LINQ to objects is more common and very useful. He's using larger data volumes than I generally am, so there's absolutely nothing "toy" about it.