All 5 comments
Alpine isn't intended for this. Alpine is designed to work with your existing markup, using a Vue-like syntax. Adding templates requires some sort of compiled / transpiler and heavier bundles.
ryangjchandler
on 13 Jan 2020
Alpine would be a life saver for us. This won't save us any problems more than it will generate. In Vue for example, at the end of the day you will find yourself dealing with xMB bundles. Then, you try to solve the issue by using a static site generator for SSR and code splitting or worst, a custom back-end implementation for SSR. Then you use nodejs with PHP for SSR which doesn't make sense at all. We shouldn't do the same mistake over and over. Let's get back to Regular DOM for the sense of our minds.
the94air
on 14 Jan 2020
Alpine would be a life saver for us. This won't save us any problems more than it will generate. In Vue for example, at the end of the day you will find yourself dealing with xMB bundles. Then, you try to solve the issue by using a static site generator for SSR and code splitting or worst, a custom back-end implementation for SSR. Then you use nodejs with PHP for SSR which doesn't make sense at all. We shouldn't do the same mistake over and over. Let's get back to Regular DOM for the sense of our minds.
馃挴. Keep your DOM, forget the VDOM. Everyone's lives are so much easier!
ryangjchandler
on 14 Jan 2020
Alpine would be a life saver for us. This won't save us any problems more than it will generate. In Vue for example, at the end of the day you will find yourself dealing with xMB bundles. Then, you try to solve the issue by using a static site generator for SSR and code splitting or worst, a custom back-end implementation for SSR. Then you use nodejs with PHP for SSR which doesn't make sense at all. We shouldn't do the same mistake over and over. Let's get back to Regular DOM for the sense of our minds.
馃挴. Keep your DOM, forget the VDOM. Everyone's lives are so much easier!
Well then, i invite you to visit any other big website/webapp (like youtube) and look at it's rendered page source. It's easier to roll your own components, rather than stumble through ids and classes.
aolko
on 15 Jan 2020
I think alpinejs + grapesjs snippets could just solve all this.
Worstcase, you could get creative with importing templates and modules.
Does alpinejs work with template-tags?
https://www.html5rocks.com/en/tutorials/webcomponents/imports/
coderofsalvation
on 29 Feb 2020
Related issues
adinata-id
路
4Comments
zaydek
路
3Comments
dkuku
路
5Comments
BernhardBaumrock
路
3Comments
hkan
路
3Comments
Most helpful comment
Alpine would be a life saver for us. This won't save us any problems more than it will generate. In Vue for example, at the end of the day you will find yourself dealing with xMB bundles. Then, you try to solve the issue by using a static site generator for SSR and code splitting or worst, a custom back-end implementation for SSR. Then you use nodejs with PHP for SSR which doesn't make sense at all. We shouldn't do the same mistake over and over. Let's get back to Regular DOM for the sense of our minds.