HAML vs Asciidoctor: What are the differences?
Developers describe HAML as "HTML Abstraction Markup Language - A Markup Haiku". Haml is a markup language that’s used to cleanly and simply describe the HTML of any web document, without the use of inline code. Haml functions as a replacement for inline page templating systems such as PHP, ERB, and ASP. However, Haml avoids the need for explicitly coding HTML into the template, because it is actually an abstract description of the HTML, with some code to generate dynamic content. On the other hand, Asciidoctor is detailed as "An open source, pure Ruby processor for converting AsciiDoc documents or strings into HTML and other formats". It is a fast, open source text processor and publishing toolchain for converting AsciiDoc content to HTML5, DocBook, PDF, and other formats. Asciidoctor is written in Ruby and runs on all major operating systems .
HAML and Asciidoctor are primarily classified as "Languages" and "Text Processors" tools respectively.
HAML is an open source tool with 3.44K GitHub stars and 545 GitHub forks. Here's a link to HAML's open source repository on GitHub.
What is Asciidoctor?
What is HAML?
Need advice about which tool to choose?Ask the StackShare community!
Why do developers choose Asciidoctor?
Sign up to add, upvote and see more prosMake informed product decisions
What are the cons of using Asciidoctor?
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
When we rebooted our front-end stack earlier this year, we wanted to have a consolidated and friendly developer experience. Up to that point we were using Sass and BEM. There was a mix of HAML views, React components and Angular. Since our ongoing development was going to be exclusively in React, we wanted to shift to an inline styling library so the "wall of classnames" could be eliminated. The ever-shifting landscape of inline CSS libraries for React is sometimes difficult to navigate.
We decided to go with Glamorous for a few reasons:
As you may or may not know, Glamorous has ceased active development and been mostly superseded by Emotion. We are planning to migrate to either Emotion or @styled-components in the near future, and I'll write another Stack Decision when we get there!
Personally, I really like HAML. Not having to use open and close tags is a huge time saver. As a result, writing markup with HAML is much more pleasant. HAML essentially forces you to be very strict about spacing, organization, and structure. It also makes the markup easier to read. Protip: I use this pretty frequently: htmltohaml.com