Ask HN: Is Meteor.js still a thing?
61–70 of 107 posts
Re: Ask HN: Is Meteor.js still a thing?
#62Over the years, I've built the equivalent of those real-time systems using postgres, redis, rabbitmq and node that can scale horizontally. It's obviously longer than using firebase, but at least I know what's going on under the hood, I can easily optimize and debug it, I can add any missing features or switch any tools (I.e. can easily switch off postgres to something else if I needed it).
It's for the same reasons that I use React on the front-end. It's great for the view layer, but I still get to pick and use great libraries for the rest of the app (in-memory database, state management, routing, etc etc.) I can easily switch off React to something else because the surface API that I'm using is extremely small.
I would still use meteor or any of the competitors for a hackathon or prototype, but never for a long-term project. YMMV
Re: Ask HN: Is Meteor.js still a thing?
#63Re: Ask HN: Is Meteor.js still a thing?
#64If you look at some quite active meteor open source repos with a non-trivial size, you may also see that meteor is still alive and kicking. ;-) * WeKan - FOSS Trello clone https://github.com/wekan/wekan * Rocket.Chat - FOSS Slack clone https://github.com/RocketChat/Rocket.Chat * Vulcan - React, GraphQL & Meteor toolkit https://github.com/vulcanjs/vulcan * 4Minitz - FOSS Collaborative Meeting Minutes and Protocols Web…
Thumbs up for Rocket.Chat, love it!
Re: Ask HN: Is Meteor.js still a thing?
#65I speak from personal experience when I say companies are migrating away from Meteor. For me personally it's to a React/RxJS front-end stack in combination with a traditional Ruby/PostgreSQL/REST api back-end. This had the disadvantage of losing the back-end reactivity Meteor is known for, but at the same time it's a much more stable, decoupled and scalable stack. Meteor simply felt too much like a black box that cau…
Tangent here, but I see this combo a lot and I don't understand what RxJS is adding to the equation on the front-end. What were/are your motivations for using RxJS?
Re: Ask HN: Is Meteor.js still a thing?
#66Earlier quoted context omitted.
Firebase Cloud Firestore is new product from Firebas and is much more flexible than Firebase Realtime Databse. It can do accomplish that query. From the docs a similar query: citiesRef .where("population", ">", 100000) .orderBy("population") .limit(2) https://firebase.google.com/docs/firestore/query-data/order-...
if you scroll down: citiesRef.where("population", ">", 100000).orderBy("country") is invalid... EDIT: sorry got confused & posted wrong example (population/population vs population / country)
> Invalid: Range filter and first orderBy on different fields
But I can’t find any documentation on what exactly the limitations on orderBy are.
The reference docs on queries don’t mention any limitations on order_by: https://cloud.google.com/firestore/docs/reference/rpc/google...
Re: Ask HN: Is Meteor.js still a thing?
#67So much hate for Meteor here, but I use it at work and it's been great for what we wanted. I inherited a vendor-built website that was Craft CMS (a Yii framework) sitting atop a Laravel application that was integrated with Google Maps and indexed by Solr -- debugging even a minor issue could take days. Meteor is fast and full-stack, no more knitting together 13 different frameworks. It's integrated with Apache Cordov…
> Is Meteor the answer for everything? Of course not. It sure does claim to be.
Promotion/marketing speak is promotion/marketing speak.
Re: Ask HN: Is Meteor.js still a thing?
#68I speak from personal experience when I say companies are migrating away from Meteor. For me personally it's to a React/RxJS front-end stack in combination with a traditional Ruby/PostgreSQL/REST api back-end. This had the disadvantage of losing the back-end reactivity Meteor is known for, but at the same time it's a much more stable, decoupled and scalable stack. Meteor simply felt too much like a black box that cau…
> React/RxJS front-end stack Tangent here, but I see this combo a lot and I don't understand what RxJS is adding to the equation on the front-end. What were/are your motivations for using RxJS?
Re: Ask HN: Is Meteor.js still a thing?
#69Earlier quoted context omitted.
> React/RxJS front-end stack Tangent here, but I see this combo a lot and I don't understand what RxJS is adding to the equation on the front-end. What were/are your motivations for using RxJS?
We use RxJS for data loading and global state management. Started with redux first, but really disliked all the boilerplate code. RxJS enabled us to have a really smart data loading and caching mechanisme that automatically pushes changes to all streams that rely on a particular piece of data whenever that data changes. No need for reducers, selectors, actions, constants or sagas. Just components with one or many RxJ…
Re: Ask HN: Is Meteor.js still a thing?
#70Contrary to many here, I feel over the last year they made themselves totally relevant again. And I think that the negative reactions here are from people that aren't fully aware of the current state of the project. Note that Meteor is much more than a data layer. Even though you won't find any easier system to deal with reactive data than their livequery system, I get that you don't want to be bound to Mongo or even…