Hacker News new | ask | show | jobs
by beagle3 4696 days ago
open does NOT equal putting yourself on equal footing with your competitors.
2 comments

Actually, yes, it does. If you're giving preferential treatment to your apps that's not possible to replicate, you're not being open.
Proof by contradiction:

Google can close and shutter youtube, Microsoft cannot. Therefore, by your definition, there is no way for youtube to ever be open unless Google commits to irrevocably fund youtube forever and ever. Alternatively, they could give Microsoft the option to close YouTube at any point in time for any reason, just like Google can.

?!?!?

ergo, your definition of openness makes no sense.

We're talking about openness of an API, not open business ownership or whatever the hell you're describing there. An open API gives consumers an equal footing in terms of the API. It doesn't affect any other part of the business.

Don't be willfully dense.

> An open API gives consumers an equal footing in terms of the API. It doesn't affect any other part of the business.

When you get to define terms, that may be. Here on earth, you're just making no sense whatsoever.

I'm not trying to define anything. I'm trying to narrow the use of the term so it doesn't lead to ridiculous contradictions.

When people say talk about something being open, they mean in a specific context. They don't mean that literally the entire business is open and you could wander into their meetings, etc.

It actually does. It not only means that, but its one of the outcomes if you are truly open.

I think a bigger problem here is why people think YouTube or Google are "open" to begin with. There are some areas in Google businesses that being more open than the alternatives (note the emphasis on more, sometimes they are just "open" in comparison with Microsoft and Apple policies) serves them well, thats why the do it, but it's not a dogma inside the company and will never be.

No, it does not mean that. You have things confused.

IF you are at equal footing with everyone else, THEN you are "open". But the other way around does not follow.

e.g. Mozilla (or Digia, or SourceFire, or thousand others -- take your pick) can relicense their open source software as closed source, and put out binaries for future versions without releasing the source. Others using the same source code base cannot. That does not make that source code any less open.

1. 'open source' and 'open' are not the same thing. Look at android being open source but with closed development.

2. The property of being 'open source' applies to specific copies of software. All that 'closed' stuff you were talking about is applied to non-public copies so it has no relevance to the discussion of the open source copies.

> Look at android being open source but with closed development.

But it's still an "open" system by everyone's definition of the word - the source is open, the API is open, everyone is welcome to use it and make changes. It's just that Google is not obligated to accept them into the official tree. Who cares how the development process looks like? Android is open, and claiming otherwise is foolish. e.g. Amazon's Kindle Fire version of Android.

> The property of being 'open source' applies to specific copies of software. All that 'closed' stuff you were talking about is applied to non-public copies so it has no relevance to the discussion of the open source copies.

Do you actually have an idea of how the GPL works? Because what you wrote here indicates you do not. SourceFire (the company that makes Snort) used to provide the source under the GPL, but then continued to develop it and provide PUBLIC copies without source. No one, except themselves (as the right holder) could legally do that. That does not make the open GPL versions any less "open source" or "open" in general.

>That does not make the open GPL versions any less "open source" or "open" in general.

We agree then on that, I think, but it has nothing to do with the API openness so I'm not going to pursue it.