That and also React has a bigger momentum/usage in general. If you look at the usage of Blaze to contrast it too it becomes clear that usually once a project gets started in one it is unlikely that a switch will occur. This also contrasts with a survey on the Meteor forums where React and Vue were reported to have almost the same usage. I think that the survey managed to reach out to people who do not frequent the forums.
I guess I will get into details about it in the follow up article.
Versatile, Passionate and Involved for as long as there is coffee. I'm a Problem Solver, Conference Organiser, Tech Lead and Javascript Developer.
Organiser of Frontend Love and VueJS Amsterdam
Vue is on the rise though. If we can make the switch to Vue 3 and make it a bit more closer to Vue's default way of working, it will be much nice for Vue devs to use Meteor.
With Vue 3 I'm planning to create some hooks that cover Meteor's reactivity system like const cursor = useFind(selector) and const status = useSubscription()
Sadly I'm not familiar with Vue to that extend to say. I think the crucial thing will be the integration package and how well it handles the reactivity and other Meteor features.
That is for example a problem with React that there are some cracks in handling the Meteor reactivity (which might get better in the future, but it is hard to say now).
As my experience, React or Vue both were not good integrated on Meteor. Actually it was not the frameworks matter, it is caused by original blaze and pub/sub structure is too much good to be used.
So I think new user might be prefer to use third party front-end framework to be integrated, but the legacy user will just use blaze way if there's no need for business requirement.
That's why I asked your opinion if I missed something good for Vue updates ^^
Thanks-
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
That and also React has a bigger momentum/usage in general. If you look at the usage of Blaze to contrast it too it becomes clear that usually once a project gets started in one it is unlikely that a switch will occur. This also contrasts with a survey on the Meteor forums where React and Vue were reported to have almost the same usage. I think that the survey managed to reach out to people who do not frequent the forums.
I guess I will get into details about it in the follow up article.
Vue is on the rise though. If we can make the switch to Vue 3 and make it a bit more closer to Vue's default way of working, it will be much nice for Vue devs to use Meteor.
With Vue 3 I'm planning to create some hooks that cover Meteor's reactivity system like
const cursor = useFind(selector)
andconst status = useSubscription()
I've an experice for Vue & React integaration on Meteor, but honestly both were not comforatble to use Reactivity than blaze it is.
Do you think that Vue 3 would be good enough to go if it's improved?
Sadly I'm not familiar with Vue to that extend to say. I think the crucial thing will be the integration package and how well it handles the reactivity and other Meteor features.
That is for example a problem with React that there are some cracks in handling the Meteor reactivity (which might get better in the future, but it is hard to say now).
As my experience, React or Vue both were not good integrated on Meteor. Actually it was not the frameworks matter, it is caused by original blaze and pub/sub structure is too much good to be used.
So I think new user might be prefer to use third party front-end framework to be integrated, but the legacy user will just use blaze way if there's no need for business requirement.
That's why I asked your opinion if I missed something good for Vue updates ^^
Thanks-