@timriley I still use ERb.
I used to be really into HAML until I started getting into AngularJS where you make heavy use of custom attributes (e.g. ng-foo="bar") and HAML didn't make that nice to use. I don't do AngularJS these days, but I never got back into alternative templating engines either.
It looks like Slim has great support for custom attributes out of the box.
@timriley ERB here. No allegiance or anything, just do!
@timriley ERb for me. With Emmet it’s about the same amount of typing but you mostly see the final HTML.
@citizen428 I've seen this Emmet thing mentioned around the place. I think it's time I look into it!
@timriley At my last job it was erb.
I think because they didn't want to learn something new. 😒
@janko We prefer erbse in dry-view because it has sane block capturing out of the box (without any need for using capturing/buffer concat helpers), and this is an important aspect of dry-view's rendering features.
Erubi offers this too, with its capture_end engine, but the syntax is unusual.
Given dry-view works with all tilt-supported engines, we need to do a little work to help the user ensure a compatible engine is available. See https://github.com/dry-rb/dry-view/pull/106 for more details.
@timriley I've tried several (slim, haml, etc.), but extra cognitive load (how will this translate to HTML?) vs. erb has generally pushed me back to erb
@timriley ERB too, because it’s built-in and close to the HTML output, which I prefer over abstracting it away like HAML does, for example. I don’t have much experience with Slim, though.
@timriley only working with Haml, love it's abstractive syntax and obligations like indentation, it is restrictive but produces cleaner html tree. Worked a lot with erb, but since I hate working with HTML, I feel inconfortable working with it.
@timriley me... still erb... what is Slim
Server run by the main developers of the project It is not focused on any particular niche interest - everyone is welcome as long as you follow our code of conduct!