News for hackers. Stuff that matters.
Re:Vue.js vs. React by chrisco255 on Saturday August 19, 2017 @05:29PM (#15055728)
Templates have always been nice for basic examples. But now what happens if you only want to show odd numbers in listItem? It's not obviously clear how to do that in this example. Then you start adding in filters or Angular pipes. And the syntax grows in complexity until it becomes unwieldy. If you know the basic rules of JS, you already know how to achieve this with JSX. There's no need to go read the docs.
Re:Vue.js vs. React by LouisSayers on Saturday August 19, 2017 @06:05PM (#15055879)
Haven't used VueJS but the obvious thing to me would be to do your data transformations before hitting the view code - separating view code from business logic.

So is this really a problem?

Re:Vue.js vs. React by chrisco255 on Saturday August 19, 2017 @06:18PM (#15055938)
You don't always want to transform data, sometimes this is merely a UI concern...as in filtering, sorting, etc.
Re:Vue.js vs. React by LouisSayers on Sunday August 20, 2017 @06:18AM (#15057792)
Yeah, so filter and sort it before you hit the view (and by this I mean the markup jsx or whatever) code, and problem solved ;)

Classic MVVM pattern

Re:Vue.js vs. React by ng12 on Saturday August 19, 2017 @07:02PM (#15056108)
Then you're back at OPs original complaint which was that loops take you away from the markup you're currently writing.
Re:Vue.js vs. React by LouisSayers on Sunday August 20, 2017 @06:30AM (#15057826)
Sorry, I shouldnt have said 'business logic' here. I really mean separating presentation and presentation data.