| > My only point in mentioning apollo-tools is that DSLs are very powerful, and have the potential to make complex problems much simpler. Yes. But just because it has that potential, doesn't mean that Vue's DSL(s) are not without the many problems anf gotchas I described. Just because Apollo's/GraphQL's DSL is potentially good, doesn't mean that Vue's is. etc. > It's not a question of "better" or "worse". It's a question of tradeoffs on spectrum of abstraction.
> I'm not here to bash JSX or react. But you apparently are, and I'm just trying to open your eyes a bit. My eyes are wide open. Where in JSX I see a uniform approach that works in all JSX contexts, in Vue I see several DSLs bound together by magic of the library. > @ and : are just short hands. That's like saying: what's the difference between `map` vs `reduce` Shorthands mean: - new syntax. For all intents and purposes it's a new syntax (call it a DSL syntax). And you have to know the difference and gotchas of that syntax. You have to know where you can: -- provide a thing that looks like a function ref -- provide a thing that looks like a function call -- provide a thing that looks like a bound variable -- provide a thing that looks like a Javascript expression etc. etc. etc. And that is further compounded by the fact that `v-` attributes sometimes take single Javascript-like expressions, sometimes not (v-for), some have additional "arguments". some have additional modifiers etc. etc. And of course, some of it is Javascript expressions inside strings (`v-` attributes), some of it is Javascript-like (but not really Javascript) DSL inside mustache's curly braces (inside tags). So here's the original statement that started this thread: "The amount of special cases in Vue templating syntax is comparable to the special cases and gotchas of JSX" This is demonstrably provably patently not so, as this thread has demonstrated. |