i like-ish the idea of Alpine, maybe, if it sticks around for the next 10 years and adds the functionality it's missing -- functionality that exists in jQuery

i like-ish the idea of Alpine, maybe, if it sticks around for the next 10 years and adds the functionality it's missing -- functionality that exists in jQuery and Vue today. which means i'd be likely to use jquery or vue if i had to choose a tool today for a project i needed to be around in a couple/few years. but that might be a bit too harsh -- if it's so simple then i'd be able to hack on it relatively easily without worrying about which version it was at 5 years from now, or if it really exists at all in any sense -- because i would be able to master all its use cases (so i would not need any support/help), or swap in a new tool. i would say that the answer to the question, 'Why should I use Alpine instead of Vue?' should be something other than, 'The non-VDOM, bro!' i'm sure that's important to some people -- just not me. if you said it's actually truly really much simpler than Vue, then that might be cool. if you said it's much simpler than vue and does a lot less than vue, that might be ok, too -- just tell me what less it does so i know whether to waste my time or not. if it's like jquery, minus a ton of features, but with new/better syntax, that could be interesting. i support it. let's see where it goes. i've never been crazy about the weird 'open' binding/variable/whatever examples/uses -- in alpine/vue/anything. i'm always thinking, is that a variable, or an html attribute, or a standard naming convention of this particular framework, or maybe it's a css property, or a bound tool variable that is named the same as a css property or value, or....