Part of me wishes they could outlaw these types of things, but I don't really see any way you could logically force someone to make their platform available to competitors.
Part of me wishes they could outlaw these types of things, but I don't really see any way you could logically force someone to make their platform available to competitors.
Almost every action Microsoft has taken in the last 20 years has been about furthering their lock-in. The Xbox exists solely to promote DirectX, which tightens Windows' foothold; other consoles were (and are) mostly based on a derivative of OpenGL, which made it easier to port games to non-Windows platforms.
.NET exists solely to ensure that more business software requires Windows, and Windows Phone exists to ensure that more mobile software requires Windows. Java's write once, run anywhere philosophy is one of Microsoft's main targets, and has been since Java gained popularity in the early-mid 90s. Cross-platform compatibility is the bane of software vendors within their sphere of influence. Since MS primarily sells operating systems and office software, everything they do is about ensuring it's difficult to use a different operating system or office software.
You can go through a similar history for almost every major software vendor. It's in their monetary interest to make it difficult for users to switch platforms, which means it's in their interest to keep your data locked up and/or obfuscated.
Xbox sales were #1 for years - had to be a profit motive there regardless of software 'lock-in'.
.NET maybe, but Windows Phone? Last place in phone sales. How does that lock anybody into anything?
IE supports Java - no lock-in possible there.
Sometimes companies complete by writing software people want to buy. Microsoft has demonstrably done that, and in a market where they are clearly incapable of locking anybody to anything.
Any business' end-goal is profit. With the Xbox, this is through both vendor lock-in and "owning the living room". Some MS exec once also talked about using it as a way to transition the masses of console gamers to PC, but that was probably just a "nice to have" at best.
No. You're confusing sales with profits. The Xbox division lost Microsoft over $3 Billion '03-'12. This has been covered extensively but see eg) http://www.neowin.net/news/report-microsofts-xbox-division-h...
Profit, other than perhaps hope of long-term profit derived from spending their competitors out of business, was certainly not their motivation
Wanting to use something as a lock-in tool doesn't make it one. I'm pretty sure Microsoft would prefer Windows phone to be at place 1.
IE runs Java applets through a third-party plugin, and Java runs on Windows because the Java guys write and distribute a VM that supports Windows. Microsoft already got itself in very hot water for trying to strongarm people off of its platform entirely (Netscape antitrust case), so they're not about to try that again. You can make software for Windows, but Microsoft is going to use their clout in legally "fair" ways to make sure you don't damage their lock-in. Java was a very serious threat to MS, which is why they created .NET and built an enterprise sales apparatus around it.
Sun lost its way and Microsoft ate up most of the custom enterprise software market with .NET. A pity really; the future could've looked much different if Sun had successfully and aggressively countered .NET. MS made sure it didn't happen because write once, run anywhere meant that Windows wasn't going to be very important anymore. .NET touted similar features, but the catch was they only wrote a VM for MS platforms, incidentally.
Pre-reply: Yes, Mono exists, Microsoft made minor contributions here and there to it, but it is now and always has been a second-class citizen in this space, and Microsoft will ensure that it always will be. It seems Mono typically gets support for an API just as it becomes deprecated and its new big brother starts to emerge on Windows. That's intentional.
Why is vendor lock in NOT illegal? (Besides lobbying)
This paints it as more of a societal problem than a legal one, and I think you're correct in hindsight.
I think about my gamer friends, and they've resigned themselves to vendor lockin because "What choice do I have if I want to play with my friends?", something I've come to call the Facebook Argument.
However, when I think about [some of] my colleagues, many of them don't like vendor lockin when it's applied to them, but aren't against implementing similar features in their own projects with a different name, and I have a hard time believing they don't see it for what it is.
Edit: typo
Suppose my only option for earning a living depends on software from Vendor X, who has used lock-in techniques to eliminate their competition. At this point there would be nothing to be done except make vendor lock-in illegal.
It would be easy to do, too, simply by requiring either A. up-to-date, detailed documentation of file formats and protocols necessary for data migration, or B. support for an interchange format that provides the same features as a proprietary format.
This is not to say I'm a fan of vendor lock-in. Quite the opposite, actually. But I do know laws like this will always have unintended consequences, will always be manipulated by those same large companies ostensibly being regulated to give them advantages over new entrants, and, as a result, will always make the competitive landscape more difficult than it would have otherwise been. How big does your market have to be? How big does your company have to be? Is the broadband chip on your phone subject or just your whole phone? What about trade secrets?
The advantage of the antitrust laws is in the lack of specificity. It takes a complete trial to actually show wrong-doing.