The one thing that golang really needs is a templating library that doesn't suck, Html bindings in this language feel more like an after thought and this is coming from a person that really likes this language.
I spend most of my time in the JavaScript ecosystem, but I've worked with Go and Rails and have been working with Django recently and my take is that this seems to be true for most other languages/frameworks. There are plenty of valid criticisms of React/etc, but the one thing they got really really right was making "templates" be normal functions that return a data structure representing the HTML. Logic is way less…
Show HN: Build progressively enhanced reactive HTML apps using Go and Alpine.js
41–45 of 45 posts
Re: Show HN: Build progressively enhanced reactive HTML apps using Go and Alpine.js
#42I'm currently working with Alpine.js in order to try to build "Universal Components" or "Hypermedia Components". Where you just hit a URL and get your component like /components/infinite-canvas or /components/svg-2-base64 or /components/lib-somelib. [1] ilse.ink/components(It's not ready yet)
Sounds interesting. ilse.ink/components didn't work. Could you post a link to it?
Trying to make universal components is hard, like, I wanted to make all components available trough a "filter" where you could re-use React.js, Vue.js, Svelt, Solid components with each other. When you think about it, components are just I/O with maybe some libraries. I'm thinking this is field is right for some standardization.
Re: Show HN: Build progressively enhanced reactive HTML apps using Go and Alpine.js
#43The one thing that golang really needs is a templating library that doesn't suck, Html bindings in this language feel more like an after thought and this is coming from a person that really likes this language.
I spend most of my time in the JavaScript ecosystem, but I've worked with Go and Rails and have been working with Django recently and my take is that this seems to be true for most other languages/frameworks. There are plenty of valid criticisms of React/etc, but the one thing they got really really right was making "templates" be normal functions that return a data structure representing the HTML. Logic is way less…
Re: Show HN: Build progressively enhanced reactive HTML apps using Go and Alpine.js
#44Earlier quoted context omitted.
Sounds interesting. ilse.ink/components didn't work. Could you post a link to it?
I'm still working in it, but that's going to be the link. Trying to make universal components is hard, like, I wanted to make all components available trough a "filter" where you could re-use React.js, Vue.js, Svelt, Solid components with each other. When you think about it, components are just I/O with maybe some libraries. I'm thinking this is field is right for some standardization.
Re: Show HN: Build progressively enhanced reactive HTML apps using Go and Alpine.js
#45Earlier quoted context omitted.
I'm still working in it, but that's going to be the link. Trying to make universal components is hard, like, I wanted to make all components available trough a "filter" where you could re-use React.js, Vue.js, Svelt, Solid components with each other. When you think about it, components are just I/O with maybe some libraries. I'm thinking this is field is right for some standardization.
Do you know about shoelace?