Need advice about which tool to choose?Ask the StackShare community!
Elixir vs Markdown: What are the differences?
- Syntax Complexity: Elixir is a programming language that is more complex in terms of syntax compared to Markdown, which is a lightweight markup language. Elixir requires more coding knowledge and understanding of programming concepts, while Markdown is simpler and more straightforward with its formatting rules.
- Application Purpose: Elixir is primarily used for building robust, scalable, and fault-tolerant applications, especially in the context of concurrent programming and distributed systems. On the other hand, Markdown is mainly used for creating formatted text documents with simple formatting elements like headers, lists, and links.
- Execution Environment: Elixir code needs to be compiled and run on a virtual machine known as the Erlang VM (BEAM), making it suitable for high-performance applications. Markdown, on the other hand, does not require any execution environment as it is interpreted directly by Markdown processors, rendering it for rendering formatted text.
- Dynamic vs. Static: Elixir is a dynamically typed language where variables do not have static types, allowing for flexibility in programming. Markdown is a static format, where the syntax and elements used to format text are predefined and cannot be changed or customized during processing.
- Community and Documentation: Elixir has a smaller but thriving community with extensive documentation, libraries, and frameworks to support developers. Markdown, being a simpler language, has a wider adoption and support across various platforms and tools due to its ease of use and familiarity.
In Summary, Elixir and Markdown differ in syntax complexity, application purpose, execution environment, dynamic vs static typing, and community support and documentation.
#rust #elixir So am creating a messenger with voice call capabilities app which the user signs up using phone number and so at first i wanted to use Actix so i learned Rust so i thought to myself because well its first i felt its a bit immature to use actix web even though some companies are using Rust but we cant really say the full potential of Rust in a full scale app for example in Discord both Elixir and Rust are used meaning there is equal need for them but for Elixir so many companies use it from Whatsapp, Wechat, etc and this means something for Rust is not ready to go full scale we cant assume all this possibilities when it come Rust. So i decided to go the Erlang way after alot of Thinking so Do you think i made the right decision?Am 19 year programmer so i assume am not experienced as you so your answer or comment would really valuable to me
We have a lot of experience in JavaScript, writing our services in NodeJS allows developers to transition to the back end without any friction, without having to learn a new language. There is also the option to write services in TypeScript, which adds an expressive type layer. The semi-shared ecosystem between front and back end is nice as well, though specifically NodeJS libraries sometimes suffer in quality, compared to other major languages.
As for why we didn't pick the other languages, most of it comes down to "personal preference" and historically grown code bases, but let's do some post-hoc deduction:
Go is a practical choice, reasonably easy to learn, but until we find performance issues with our NodeJS stack, there is simply no reason to switch. The benefits of using NodeJS so far outweigh those of picking Go. This might change in the future.
PHP is a language we're still using in big parts of our system, and are still sometimes writing new code in. Modern PHP has fixed some of its issues, and probably has the fastest development cycle time, but it suffers around modelling complex asynchronous tasks, and (on a personal note) lack of support for writing in a functional style.
We don't use Python, Elixir or Ruby, mostly because of personal preference and for historic reasons.
Rust, though I personally love and use it in my projects, would require us to specifically hire for that, as the learning curve is quite steep. Its web ecosystem is OK by now (see https://www.arewewebyet.org/), but in my opinion, it is still no where near that of the other web languages. In other words, we are not willing to pay the price for playing this innovation card.
Haskell, as with Rust, I personally adore, but is simply too esoteric for us. There are problem domains where it shines, ours is not one of them.
Pros of Elixir
- Concurrency174
- Functional162
- Erlang vm133
- Great documentation113
- Great tooling105
- Immutable data structures87
- Open source81
- Pattern-matching77
- Easy to get started62
- Actor library59
- Functional with a neat syntax32
- Ruby inspired29
- Erlang evolved25
- Homoiconic24
- Beauty of Ruby, Speed of Erlang/C22
- Fault Tolerant17
- Simple14
- High Performance13
- Doc as first class citizen11
- Good lang11
- Pipe Operator11
- Stinkin' fast, no memory leaks, easy on the eyes9
- Fun to write9
- OTP8
- Resilient to failure8
- GenServer takes the guesswork out of background work6
- Pattern matching4
- Not Swift4
- Idempotence4
- Fast, Concurrent with clean error messages4
- Easy to use3
- Dynamic Typing2
- Error isolation2
Pros of Markdown
- Easy formatting345
- Widely adopted246
- Intuitive194
- Github integration132
- Great for note taking41
- Defacto GitHub lingo2
Sign up to add or upvote prosMake informed product decisions
Cons of Elixir
- Fewer jobs for Elixir experts11
- Smaller userbase than other mainstream languages7
- Elixir's dot notation less readable ("object": 1st arg)5
- Dynamic typing4
- Difficult to understand2
- Not a lot of learning books available1
Cons of Markdown
- Cannot centralise (HTML code needed)2
- Inconsistend flavours eg github, reddit, mmd etc1
- Limited syntax1
- Not suitable for longer documents1
- Non-extensible1
- No right indentation1
- No underline1
- Unable to indent tables1