My Meteor app uses Apollo and React. Here are my current Chrome audit stats, including Time to Interactive:
4 Likes
Regarding Firebase:
- When I checked, they were using some tree-based storage which was not appealing to me (I think theyâve changed that).
- It was not easy to customize the onboarding template and flow.
- There was no way to customize the admin panel (add features etc), so it meant we had to build our own
- But most importantly, Iâve used Google App Engine a decade ago and had many pain points when I wanted to migrate my data down the road, so I didnât want to take that path again.
With that said, I do think Firebase has its market as a backend for mobile apps with simple CRUD logic.
With regards to the Auth, we use Meteor accounts. We did build our own auth using PassportJS at one point and it took around 5 weeks (one dev) including testing, I personally think it was not worth it, since the time could be have been spent to add features. The security checklist you shared is very informative, luckily we covered all of it except point 2.4 (secondary data verification).
Same here.
With regards to Time to Interactive (TTI), it is around 2s, this is after code splitting and optimizing the bundle, React apps can easily get bloated with JS code if one is not careful, I like bundlephobia, and use it before adding any React library, there is also bundleWizard and Meteor built-in bundle visualizer. We also use SSR (with data hydration) to get fast first paint. I think this the area where I would give NextJS credit, since theyâve SSR best practices built-in and they made it easier to achieve that performance with React, but again it is not compelling enough of value proposition for us, it takes some effort and knowledge to get this right with Meteor, I think it can be made easier but it is not too hard to do once the optimization is desired, Iâd rather have Accounts done by the framework as oppose to SSR, since it is more sensitive and difficult area as youâve alluded to.
However, if youâre really keen on the very fast TTI, I personally would go with Svelte. The good thing about Meteor that it has differential bundling out-of-the-box, I donât think other frameworks has it yet, which means youâre shipping modern code to modern browsers, thus speeding up the execution time.
Iâm curious about your experience with Parcel (I find it very attractive as well), how do you compare it to something like Meteor?
P.S I checked your website from the medium link, I think it is impressive, you seem to be a very thoughtful person and I share a lot of your views, so keep it up 
.
4 Likes
GraphQL is great. According to surveys about half of its client usage is with library-free http calls. Apollo helps with React integration and optimistic updates. However subscriptions are not as powerful as Meteor pub/sub. The Meteor community has delivered useTracker react hook which should be praised.
4 Likes
I posted about my experience with Parcel here. Back then you didnât seem really attracted by the way 
Summary: itâs really fast, just occasionally CPU gets really high or React components get messed up and you have to restart Parcel (which often still takes less time than a Meteor reload). Itâs not perfect but it really made a difference. Not just the speed, but the hot reloading (keeping scroll position and component state) is a godsend for productivity, it really helps you stay in the flow. You have to experience it to understand what I mean.
2 Likes
Yeah I recall that conversation! thanks for sharing that link, but let us also hear it from @dandv since he seems to have first-hand experience with it.
I personally like Parcel as a build-tool, but we ended up with webpack for a project last year since it was more flexible. However, I do find parcel intriguing, and I unfortunately didnât have the opportunity to use it in any major project, and I probably wonât now that Deno is here with its own bundler and Rust. Deno for sure will be my new go-to for side projects/experiments.
Sidenote: I personally find it a little strange how you keep discarding things people recommend (like Next.js and Parcel before), but at the same time are eager to jump on/recommend new, unproven tech you often havenât even tried yourself (Svelte, Deno, âŚ).
3 Likes
We do have hot reloading with large Meteor projects, we run webpack in parallel when doing front-end work, for medium React project, Meteor refresh is good enough. However, Iâm willing to invest money to see HRM API first-class in Meteor as I mentioned here, I think it needs to be there and it is a limitation now especially with React Fast Refresh (the previous hot reload was not reliable most of the time).
Iâve not rejected Parcel, I just didnât have the opportunity to try it in a major production project. Iâve used NextJS, and I just didnât find its value proposition compelling enough (at least for me) and Iâve mentioned my reasoning above several times, feel free to respond to my question about NextJS value here, perhaps Iâm missing something. With Svelte, the benchmarks are very clear. I try to do my own research, try the tools with side projects, and form my opinion while trying my best to filter the hype.
However, I do think Deno has a lot of potential down the road as I explained in that thread.
2 Likes
Really just a matter of setting a token with a cookie or localStorage.
I agree with you, few people want to own security.
No such thing as neither nor.
I wonder if this is neglectable if there is no attack surface for xss / csrf
I have no personal experience with this by the way. For me, app with accounts â> Meteor 
2 Likes
Having played this from every possible angle at this point, the truth as I see it is that Meteor is the best developer experience, pound-for-pound in the industry. But, developers (whether we want to admit or not) are obsessed with the new-and-shiny.
Is there any technical reason to not use Meteor in 2020? No, unless youâre being fussy. Having built everything from tiny toy apps to big olâ systems, you can do it with Meteor if you want to and know what youâre doing.
The only consistent reason people donât want to use it is that itâs not the prom queen anymore.
14 Likes
I have asked number of developers on twitch about their thoughts on Meteor, their response has been mostly, âThe core team left to work on Apolloâ itâs like the project is abandoned, other thing is they criticize Mongodb a lot , âlack of relationshipsâ will bite you down the line.
Their opinions of meteor is based on out of date information and lack of knowledge of how Mongodb works.
3 Likes
Iâve used Parcel to bundle an admin-style app built with with Webix (side note: Webix is another tool from the âamazing productivityâ category; orders of magnitude faster to build admins interfaces with it than with anything else Iâve tried, and highly declarative no-BS code - search for anything in the top right at https://snippet.webix.com/, e.g. âside barâ); too bad they suck at marketing and open sourcing). Hot reloading was great, and thatâs where the comparison between Parcel and Meteor stops, since Meteor offers so much more. I havenât seen Meteorâs hot reload in years so I canât make an informed comparison.
Gatsbyâs hot reloading works the same way, preserving scroll position and component state. Very convenient indeed.
For me it would be âofficialâ PWA support, though according to the last blog post, thatâs coming.
Exactly. Sadly, lots of uninformed opinions and popularity bias (though not entirely unwarranted, given the risk of libraries falling out of maintenance) in the JS ecosystem.
2 Likes
We have one production system (built in 2016/2017) thatâs full Meteor and Blaze, including mongodb, pub/sub, accounts, and everything. And it works great, getting to ~100k users / month and still doing fine with a single EC2 node as an app server.
For our latest project however, Iâm just using Meteor as a build tool, and use React with a REST API provided by feathersJS connected to a postgresql backend. Itâs a great build tool, but leaving the comfy confines of the Meteor environment reminds me just how many problems Meteor solved years ago that the JS community is still grappling with today.
Itâs 2020 and Iâm still dealing with rolling my own accounts system. And reading tons of blog posts and articles about how to manage data access with a redux store and a REST API leaves me wishing for the simple pub/sub mechanism of Meteor that automatically provides local caching, expiration, record merging, sync, and optimized network transfers without a single line of extra code.
I have a serious case of javascript fatigue, and itâs annoying to see all these shiny new toys that everyone keeps talking about while basic functionality like accounts systems and data management are considered too unsexy for frameworks to focus on. Leaving complex data management optimization, or account security best practices, as an âexercise for the userâ while touting a few tenths of a second reduction in time-to-paint benchmarks seems ass-backward to me.
So why am I not using Meteor fully? For me, it comes down to the ability to build a team. In 2016 / 2017, it was fairly easy to find JS developers who were experienced with Meteor. Now, itâs extremely difficult. Even previous developers that we worked with, when we get back in touch with them about working on new stuff, tell us they havenât touched Meteor projects in years and have moved on to other frameworks. Iâm scared to start a new project with Meteor and then be unable to find developers. Meteor is different enough (especially with the way pub/sub and reactivity works) that it takes developers, even ones comfortable with JS, at least a few months to really grok how pub/sub is different than REST APIs. While Iâm willing to train new developers, I canât be sure theyâll actually become good Meteor developers and unlearn the principles of the other frameworks they know.
Thatâs my biggest reason for âwhy not meteor in 2020â 
But to that, Iâd add maybe a controversial idea: 90% of websites these days donât need Meteor or even much of javascript. Before Meteor, I used Ruby on Rails to create static sites. And again, itâs amusing when people write React/node.js SPAs that are actually pretty basic static websites. Even many âadvancedâ websites are often primarily a static website with a few interactive bits that can be easily managed in a couple of limited scripts and AJAX calls.
In fact, for my current site, I wrote my prototype in Rails, because itâs an even better ecosystem, with well maintained gems for just about every problem you have, and only recently rewrote it in React when we better understood the features our early users needed, and decided that interactive and dynamic features were truly necessary and made an SPA worth the hassle.
So perhaps Meteor is stuck in an anti-sweet spot: those who chase shiny new features without regard to utility seem to hop to the latest greatest thing. And those who want a well-engineered full stack solution with a robust ecosystem choose Rails / Django / Java / etc and other older technologies for the 90% of projects that are little more than CRUD frontends to a big database. Meteor is stuck in the middle: not shiny and new enough (any more) to attract early adopters and momentum chasers; not old and established enough (yet) to attract the stable and boring developers.
The good news is that, IMHO, every framework goes through this transition. I think as long as the meteor ecosystem continues to grow, focusing on solving real problems that people have, then itâll soon cross that valley and be seen as a stable, solid choice by the vast majority of developers that prefer to live a little further away from the bleeding edge.
11 Likes
Rebuild it from scratch in TypeScript on top of Deno, rebrand it âSpaceballâ or something, and problem solved! 
3 Likes
@dandv I agree, although Iâd prefer PlutoJS over Spaceball ;), it would be great for the Meteor community to experiment with Deno and attract the early adopters because it is a technology worth investing in, not just another hyped JS framework, and I think the Meteor community has a lot to offer on that front, as I explained here.
However, Iâd suggest to ignore the momentum/hype chasers, they will spend their entire career chasing with nothing to show, and they are not worth the effort.
@mraju thanks for sharing your thoughts, great read.
3 Likes
Love your post @mraju, hope Tiny is reading this as well (@matthollingsworth), as this seems to be mainly a marketing problem. I agree anno 2020 there is still a space for Meteor (provided it continues to evolve), we just need to lose this image:
Iâve listed some other misconceptions I often encounter in the field here: Introduction, and favour to ask the community! - #19 by rijk
This. Even without accounts, when Iâm working in projects that donât have a Meteor backend and I have to do API requests back and forth to fetch and update data, managing that data in component state manually, feels like going back in time for me. âAss-backwardâ is the perfect word 
While I agree that Meteor doesnât need to change, it works fine, we also should acknowledge that the bar in the industry keeps getting raised. Proper, Parcel/Next speed HMR is more than a âshiny new featureâ, in my opinion this is now table stakes and Meteor needs to keep up.
That said, implementing this would not only get Meteor back to the bleeding edge of dev experience on all fronts, but could also help shake this âMeteor is no longer maintainedâ image. So it might even be double bang for your buck
6 Likes
This Webix thing looks very interesting, I didnât know about it. It even has an open source built-in Meteor real-time pub/sub integration! thanks for the reference.
2 Likes