Mostly it is about template engines (that hide away real HTML) in Ruby (as due to app runtime specific it is very easy to add pre-compiled "sweets" there, and everybody do it). But in general such tpl engines could exist in any server side language.
I don't like DSLs and abstractions that lead me away from the "origin". Ok, a careful reader have already got what will I write further :)
This post is not about "stop using it" or "it is bad", it is about "reconsider is it really so useful".
Let's start with examples
- Ruby: ERB, Slim, HAML
- Node.js + JS: JADE, Mustache, doT, Swig (it is unified now with Browserify or Webpack)
- PHP: Twig, PlatesPHP, Dwoo, Smarty
This just a small subset of all existing engines, that I have herd of, just to have an examples. Each language has it's specific, but mostly script web languages are good template engenes by themselves.
And I am really absolutely fine with most of them. Except those that force own HTML-replacement surrogate (it is Slim, HAML or JADE like).
body h1 Markup examples #content p This example shows you how a basic Slim file looks like. == yield - unless items.empty? table - items.each do |item| tr td.name = item.name td.price = item.price - else p | No items found. Please add some inventory. Thank you!
And now I'll try to explain this...
Read more ...