Erlang vs Markdown: What are the differences?
Erlang: A programming language used to build massively scalable soft real-time systems with requirements on high availability. Some of Erlang's uses are in telecoms, banking, e-commerce, computer telephony and instant messaging. Erlang's runtime system has built-in support for concurrency, distribution and fault tolerance. OTP is set of Erlang libraries and design principles providing middle-ware to develop these systems; Markdown: Text-to-HTML conversion tool/syntax for web writers, by John Gruber. Markdown is two things: (1) a plain text formatting syntax; and (2) a software tool, written in Perl, that converts the plain text formatting to HTML.
Erlang and Markdown belong to "Languages" category of the tech stack.
"Real time, distributed applications" is the top reason why over 49 developers like Erlang, while over 345 developers mention "Easy formatting" as the leading cause for choosing Markdown.
Erlang is an open source tool with 7.74K GitHub stars and 2.1K GitHub forks. Here's a link to Erlang's open source repository on GitHub.
Asana, Code School, and GoSquared are some of the popular companies that use Markdown, whereas Erlang is used by AdRoll, Grooveshark, and Heroku. Markdown has a broader approval, being mentioned in 756 company stacks & 718 developers stacks; compared to Erlang, which is listed in 70 company stacks and 47 developer stacks.
What is Erlang?
What is Markdown?
Want advice about which of these to choose?Ask the StackShare community!
Sign up to add, upvote and see more prosMake informed product decisions
What are the cons of using Erlang?
Sign up to get full access to all the companiesMake informed product decisions
Sign up to get full access to all the tool integrationsMake informed product decisions
Markdown represents a highly portable and lightweight text formatting. I had converted all of my Wordpress posts to Markdown prior to migrating over to Jekyll and eventually to Hugo. The fact that many generators support Markdown means that my content remains portable regardless of the platform/engine I use.
What you see is not what you get, never it is.
Documentation is better in Markdown format. You don’t need anything special to read it.
It is compact, portable, comparable.
Markdown is my text file format of choice.
Because it is almost an effortless markup language without ever having to write an HTML tag. Of course, you'll want to use it in environments that make it look pretty (GitHub, etc.)
Using StackEdit to edit markdown files for blog roll and about sections. MD files are stored in Google Drive and pushed to GH pages through StackEdit.