mcmc

As I've been slowly recovering from back injury/surgery over the past few years, I've been unable to sit for long periods of time. In order to be able to write software at all I've had to construct a laying down desk where I look up through a glass table at the monitor.

I wonder, does this improve my odds wrt to the article? Or rather, is it that 6+ hours of waking inactivity increases the likelihood of premature death? (either sitting or laying down)

Note the extra querystring arguments in the url: ?utm_source=feedburner&utm_medium=feed&utm_campaign=Feed%3A+Techcrunch+%28TechCrunch%29&utm_content=My+Yahoo

I wonder if replicating this stuff messes up techcrunch's metrics significantly?

"With node.js... you really, truly and most awesomely don't worry about race conditions."

Most of node.js's fanbase well and truly believes this nonsense, that you can't have race conditions simply because there is no pre-emption of your running code. In fact, single-threaded, event-based logic can very easily end up in situations where the timing or ordering of network frames impact a response in an unanticipated manner.

IANAL, But this doesn't sound entirely correct.

Youtube is operating as an OSP under the DMCA safe-habor laws, and this has been upheld in court. Youtbue must therefore act neutrally in each case -- that is, they have obligations both to the uploader and the alleged owner. If they don't fulfill these obligations, such as reinstating a video that doesn't actually violate copyright law (given the existent of fair use,) then they can lose their protection under the DMCA.

Granted, Youtube could opt to not seek protection under the DMCA, but it seems like this isn't their best strategy.

I ran a non-profit called ossline for a while (www.ossline.org) which helped open source projects with contributor license agreements, so I am familiar with the issues.

I don't understand this "no way in hell I am signing a contract just to contribute to an open source project" sentiment. It is trivially easy to do (see Node.js's CLA which is an entirely electronic form,) and it gives the users all sorts of additional protections that traditional open source licenses can't otherwise provide, such as patent royalty protections.

The downside of these CLA agreements is that it allows the controllers of the project to re-release code under a less stringent license, and in some cases a commercial license. I can see someone becoming upset that code they worked on in a GPL project was later released as BSD, but that doesn't seem to be an issue with the OP.

All in all, the only reasonable take away here can be summarized in a sentence: "Diaspora may have a more limited uptake by corporations who are hesitant to open source proprietary additions to the software."

Certainly nothing to write a rant over.

If you need real-time web/network/mobile work done, I have a ton of experience and love doing it. (SF/Bay area, telecommute okay)

- I wrote Orbited (www.orbited.org) - Designed WebSocket handshake (officially recognized by w3c/html5) - Comet session protocol (http://orbited.org/csp) - Hookbox (www.hookbox.org)

I've worked on pretty much every type of related app you can imagine (games, stock tickers, chat, collaboration)

contact: see profile

It seems like it is a fair comparison; why do consumers care what MS's target market is, except insofar as it affects a product they want to buy?

I suppose this is why many people prefer Ben and Jerry's ice cream to Safeway.

This is a cool demo; props to the guys who made it.

I have done a few demos like this, and it turns out to be surprisingly hard to turn it into a product. For instance, just because you can send over changes to the DOM, you can't necessarily reproduce the javascript side-effects, exactly. You can't just poll the state of the DOM because it doesn't reflect all of the state that lives in javascript closures that you can't even see.

One easier method, and probably what they did in this demo, is simply catch any user-generated event in browser A and re-emit it in browser B, thus letting the existing javascript code / browser logic do any actual DOM/state modification.

But what happens when each user triggers an DOM event at the same time? They end up getting applied in reverse order on the two browsers. In many cases this can cause the two browsers to fall out of sync.

Anyway, I love seeing WebSocket demos, and this is pretty fun. Just be sure you realize what a rabbit hole this is if you want to make a product.