Hacker News new | past | comments | ask | show | jobs | submit login

"I will use my operating system monopoly to put you out of business if you don't assist me in putting an unrelated competitor of ours out of business" is worse to you than "you may only use Objective C to develop on this device"?

I don't like Objective C either, but I don't take it that far.




Microsoft, as all companies would, is going to use their successful product(s) to push other products that they create. They had 95%+ of the OS market and simply wanted to push the use of their browser to those individuals. That doesn't and never has seemed like a dirty tactic to me. Apple pushes its own products over its competitors on the iPhone. You won't see Opera on the default dock bar on the iPhone anytime soon...it may never even be approved to be in the app store. Microsoft may have made it tough for their competition (and I'm sure they crossed the line many times as you mention) but they certainly aren't telling the folks at Mozilla now that Firefox must be re-written in .Net or they aren't going to allow it to run on their platform!


> Microsoft, as all companies would, is going to use their successful product(s) to push other products that they create

Please, keep in mind that if the successful product is effectively a monopoly, then this conduct is not only immoral. It's also illegal.


Well, Windows Phone 7 only allows verified CLI bytecode apps, which practically speaking means Firefox won't be compiling for it anytime soon.

But MS doesn't care how you compile, just as long as the bytecode checks out safe.


And Windows Phone 7 is not a dominant player in any segment.


"I will use my operating system monopoly to put you out of business if you don't assist me in putting an unrelated competitor of ours out of business" is worse to you than "you may only use Objective C to develop on this device"?

What about this: "I will use my mobile operating system prestige to put your mobile company out of business if you don't assist me in putting a competitor of ours, Adobe, out of the mobile app business".

The word "monopoly" doesn't add much. People could develop for MacOS back then when Microsoft did that, but nobody used MacOS. Likewise, people can develop for Android now, but nobody uses android.


Sorry to be so presumptious but I don't think you've thought this through. Microsoft threatened to drive companies out of the computer industry. There are still plenty of other viable mobile platforms to develop for if the iPhone doesn't work out for you.


What I mean is that it is much more than "you may only use Objective C to develop on this device". You also haven't thought this through. It has many more long term implications than the language choice.

And we have a disagreement about what viable mobile platform means.

For example, "Gameloft sells 400 times more games on iPhone than it does on Android." http://www.pocket-lint.com/news/29757/gameloft-cutting-andro...

There isn't much of a mobile games market outside the iPhone. Unless you want to develop children games for the DS. And then you would need to wear a suit to sign a contract with Nintendo. And guess what, they don't sign more than X contracts a year, where X is a very low number. So you could be out of luck.

The point is that if the iPhone is the most lucrative platform now, it is not in the best interest of the developer to put their eggs in only one basket. And markets change. So they should create demand in parallel in other devices too.

But to port to other devices takes time and money, two scarce resources, as you now.

One way they could be less dependent on the iPhone with minimum investment is to use a compatibility layer like Unity. Unity already works on the Wii, and will work on the Android and Xbox soon, with windows phone probably not far away. But with the new rules, that is not a solution anymore.

Also, it is ironic that Unity will work on Xbox but not on the iPhone. Don't you think?


When the iPhone has 70% of the market, instead of the ~25% it apparently has now, your argument will make sense to me. Until then, you seem to think that Apple has additional responsibilities to the market simply because they're the best current platform. Being the best doesn't mean that.


I would guess they have 95% of the 3D mobile games market now.

And I didn't say they have additional responsibilities to the market at all. I was just making the case that to limit choice of your partners (and, therefore, your consumers) to kill your competitors is evil. It is what Microsoft did with OEMs and it is what Apple is doing with developers.

Is is perfectly possible to kill a competitor without being evil. The best example is Facebook. I don't think Facebook would ban a developer for using a Google API or a compatibility layer that make games work in Myspace too. They even allow multiple payment platforms!


No, they just prevented them from shipping software by default. No OEM was going to say, you know what, Netscape is more important to me than being in business. That's just a business deal. But as a user you could always just install it yourself. It was all about market share, there was no actual limitations on the device. This is about materially impacting WHAT YOU CAN DO ON THE DEVICE, as both a user (certain apps unavailable, this will make it worse) and as a developer. Microsoft never did anything like that on the scale Apple is doing now.


What Microsoft did was in fact so much worse than what Apple is doing that the DOJ sued them for it and won.

I think the reason for the vitriol on this particular issue is that Apple is doing something that computer geeks don't think is correct, and computer geeks can't handle it when people do things "wrong".


Your first statement can't be judged yet. If all Microsoft had ever done was the IE thing, they wouldn't have sued. They had a pattern of anti-competitive behavior and that was the most egregious and well documented example so the DOJ went with it. Apple over the last few years has been fairly anti-competitive, this won't push it over the edge but it is another straw on the camel's back. So lets look back in 10 years and see what happened.

And the 2nd statement could be applied to the whole Opera sueing MS over browsers in the EU recently, or even the IE/Netscape thing back in the day.

Honestly I think it is more people don't like being told they have to waste time and money giving up projects/products they started and learning the tools Apple is arbitrarily forcing them to use. That is money out of people's pocket and you will find that pisses people off a lot more than anything else.


Being anticompetitive is not against the law.

Acting anticompetitively to support a monopoly is what is against the law.

If the DOJ is up on Apple in 10 years, it'll be because their policies from today are so successful that they come to absolutely dominate the market.


Being anticompetitive is not against the law.

Acting anticompetitively to support a monopoly is what is against the law.

If the DOJ is up on Apple in 10 years, it'll be because their policies from today are so successful that they come to absolutely dominate the market. In which case, it would have been practically actionable for them not to have served their shareholders by pursuing those policies.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: