2 ms·
This is the risk you take with using contractors. When you hire someone to do the work, you are the legal owner. This includes the good and the bad. The good
by mbreese 17y ago
This is the risk you take with using contractors. When you hire someone to do the work, you are the legal owner. This includes the good and the bad. The good being you can make money from it. The bad being that you now have a potential legal liability. When something is done work-for-hire, it is legally just like you produced the work in-house. So from the outside world, Microsoft is the entity that is legally responsible. The contractor is responsible to only Microsoft (and I'm sure their contract includes a provision to deal with this).
What you're describing is a legal nightmare. In this case, imagine that Microsoft didn't pull the plug. What would happen then? Would Microsoft say "Oops, sorry, it was the contractor's fault. But we paid him, and got our code, so we're going to keep using it." They didn't pull the plug out of the goodness of their hearts. They did it because they are legally liable for it, and the longer it was in the wild, the worse their liability.
The rest of this is PR. Plurk maybe pushing this a bit far, but that is a PR decision, not a legal one. From a legal perspective, they might have been injured enough for a lawsuit.