\nIn the realm of web development, anytime you start using some software platform to deal with the tedium of writing web pages by hand, it’s quite often it leads to some sort of templating system to handle it.\n<\/p>\n
\nWhile nice in theory and can promise many things (Seperation of logic from presentation, blah blah blah) from the standpoint of someone trying to use these systems it’s more like being thrown a new language every week.\n<\/p>\n
\nAs a personal anecdote, when I started learning Zope<\/a> there was the promise that DTML<\/a> would be the tool that would solve all one’s problems when working with Zope. However, as was often than not there were always these small things that got in the way like:<\/p>\n So in the middle of it all I learned about this new fangled and shinier system called Zope Page Templates<\/a> (ZPT) for short. I never really learned it that much as I was finally coming to terms with using DTML without being a complete newbie. Of course this ended up being a major hindrance to understanding this nice CMS package built on top of Zope called Plone<\/a> however after this, I ended up moving on and not bothering much with Zope.\n<\/p>\n \nSo how much of that built up knowledge did I get to take with me? About zero. Sure I could pick up yet another template language system that came along but that required once again to go through the docs and find out how to write something as basic as if<\/em> again since it wasn’t EXACTLY the same. Anyways, my current view is that learning more templates is not on one of my higher priorities these days unless it gets me something I want and is rather portable. So seeing something like Hobo<\/a> and something called Liquid<\/a> that supposedly is tied in somehow with some Rails Blog app called Mephisto<\/a> isn’t making me that enamored with some parts of Rails.\n<\/p>\n \nDHH<\/a> captures it very well in \nThe pursuit of “no code”-templates reminds me of the search for the holy grail of the MDA camp with “no code”-programs. It’s mirage, but its also a play on words of the “a rose by any other name…” variety.\n<\/p><\/blockquote>\n Amen.<\/p>\n","protected":false},"excerpt":{"rendered":" In the realm of web development, anytime you start using some software platform to deal with the tedium of writing web pages by hand, it’s quite often it leads to some sort of templating system to handle it. While nice in theory and can promise many things (Seperation of logic from presentation, blah blah blah) […]<\/p>\n","protected":false},"author":703,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1101,1215,972],"tags":[],"class_list":["post-593","post","type-post","status-publish","format-standard","hentry","category-geek","category-gripe","category-programming"],"jetpack_featured_media_url":"","_links":{"self":[{"href":"https:\/\/archive.blogs.harvard.edu\/hoanga\/wp-json\/wp\/v2\/posts\/593","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/archive.blogs.harvard.edu\/hoanga\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/archive.blogs.harvard.edu\/hoanga\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/archive.blogs.harvard.edu\/hoanga\/wp-json\/wp\/v2\/users\/703"}],"replies":[{"embeddable":true,"href":"https:\/\/archive.blogs.harvard.edu\/hoanga\/wp-json\/wp\/v2\/comments?post=593"}],"version-history":[{"count":0,"href":"https:\/\/archive.blogs.harvard.edu\/hoanga\/wp-json\/wp\/v2\/posts\/593\/revisions"}],"wp:attachment":[{"href":"https:\/\/archive.blogs.harvard.edu\/hoanga\/wp-json\/wp\/v2\/media?parent=593"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/archive.blogs.harvard.edu\/hoanga\/wp-json\/wp\/v2\/categories?post=593"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/archive.blogs.harvard.edu\/hoanga\/wp-json\/wp\/v2\/tags?post=593"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}\n
\nhis blog post on templating languages<\/a><\/p>\n