Alpine: See if there are any ideas worth borrowing from Mavo

[carlmjohnson]

Mavo is another Angular-inspired HTML-first framework: https://mavo.io/ Its approach seems to be more all-in-one than Alpine, but it’s probably worth reading the docs and seeing if there’re any ideas worth stealing.

[mblarsen]

Yeah it has been around a long time, and I was wondering if there any experiences to be learned from it.

Aside: litte cool widget built with Mavo https://css.land/lch to illustrate lch

[HugoDF]

Interesting project, honestly I like that Alpine mostly works like I've come to expect from Vue/React with a restricted feature set (eg. No templating, just directives)

[carlmjohnson]

Yeah, reading through it, the only thing that really jumps out to me are maybe property and mv-storage. But they're both coming from the point of view of providing a rich framework instead of letting users build up from primitive pieces.

[SimoTod]

Aside: litte cool widget built with Mavo https://css.land/lch to illustrate lch

A bit less refined since I didn't have much time, but this would be the Alpine version https://codepen.io/SimoTod/full/RwWgWMo

[HugoDF]

Yeah, reading through it, the only thing that really jumps out to me are maybe property and mv-storage. But they're both coming from the point of view of providing a rich framework instead of letting users build up from primitive pieces.

I think persistence is not likely to be something Alpine core ever does, you can mostly reproduce this functionality using localStorage in x-data + $watch in x-init, obviously a bit of boilerplate but it's likely to be a pretty common "syncing" pattern that applies to the URL, localStorage, even a backend server if you wanted.

As it stands, are we ready to close this issue? Might be worth revisiting for v3