Not quite, because they will invariably have to be backwards-compatible to some degree, and code reuse (which will happen) will have the negative effect that bugs can be found for older versions by inspecting the new.
They stated certain things had to happen and would cost so much that the benefits of open source. I said that isn't true. This should be obvious because Microsoft is a company that makes money, they don't give things away for free of this magnitude without very good reason - they obviously believe the costs (which are not nearly as egregious as purported, especially early in a project, especially if they had made these considerations before) are justified.
So I object to the notion that all of those costs are so significant or upfront and I object to the notion that they're doing this with no intention of benefiting (which I have no problem with).
All of the things mentioned are easy to account for, cheap, or already a cost of business ie: a legal team is not hourly for Microsoft, documentation is something a contractor can do in a few weeks even for very large projects, fairly cheap, etc.
Now, where I was mistaken is in how new the project is. I had thought it was younger but someone pointed out it's older than I had realized. So the costs will be higher if they hadn't prepared for this, but, again, not 'unrecoverable'.
Regardless, and more importantly, I'm not particularly interested in discussing it, because it seems really boring.
-19
u/staticassert Dec 05 '15
It's pretty easy to do it when you're so early in a project.