This looks really good, definitely going to pick it up when 8 comes out.
Playing with the 8 previews, I've had problems with the density of not-called-metro-anymore interfaces and a mouse. 90% of this looks workable, and hopefully the rest will follow.
Yeah, that's what I was thinking. Either way you (potentially) have a lot of data to push around, but encoding things as text that could largely be fixed width binary floats really bloats them up.
Destroying Facebook was never what they promised. They promised an alternative. What they delivered was in line with the amount of funding they received.
The people holding Bernie Madoff paper had no trouble standing in line for a share of the recovery, and the people who had gotten too much out had no barrier to getting it clawed back.
The issue with Meteor was that all clients have full write access to the server-side database, including other users' data. Which is problematic, to say the least.
This actually isn't true. One can easily remove the "autopublish" package to disable the behavior of publishing all data to the client, and selectively publish only certain records to the client. Then, all client-side database modification methods can be disabled, and using server-side functions, an authentication system can be built and you can build your application's logic.
As a consequence of its design, HTTP Basic auth wouldn't have worked as expected with meteor. All it could've done is prevented access to the whole website, users would still be able to see each other's stuff.
That almost gave me an aneurysm at the time - I had a first generation iPod touch, and it quickly became less useful app-wise. But long term it was still probably the right move, iOS 3 ran slowly on the first gen touch.