Would building a unified scripting language harm your customer-base or give the competitor the competitive edge?
Obviously if you want to lock in customers, go solo which will prevent your customers from easily switching over to the competitor's product (sounds a little like Microsoft tactics) or if you know your product is superior, a collaboration will allow you to get customers from the competitor in which case customers will have the choice to choose which business model suits their needs, make a choice based on the quality of the product as a whole as well as which features they really need instead of being locked into an invisible contract due to the choice they made initially.
Going the collaboration route will also put your company in a position where developers will respect your company (for not being a greedy monopoly monster) instead of boycotting it due to their "moral" beliefs in open standards.
I would say that if possible make it compatible, not so much to cooperate but to compete. Making an incompatible solution would lock you customers in to some degree (you don't have any yet with a lot of scripts - so not much gain), but making a compatible solution keeps the door open for customers of your competition to migrate (they might have some scripts by the time you ship yours). Just my 2cents
I would write something that is specifically tailored towards my own system (don't compromise your technical quality) and then release and fully support a compatibility layer that allows my competitors scripts to run on my system (make it easy for users to migrate).
I'd stay away from doing things that will try to lock people in and cripple them if they move. These tactics worked once upon a time but in this day and age don't really cut it any more. I'd even go so far as to actually (unofficially on fora etc.) help people who are having trouble porting scripts running on my system to my competitors.
Another way to ask the question (and to answer) is to wonder WHAT KIND of script language is DESIRABLE FOR USERS.
If your competitor went a lock-in route with a proprietary scripted language, then please your users (and get a competitive edge) by using a STANDARD scripted language.
Doing so will immensely increase the value of your tool as many persons ALREADY know the scripted language.
发布评论
评论（4）
构建统一的脚本语言是否会损害您的客户群或为竞争对手带来竞争优势？
显然，如果你想锁定客户，那就单独行动，这将阻止你的客户轻易转向竞争对手的产品（听起来有点像微软的策略），或者如果你知道你的产品更优秀，那么合作将让你能够从竞争对手的产品中获得客户。在这种情况下，客户可以选择适合自己需求的商业模式，根据产品的整体质量以及他们真正需要的功能来做出选择，而不是因为因为某种原因而被锁定在无形的合同中。他们最初做出的选择。
走协作路线还将让您的公司处于这样一个位置：开发人员会尊重您的公司（因为不是贪婪的垄断怪物），而不是因为他们对开放标准的“道德”信念而抵制它。
Would building a unified scripting language harm your customer-base or give the competitor the competitive edge?
Obviously if you want to lock in customers, go solo which will prevent your customers from easily switching over to the competitor's product (sounds a little like Microsoft tactics) or if you know your product is superior, a collaboration will allow you to get customers from the competitor in which case customers will have the choice to choose which business model suits their needs, make a choice based on the quality of the product as a whole as well as which features they really need instead of being locked into an invisible contract due to the choice they made initially.
Going the collaboration route will also put your company in a position where developers will respect your company (for not being a greedy monopoly monster) instead of boycotting it due to their "moral" beliefs in open standards.
我想说的是，如果可能的话，让它兼容，与其说是合作，不如说是竞争。制作不兼容的解决方案会在某种程度上锁定您的客户（您还没有任何脚本，因此没有太多收益），但是制作兼容的解决方案为您的竞争对手的客户迁移敞开了大门（他们当您发货时可能会有一些脚本）。
只是我的2分钱
I would say that if possible make it compatible, not so much to cooperate but to compete. Making an incompatible solution would lock you customers in to some degree (you don't have any yet with a lot of scripts - so not much gain), but making a compatible solution keeps the door open for customers of your competition to migrate (they might have some scripts by the time you ship yours).
Just my 2cents
我会编写一些专门针对我自己的系统定制的东西（不要损害你的技术质量），然后发布并完全支持一个兼容性层，允许我的竞争对手的脚本在我的系统上运行（使其成为可能）方便用户迁移）。
我不会做那些试图将人们锁在里面并在他们搬家时削弱他们的事情。这些策略曾经有效，但在当今时代已经不再有效。我什至实际上（非正式地在论坛等）帮助那些在将我的系统上运行的脚本移植到我的竞争对手时遇到困难的人。
I would write something that is specifically tailored towards my own system (don't compromise your technical quality) and then release and fully support a compatibility layer that allows my competitors scripts to run on my system (make it easy for users to migrate).
I'd stay away from doing things that will try to lock people in and cripple them if they move. These tactics worked once upon a time but in this day and age don't really cut it any more. I'd even go so far as to actually (unofficially on fora etc.) help people who are having trouble porting scripts running on my system to my competitors.
提出问题（和回答）的另一种方法是想知道用户需要什么样的脚本语言。
如果您的竞争对手采用专有脚本语言进行锁定，那么请使用标准脚本语言来取悦您的用户（并获得竞争优势）。
这样做将极大地增加您的工具的价值，因为许多人已经了解脚本语言。
没有人想学习一门新语言。
Another way to ask the question (and to answer) is to wonder WHAT KIND of script language is DESIRABLE FOR USERS.
If your competitor went a lock-in route with a proprietary scripted language, then please your users (and get a competitive edge) by using a STANDARD scripted language.
Doing so will immensely increase the value of your tool as many persons ALREADY know the scripted language.
Nobody wants to learn a new language.