Tiny has its work cut out for it. The RoadMaps for Meteor and Galaxy are really good news, better than (at least I) had hoped for. But will the roadmaps be enough to reverse developer perception?
I remember in the pre-1.0 days there were monthly meetups in many cities, multiple podcasts on Meteor, and Meteor was the recommended technology for certain hackathons I attended. Can we get back to that? Or is there a different route more appropriate to today?
The darkest hour is just before dawn.
I just started a job at a development agency, and they also have a strong aversion to Meteor. What they think they know about it is based on its very opinionated full-stack past. They were surprised it even supports React or Apollo. A splashy “2.0” and a marketing push could help to dispel some of that.
They are actually mostly a RAILS shop, and when I did show them what I was doing with Meteor, they said “oh, that’s the rails of node.js”. That’s maybe what Meteor should strive for?
Well, what do you expect if the CEO of the company writes FUD posts and then leaves only one developer on the team? Ben might be genius, but that’s just not enough to keep up the pace as it was before. Anyways, I’m still in and really hope Tiny will give Meteor the love it deserves.
Could you please refer to these posts?
I think @waldgeist refers to this post, which at the time scared away many developers who thought their apps will become obsolete shortly.
In retrospect, one would easily agree that this whole debacle concerning Blaze could’ve been conducted a lot more quietly, and with far less damage.
Yes, that was the post I was referring to. It caused a lot of doubts and uncertainty back then, when most people were still using Blaze in production and React wasn’t even tightly integrated yet.
Just came across this Transmission episode from 15/02/2016: https://podcasts.apple.com/be/podcast/transmission/id1078456050?l=nl&i=1000362991215
It’s quite ironic listening to the excitement for what’s coming, knowing that almost 4 years on we are pretty much still in the same spot
In the episode, Paul Dowman said he was expecting the community to grow at least 50% as a result of the move to NPM, Sashko said internally they expected even more than that.
This was right around the time they started on Apollo I think, Sashko was talking about ‘the data story’ and how what they were going to build around that was going to be a ‘game changer’.
So, yeah, if MDG would have delivered on the promises they made about Meteor back then instead of getting side tracked by Apollo, I think we could be in a different spot for sure. Although my experience reflects @captainn’s, in that much of the reputation I encounter in practice does seem to be stooled by little actual knowledge of the framework. So it might also not have mattered.
It is frustrating though, how they suddenly completely changed course, leaving us stranded without really communicating about it. I’m exaggerating a bit because the framework is still great as is, but listening to this podcast, hearing Ben talking about HMR (again: feb 2016), I can’t help but feel a little sad for what could have been.
That’s not entirely fair.
To clarify, I was referring more to the excitement about how the community and adoption was going to grow, and to the specific improvements talked about in the episode (contributing to core, testing, HMR). It could have been recorded last week in that regard. Genuinely not sour, just saying I understand the sentiment. And listening to this episode did remind me that at some point MDG’s messaging has totally shifted.
But you’re right, it doesn’t help to focus on the negatives, we’re better off investing our energy in moving the framework forward.
I hope the next paragraphs are seen as some positive and productive input
I was reviewing some of the frameworks from the survey and all I see there is hours of wasted time, because of setting up architecture and basic features (that already come out of the box with Meteor) or just miss important functionality that is crucial for our use cases (reactivity). Let’s be honest: If I really want this kind of pain to setup everything from the ground I would go for Java EE…
Besides that I agree that there is few knowledge about Meteor’s current abilities outside of this community:
- No one besides us knows that the survey is built using Vulcan = Meteor. I think no one complained about the quality of the survey website (it worked so well I was really impressed). So let them know about this! “Did you know the famous State of JS survey was built using the tool, which the most participants thought to be outdated?”
- No one besides us knows that Meteor has always been on the edge of the new ecma versions.
- No one besides us knows that you have out-of-the-box support for the major frontends. I mean other frameworks either support excatly one or none (and you have to set it up all yourself again).
- No one besides us knows that you can write using DDP/websocket and HTTP and that you can also use express as middleware by just using one line of code.
- No one besides us knows that you have a full oauth2 based authentication workflow out of the box. This is still taking ages to implement on your own, even with packages like passport
Also some ideas for concrete marketing steps could be
- a new major version, just to show we are far far away from 1.0 days
- a new website with a fresh design, built with Meteor, hosted on Galaxy (shows that you eat your own food and it tastes good)
- an SEO campaign that downranks all those old and deprecated articles
- an improved atmosphere registry where abandoned packages are ranked down
- a curated gallery, where companies and community can submit links to great Meteor websites and apps for promotional purposes
@filipenevola hinted that a new website is already in the works so that’s one item off of your list
We are following everything that is happening very closely and working to revert as much as possible.
It’s also important to attract new people to Meteor. If you read the new Meteor roadmap with this perspective you will see many items related to documentation and tutorials. These items are very important to keep the community growing and to show that Meteor is very up-to-date and a great tool to start new projects.
Again, I’m confident that the future of Meteor is going to be amazing, we already have a great tool and it will be even better in the upcoming years. We need to learn from the past but move forward.
I’m a Meteor user for many years then I understand the frustration but I try to focus my efforts in the future and in what I can do now to help Meteor. Go go go!
@filipenevola I already read the roadmap and I am also confident about the next moves. This was rather a braindump after the survey because I can’t get in my head why devs are currently so hot for static side generators (back to the 90’s?) and serverless / JAM stack (GDPR nightmare) oO"
Thanks, the new vibe you’re bringing to this community is already fantastic!
thank you for your effort
That’s brilliant, also a new
Discover Meteor book that shows how easy it is to build great app using Meteor for beginners!
I will be making a ton of Meteor content in 2020. I’m not sure when to get started, but I’m excited to fill in the void of video tutorials. What kind of content do people think will help the most? I’m planning some basics content with React and some more full stack intense stuff with Apollo, TS & SSR.
Just meteor and react .
This is perfect focus.