Live data from Hacker News

Hamlet: A type-safe Haml template engine for Go

github.com

11–20 of 42 posts

Re: Hamlet: A type-safe Haml template engine for Go

#11
post #6

That's great; Haml is one thing I like most when doing web development on Ruby/Rails. The only thing I don't like about this implementation is the blocks with inline code: - if user != nil { %strong The user exists - }

Couldn’t you do without the angular brackets?

    - if user != nil
      %strong The user exists
(That being said, the indentation bit also tripped me up in the past)

Re: Hamlet: A type-safe Haml template engine for Go

#14

The example has left me with a strong impression I should avoid this and HAML. That syntax frightens me.

there is a better side by side of the syntax here https://haml.info

(i've been using haml for 17 years lol. if I'm going to need a template language, i find it more enjoyable to read and write than everything else)

Re: Hamlet: A type-safe Haml template engine for Go

#15
post #8

The example has left me with a strong impression I should avoid this and HAML. That syntax frightens me.

It looks unnecessary. The syntax is ugly and by looking at the examples I can’t say what problem it is supposed to solve.

I love Haml / Pug / Slim. I think it's very clear what problem it solves: you don't need to worry about closing tags, and doing it in the right order, because the tree is visually in front of you. It also means less code (because of no closing tags), which means it's easier to read.

It's like HTML but less verbose, less errors prone (

foobar

is impossible to write), and basically the formatter is part of the language. What is there not to like?

Re: Hamlet: A type-safe Haml template engine for Go

#18
post #15
post #8

Earlier quoted context omitted.

It looks unnecessary. The syntax is ugly and by looking at the examples I can’t say what problem it is supposed to solve.

I love Haml / Pug / Slim. I think it's very clear what problem it solves: you don't need to worry about closing tags, and doing it in the right order, because the tree is visually in front of you. It also means less code (because of no closing tags), which means it's easier to read. It's like HTML but less verbose, less errors prone ( foo bar is impossible to write), and basically the formatter is part of the languag…

Why invent a new language so you don't have to close tags? Do I miss something?

Re: Hamlet: A type-safe Haml template engine for Go

#19
post #15

Earlier quoted context omitted.

I love Haml / Pug / Slim. I think it's very clear what problem it solves: you don't need to worry about closing tags, and doing it in the right order, because the tree is visually in front of you. It also means less code (because of no closing tags), which means it's easier to read. It's like HTML but less verbose, less errors prone ( foo bar is impossible to write), and basically the formatter is part of the languag…

Why invent a new language so you don't have to close tags? Do I miss something?

> so you don't have to close tags

Re: Hamlet: A type-safe Haml template engine for Go

#20
post #15

Earlier quoted context omitted.

I love Haml / Pug / Slim. I think it's very clear what problem it solves: you don't need to worry about closing tags, and doing it in the right order, because the tree is visually in front of you. It also means less code (because of no closing tags), which means it's easier to read. It's like HTML but less verbose, less errors prone ( foo bar is impossible to write), and basically the formatter is part of the languag…

Why invent a new language so you don't have to close tags? Do I miss something?

sure, I guess lighting the house with fire also works!
Post reply on HN