jasoncodes
commented
11 years ago We agree that removing Haml as a dependency would be beneficial to Postmarkdown adoption. This is however a low priority issue for us.
For convenience of Haml users, we should keep the Haml templates for the generator (in addition to new Erb templates) and use these if the host Rails app has Haml installed. Postmarkdown itself would always use the Erb templates.
I'll leave this issue open and update it if we do any work on it.
philipjoubert
sassydumplings
I'm just mooting this; I recognise it's a personal decision, but hear me out :)
I recognise that many people prefer Haml, which is completely fine. It's also completely possible to use Postmarkdown as it current is with Erb templates in my app, since Rails will happily load and render either. However, there's currently no way to include Postmarkdown within an app without also installing Haml.
I think it's a good principle for any library to have only the dependencies that it really needs, so that when it is integrated into other applications there is as little chance as possible that any of the library dependencies interact with the application dependencies in unexpected ways.
It's a totally valid perspective to say "well, we like Haml and we always use Haml so having Postmarkdown generate Haml templates is more convenient for us". I just suspect that losing Haml as a dependency will make the library more attractive to more people, particularly those who are trying to minimise the number of dependencies their application ends up with.