News for hackers. Stuff that matters.

A comment on Why we chose Vue.js over React. Parent comment

Re:Why we chose Vue.js over React by jmcdiesel on Sunday December 11, 2016 @01:13PM (#13152246)
After making some simple <If> <Loop object="">, etc custom components.... I've wondered why they don't exist in react by default, or arent the common pattern.

They are very readable... maybe people just dont like the "logic" in a tag... i guess... whatever, made for some really readable code...

[ Parent | on HN ]
Re:Why we chose Vue.js over React by jetter on Sunday December 11, 2016 @01:37PM (#13152377)
Regarding <If> component - here is the guy that suggested this and then admitted that this is a bad approach in a long run: http://stackoverflow.com/a/26152067/1132016
[ Parent | on HN ]
Re:Why we chose Vue.js over React by straye on Sunday December 11, 2016 @02:10PM (#13152569)
Using <If> combines the worst aspects of custom SGML template markup languages and the complexity of React but with additional runtime overhead.
[ Parent | on HN ]
Re:Why we chose Vue.js over React by natmaster on Sunday December 11, 2016 @01:44PM (#13152416)
Turns out javascript is a quite reasonable language and already does that great.
[ Parent | on HN ]
Re:Why we chose Vue.js over React by madeofpalk on Sunday December 11, 2016 @10:31PM (#13155287)
I would rather 'regular' JS functions like .map() rather than React-specific functions like <If> and <Loop> (not to mention the namespace clash with existing JS keywords)
[ Parent | on HN ]