Can Proprietary Language Teams Succeed By Going Open Source? 136
JerkyBoy writes "RunRev maintains the proprietary LiveCode programming environment. Those familiar with HyperCard on the Mac would feel quite at home using the environment to produce simple applications, and possibly more, although the programming language it incorporates has a few significant shortcomings (e.g., true object orientation). But it is a very versatile environment, currently claiming support for Windows, Mac, Linux, iOS, Android, and server-side scripting. For us NOOBs who could never find the time to learn C++ and something like the wxWidgets or QT toolkits, it seems like a pretty good deal. Recently RunRev has done something interesting, however, and that is to create a Kickstarter campaign to move the environment to open source (~500K lines of code, ~700 files). The way that they describe it, it sounds like there will be a commercial version and an open-source version of the environment (hopefully not cripple-ware), and they are asking for money to do this. But I want to know: what are their chances of success with this model? How in the world can they make enough money to maintain their programmers and overhead while giving the environment away? In other words, if a company like RunRev announces that they are moving to an open-source model, should you become more interested or less interested in their product?"
Re:Shortcoming (Score:5, Interesting)
Indeed. For example, interestingly, the standard template library (STL) used in many C++ projects is actually a move away from object orientation.
Anyway, I just had a peek at some sample LiveCode source, and noticed that sometimes it approaches human language. For example:
delete the last char of tFilesWithPaths
So, perhaps LiveCode is a move back towards the COBOL days?
Re:Shortcoming (Score:3, Interesting)
Nothing better than writing "Add one to number of gadgets, storing result as number of gadgets." instead of "nGadgets = nGadgets + 1;" or even "nGadgets++;"
If you're so inclined, COBOL is over there [wikipedia.org], and Inform7 is over there [inform7.com] (and it's pretty interesting in its own way).
Seriously, syntax is never the problem, logic and the need to explain every step is the problem.