I’m a big fan of the evolution of the v2 packages into v3 too! And supporting @akryum (sponsor) He has done a really great job on those packages and maybe thousands of devs rely on them if I had to estimate.
I also think the Vue + Meteor community members here benefit from all the cooperation we can give to each other So it kind of makes sense to keep our core efforts on supporting the primary integration. I’m hoping Meteor can really learn how to work as well together as the Vue core team with a large base of contributors and I’m hoping to do everything I can to keep fostering a stronger connection between the Meteor & the Vue communities.
I think we can also really appreciate Meteor + Vue as a very “stable” thing, as a greater priority to becoming a “shinny” thing For me, stability trumps shinny & new any day of the week!
I think it would be really cool for some of us here to try to think about what we can do to make Meteor more attractive to Vue devs. There are SO MANY people using Vue who have still never heard of Meteor , and I do think that will change! An old Meteor user @gusto who is also on the core team at Vue has also been helpful in supporting Vue + Meteor and he listed Meteor as a backend option over on Vue Land (80k+ Discord Community), which was great to see!
@cloudspider I do love the “team up” attitude , we can do great things together! Also @filipenevola has given us A LOT of support & encouragement and I do consider Vue as a 1st class citizen with Meteor, it’s just catching up to React in the Meteor community. We can use Meteor channels (like Twitter, Blog, etc.) to promote Vue + Meteor and get any updates in place we need to make it feel more at home.
Here is a list of things we could start with in the Meteor community, that would really help out:
Vue skeleton config, aka
meteor create --vue (this was started in the community, but not finished yet, and would really help new Vue users trying Meteor for the 1st time, I’ll tag you in Slack were we discussed this)
Meteor + Vue integration testing would be really nice to implement as a community somehow, so we could work together to evaluate the core (component, tracker) & advanced (SSR, Apollo, etc) packages
Issues & PRs that benefit everyone would help out @akryum a lot I think
More docs & examples always help, especially for things that have not been documented well yet, the Vue community really shines in this area, and I think we could do better in Meteor. And much appreciation for you wrting the Meteor + Vue Guide
I support you doing anything you feel you are inspired to do! And I really appreciate anything you’d like to do to keep improving the existing Meteor + Vue foundation!
I’m still very excited about Vue + Meteor, and now recently just turned my main app into an official PWA. It blew my mind to be able to install desktop & mobile versions of my app with only hours of work. So also if you wanted to write about Vue + Meteor + PWAs, that is a “shinny” topic . We could add documentation to that for the Meteor Guide too.
I’ve started, but haven’t made it very far, on a Vue + Meteor GitBook, which I was hoping to focus on the really “easy” side of things to give Vue user trying Metero for the 1st time the tips they need in their projects to make it a breeze. This is a back-burner project for me though, as I still have lots of ongoing user features to build in my main app.
Team work makes the dream work! It’s great to have your support & contributions @cloudspider
I’ve started to invite over 100 devs to try Meteor and I think there will be millions of devs trying Meteor within a couple years. A lot of “web developers” served by Vue, React, Svelte are first developing web sites or very light web apps, which is the largest markets, and Meteor doesn’t even get mentioned in many JS rollups because there is SO much focus on the front-end right now. This Guide is a perfect example of how many web-devs are looking at the world these days. But they are missing the bigger picture. I think a Meteor “re-discovery” trend is starting as people run into shortcoming and complexities with alternatives.