4 ms·

Vue.js is heavily magic and doesn't support basic React concepts like render props. How is that possibly a popular framework? Like any "easy" library, you'll ru

by nawgz 5y ago

Vue.js is heavily magic and doesn't support basic React concepts like render props. How is that possibly a popular framework? Like any "easy" library, you'll run into hard situations with no solutions.

searchableguy 5y ago
What do you mean? Vue has slots which is similar to render props. https://vuejs.org/guide/components/slots.html#scoped-slots https://vuejs.org/guide/components/slots.html#scoped-slots
- nawgz 5y ago
  After a read, I guess it does. A developer I respected claimed it was not easy to pass components down like this. Now I no longer respect him. Also, I still don't respect vue. Look at this abomination <MyComponent v-slot="{ text, count }"> {{ text }} {{ count }} </MyComponent>
  - pcthrowaway 5y ago
    You can respect that developers you respect are humans who make mistakes and misunderstand things. As you've done, you've made an inaccurate claim and learned from it. Hopefully you still respect yourself. Also (and I'm not familiar with Vue to know if this is the case), the state of software is such that you can make a claim and have it invalidated a few days later after an update comes out.
    - nawgz 5y ago
      > You can respect that developers you respect are humans who make mistakes and misunderstand things No I can't. Seriously, it was a joke, he's my best friend, but I guess I misunderstood his claim or he misunderstood render props! From what I can see reviewing Vue's 2.x docs, they seem to have had this "slots" idea for a while. I get a little bit ill from looking at that syntax though so I think I'll refrain from arguing about the library again!
AlfeG 5y ago
I understand all this traction with Composition API, and don't liked it at all first time. Whenever I need to go and fix some bugs in old Vue 2 app without CompositionAPI and setup syntax - I feel very bad. Guess that Vue team a bit failed to properly describe why to use composition api, but now I think that it seems to be useful a lot

by nawgz 5y ago

searchableguy 5y ago

What do you mean? Vue has slots which is similar to render props. https://vuejs.org/guide/components/slots.html#scoped-slots https://vuejs.org/guide/components/slots.html#scoped-slots

nawgz 5y ago
After a read, I guess it does. A developer I respected claimed it was not easy to pass components down like this. Now I no longer respect him. Also, I still don't respect vue. Look at this abomination <MyComponent v-slot="{ text, count }"> {{ text }} {{ count }} </MyComponent>
- pcthrowaway 5y ago
  You can respect that developers you respect are humans who make mistakes and misunderstand things. As you've done, you've made an inaccurate claim and learned from it. Hopefully you still respect yourself. Also (and I'm not familiar with Vue to know if this is the case), the state of software is such that you can make a claim and have it invalidated a few days later after an update comes out.
  - nawgz 5y ago
    > You can respect that developers you respect are humans who make mistakes and misunderstand things No I can't. Seriously, it was a joke, he's my best friend, but I guess I misunderstood his claim or he misunderstood render props! From what I can see reviewing Vue's 2.x docs, they seem to have had this "slots" idea for a while. I get a little bit ill from looking at that syntax though so I think I'll refrain from arguing about the library again!

AlfeG 5y ago

I understand all this traction with Composition API, and don't liked it at all first time. Whenever I need to go and fix some bugs in old Vue 2 app without CompositionAPI and setup syntax - I feel very bad. Guess that Vue team a bit failed to properly describe why to use composition api, but now I think that it seems to be useful a lot