Re:Why Choose Vue.js
by ng12 on Friday June 23, 2017 @06:18PM
(#14623196)
But do you see the inter-dependencies between the script and the template? The template is assuming that it's provided a variable named messages and that it's an array of ready-to-display strings. And this information is stringly typed -- will your editor complain if you fail to define messages? Can I use Typescript to ensure that each message is what I expect? Sure, it's easy enough for simple examples but I've seen it fall apart quickly for large projects with multiple developers.
[ Parent
| on HN ]
Re:Why Choose Vue.js
by true_religion on Friday June 23, 2017 @06:35PM
(#14623277)
I'm not seeing the issue here.
This kind of system is extremely common on the backend---Python's Django and Ruby on Rails, to name a few frameworks follow the practice of templates being given data and simply acting upon it.
Since these are dynamically typed languages, there's no IDE typing support in the template.
There's just testing.
As someone who uses Django regularly, I can say there's a huge swatch of territory between "small examples" and "large projects".
That territory can easily cover teams of 19, and multimillion dollar projects.
Right, it's a common technology and it's always been a pain. With React everything is well-defined and typesafe (either through PropTypes, Typescript, or Flow) and the IDE support is fantastic.
That's my whole contention -- Vue is just a better iteration of the same old painful experience. React actually solves the problems I have.