When comparing LiveCode vs Erlang, the Slant community recommends LiveCode for most people. In the question“What is the best programming language to learn first?” LiveCode is ranked 39th while Erlang is ranked 48th.
Ranked in these QuestionsQuestion Ranking
Pro Fast to get results
Inside LiveCode's IDE you can build for OSX, Linux and Windows, and (making use of Xcode and the Android SDK) for iOS and Android too
Pro Extremely simple to get started
Single-click install of entire development environment, and all-in-one IDE makes it easy to go from visually layout out a user interface to writing code to power it to creating your own single-file applications.
Pro GUI-driven development
In LiveCode, you start by dropping GUI elements into place, then add the code that makes them function. This lets beginners see visual results right away, which is often more exciting (especially for young students). It also lets you focus on the user interaction before you get into the nitty-gritty of code implementation.
Pro Approachable yet capable language
Pro Highest ROI compared to other popular cross-platform development tools
Fluid production - from prototyping to delivery in one toolkit. With a high-level language that includes GUI controls as native elements, code more directly expresses the end-user experience. And the platform coverage is awesome, nearly unmatched.
Pro Built from the ground up with concurrency and distributed computing in mind
Erlang has strong roots with the telecom industry in which concurrent processes are normal. It's designed to be concurrent, to be used for distributed computing and to be scalable.
Fault tolerance means that a system has the property to continue operating even though one or more components have failed.
For Erlang systems, this means that the system is kept running even if for example a user has to drop a phone call rather than forcing everyone else to do so.
In order to achieve this, Erlang's VM gives you:
- Knowledge of when a process died and why that happened
- The ability to force processes to die together if they depend on each other and if one of them has a fault.
- A logger that logs every uncaught exception
- Nodes that can be monitored so that you find out when they go down
- The ability to restart failed processes (or groups of them)
Pro Upgrade code without stopping the system
In a real-time system it may not be possible to stop the system in order to implement code upgrades. For these cases Erlang gives you dynamic code upgrade support for free when using OTP. The mechanism is very easy to understand and works as follows:
- Start the app
- Edit the code
That's all that is needed, the app updates with the new code while it's still running and tests are run automatically.
Pro Great for writing distributed applications
Erlang is made to be parallel and distributed. Because it's very easy to write code that uses multiple processor cores, it's also very easy to write applications that span multiple servers.
Pro Battle proven
Erlang has been used in production for more than 20 years now. During that time it has proven itself over and over again that works great in both small startups and large-scale enterprise systems.
Erlang has been used extensively by Ericsson themselves. For example, the AXD301 ATM, which is one of Ericsson's flagships is probably the largest Erlang project ever with more than 1.1 million lines of Erlang code.
Pro Light processes
Erlang's processes have very little overhead (about 500 bytes per process). This means that a huge amount of processes can be created, even on older machines.
Pro Consistency across platforms
Erlang's processes run in a complete independent way from the OS (they aren't managed by the OS scheduler neither). This means that programs written in Erlang will run exactly the same way regardless of the operating system or platform.
Con fringe use
Con Poor ecosystem
Not a mainstream programming language.
Con Eccentric syntax
Erlang's syntax may feel very strange to 99% of programmers who have never used it. This is because it does not share any similarities or common syntax definitions that are found in all the other languages that are used today.
Con Useful in only one niche
Erlang is not really a general purpose language. It has a very special and well-defined niche where it towers above everything else. It's specialized in scalability and in distributed applications. Which is not necessarily a bad thing per se, but it still lacks and falls behind other languages when it needs to do things outside it's niche.