How we do Vue: one year later (2017)

Re:How we do Vue: one year later (2017) by jimmy1 on Monday March 18, 2019 @07:55PM (#19426595)

I have to agree with this. Ultimately whether or not you like Vue or React better boils down to if you agree with the semantics of the web, and including them in your app building process (i.e you like html, and css, and just want to "pepper" in some logic and interactivity with JavaScript), or if you would rather just embrace JavaScript whole-heartedly.

Vue relies too much on overloading the string type for my taste (fundamentally, all JS libs do this to some extent). Too much magic happens with these string-based v-bindings.

Irrespective of that, these days I am hard pressed to not use typed JS in some form or fashion anyways.

[ Parent | on HN ]

Re:How we do Vue: one year later (2017) by dpisk on Monday March 18, 2019 @09:17PM (#19427184)

As far as component libraries that start from HTML, I think Marko has the best syntax. Attributes are always parsed as JS expressions, for example. There's still some quirks, but overall it's pretty nice. https://markojs.com/docs/syntax/

There are some benefits from just embracing JavaScript though, especially, as you mention, integration with things like TypeScript.

[ Parent | on HN ]

Re:How we do Vue: one year later (2017) by pbowyer on Tuesday March 19, 2019 @03:32AM (#19428797)

That attribute syntax is awesome! I've found VueJS's handling of attributes to be somewhat confusing, sometimes getting a different type passed through than I was expecting. Marko takes the approach that would least confuse.

[ Parent | on HN ]

Re:How we do Vue: one year later (2017) by enraged_camel on Monday March 18, 2019 @08:52PM (#19427020)

>>Irrespective of that, these days I am hard pressed to not use typed JS in some form or fashion anyways.

What do you mean by "anyways"? I use TypeScript with Vue and it's great.

[ Parent | on HN ]

Re:How we do Vue: one year later (2017) by jimmy1 on Monday March 18, 2019 @09:08PM (#19427124)

Despite whatever framework I use, I believe adding types improves it and reduces bugs, Vue included. (These days I'm favoring ReasonML and that skews me to React, but I believe Vue.js is also available on Bucklescript)

[ Parent | on HN ]

Re:How we do Vue: one year later (2017) by Rapzid on Monday March 18, 2019 @10:46PM (#19427640)

I could see it being great if everyone on the project were writing class components and using JSX. String templates and extended objects?

Mutiny.

[ Parent | on HN ]