Originally Posted by eddiem:
John,
I have to disagree. The subset of people who would want to work on software to do Wifi Control, who use MTH engines, who use DCS, that are into O gauge railroading is not a huge group.
If the codes were published and documented with a disclaimer, I would not complain a bit if they responded to a call from me with, "I'm sorry, but MTH does not provide support for software questions or issues related to 3rd party software."... seems to work for Lionel!
Apple does not provide support for the millions of apps that they sell thru their app store...they make the box, provide a software development kit, and I can write apps for MY iDevice.
Ed
As an IT professional who has spent a large amount of his career in smaller to mid-size manufactuing, eletronics, and semiconductor testing industries, I have to disagree with your disagreement.
Comparing Apple to MTH is, to forgive the pun, apples and oranges. Apple is a huge company that sells millions of devices and has a large resource base to tap in, and in cases, 24/7 worldwide support, not to mention that they (and other software/hardware vendors) by deliberate design, don't always post their support information prominently on their websites (or they at least make you navigate through several links or force you to fill out an online form before you get there) just to avoid those "irrelevant" type of calls & inquiries.
MTH and the other O gauge manufacturers on the other hand, are small nickle-sh*t companies by comparison with resources that are not always in optimal proportion to capacity, and making access to contact support more difficult as other larger software/hardware manufacturers do is not a model that works in such a niche market. It doesn't matter how big or small the group of open source is when you're a company as small as them. With the limited time and resources at your disposal, you want that time and resources helping customers with the products you actually support, and calls received by users with the expectation or lack of knowledge of the degree of support provided by MTH is time and resources wasted, a situation that would only get exacerbated when 3rd party products start cropping up that you opened your architecture up to. Like I alluded to earlier, not everyone reads disclaimers or "gets the memo" and would still call asking for support that you don't provide. Why waste precious time as a support provider and the consumers when you can avoid it? It can also can give the impression to certain customers that MTH doesn't want to be bothered in helping them even if they legitimately don't support that 3rd party product and tell you to call someone else.
Open source has it's place, but it does have its drawbacks, and that includes additional layers of ambiguity and complexity when it comes to end-user support, and that's exactly what MTH has been avoiding by not open-sourcing their DCS command sets.
As for Lionel, well, there were 3rd party TMCC developers like ERR, TAS, DD, etc exploiting Lionel's published command sets, and look what ended up happening to them; they either went out of business or ended up getting absorbed by Lionel.