Similarly, for Templ/Tailwind/AlpineJS components, I’ve recently found https://goilerplate.com.
Show HN: Gomponents, HTML components in pure Go
31–40 of 50 posts
Re: Show HN: Gomponents, HTML components in pure Go
#32Similarly, for Templ/Tailwind/AlpineJS components, I’ve recently found https://goilerplate.com .
Nice! Maybe I should build a small adapter so Templ components can be used with gomponents.
Re: Show HN: Gomponents, HTML components in pure Go
#33Awesome, now do it in Haskell!
There are at least two generations of libraries doing that in Haskell. There was blaze-html and then lucid afterwards to fix some monad laws.
There was also was WASH[1] way before blaze.
Given the minimal syntactic overhead and the do-syntax overload/Monad type class, Haskell is a great language to do these embedded DSLs in.
Re: Show HN: Gomponents, HTML components in pure Go
#34This is a horrifyigly bad idea.
Re: Show HN: Gomponents, HTML components in pure Go
#35This is a horrifyigly bad idea.
:D
Re: Show HN: Gomponents, HTML components in pure Go
#36[flagged]
Re: Show HN: Gomponents, HTML components in pure Go
#37I saw the dot imports and thought “What a neat feature! I wonder why nobody uses it.” Then I googled it and saw a million articles saying how they should be avoided and removed from the language because they make code more difficult to understand.
Typical gophers, can’t accept that there’s a time and place for everything and need to have a hard rule to use that applies to every single situation. Imagine that code, but with gomponents.Ul, gomponents.Li, gomponents.Div everywhere.
Re: Show HN: Gomponents, HTML components in pure Go
#38I saw the dot imports and thought “What a neat feature! I wonder why nobody uses it.” Then I googled it and saw a million articles saying how they should be avoided and removed from the language because they make code more difficult to understand. Typical gophers, can’t accept that there’s a time and place for everything and need to have a hard rule to use that applies to every single situation. Imagine that code, bu…
Yeah, the dot import made the whole thing click for this library. It’s the only use case I found for it so far though. :D
Fun fact: I got the idea from an episode of the GoTimeFM podcast, where the hosts and guests were discussing features they would like to see removed from the language.
Re: Show HN: Gomponents, HTML components in pure Go
#39[flagged]
Yeah, give it a try! It’s weird at first but grows on you IMO.
Re: Show HN: Gomponents, HTML components in pure Go
#40I saw the dot imports and thought “What a neat feature! I wonder why nobody uses it.” Then I googled it and saw a million articles saying how they should be avoided and removed from the language because they make code more difficult to understand. Typical gophers, can’t accept that there’s a time and place for everything and need to have a hard rule to use that applies to every single situation. Imagine that code, bu…
the import is html not gomponents, which imo is fine