Forgot your password?
typodupeerror

Comment: On topic (more or less) (Score 1) 136

by pancake coil (#42779477) Attached to: Can Proprietary Language Teams Succeed By Going Open Source?
It amazes how quickly things move off topic. The "it's not as good as x" or "only real men program in x" folks really feel a need to hop in. I fall into the category of programmer that makes his extra money programming, the day job pays the rent. I also use the tool, or language, that gets me where I want to be with the least amount of hassle. The world really is big enough for a number of languages.

LiveCode has its place. It is fast and convenient to develop in. The primary issue is its distance to native APIs and raw speed for numerically intensive stuff. If the language doesn't support it, it is a bother to get there. Fortunately, it is rarely a problem.

On to the real question, can this be a successful? Yes, as others have pointed out, it has worked before in similar cases. In the dual license situation, you get the tool for free if you want to give your work away. If you don't, you pay to earn your income. Should it be successful? Yes - it is a very approachable language which is a benefit for those learning to program (the syntax stays out of the way) and, for the same reason, a fast, efficient, and comfortable language to develop apps in if you don't need raw speed.

IF I HAD A MINE SHAFT, I don't think I would just abandon it. There's got to be a better way. -- Jack Handley, The New Mexican, 1988.

Working...