Lpc2000

--- In lpc2000@yahoogroups.com, "Paul Curtis" <plc@r...> wrote:

> We are currently in two (or maybe three) minds as to whether to open up
> the CrossConnect API.  There's good reasons to keep it closed and good
> reasons to open it up.  

I'm sure you understand the pros and cons of opening the interface.

In favor of opening the API:

1. If the interface is open you may sell more CrossConnect parts.

2. You would foster "good will" by having an open interface.

Reasons not to open the API:

1. You might lose a competitive advantage because there would be less
need for people to buy CrossWorks.

2. Further, your competitors might even take advantage of your own
device. They wouldn't make a clone, but rather, if they support your
devices you'd make a small amount on the devices themselves, but they
would get the higher profit margin on selling their software tools to
people who buy your parts.

Obviously #1 on the "in favor" list is mitigated by the fact that you
are not really in business to sell CrossConnect parts. Rather, it's
likely being done specifically as a "value added" addition to help
CrossWorks users. In fact, I am guessing that you're probably making
very little profit selling CrossConnect.

I'm definitely in favor of open source tools (I write some of my own
for the hc11/hc12), but I understand that businesses have to pay
attention to all of the items mentioned above.

We all love to hate the "bean counters", but we also need to eat :-)

Eric