Ask HN: Is Meteor.js dead? • Hacker News Board

Re: Ask HN: Is Meteor.js dead?

#91

Post by gremlinsinc » Fri, Apr 13, 2018, 5:47 AM UTC

aogaili wrote: post #62

gremlinsinc wrote: post #35

Probably not dead yet, but in 2018 it makes more sense to use lightweight tools and frameworks that you can easily extend and make your own, and setup microservices. Vue + Koajs might be good if you want to stick with js, vue/laravel go well together, or vue+(pick one: django, phoenix, rails, flask, sinatra, etc...). With react native or ionic framework you can easily built mobile apps for ios/android off the same ap…

so how is vue/laravel any better then vue/meteor, react/meteor or angular/meteor which are all officially supported? react native and ionic framework all can be used with meteor in which meteor can be used as a backend (providing API such as rest, apollo or DDP) and many active projects used this approach.

As far as I know Meteor is losing a lot of support, while I used to like meteor, I wouldn't touch it with a 10 foot pole today because of some of the concerns others have brought up.. I'd say using microservices/api on any platform -python, koa, express, java, go, elixir, laravel, etc.. with vue or react on the frontend is the current trend/best practice.

For me, I know laravel inside/out. For me it's way better because I can build an app in a week using Vue+Laravel. Laravel also isn't coupled to mongodb which, personally I cannot stand nosql db's. There's been so many cases where companies have used nosql and then had to migrate to postgres because they need 'acid', or other features. PG has json data types, so there's no reason not to use it as a doc store within a rdbm.

Re: Ask HN: Is Meteor.js dead?

#92

Post by robeastham » Sat, Apr 14, 2018, 9:31 PM UTC

sgdesign wrote: post #44

013a wrote: post #25

We still use it, though we are phasing it out. In general, its solid for its use cases, but you need to understand what its good at. Its pretty great for small apps, prototyping, hobby projects, etc. There are a few things we learned that I'd share: Use React. Should be obvious. Meteor's react support is pretty great. Stay away from Meteor packages as much as possible. Its better to look for a similar NPM package and…

You could check out http://vulcanjs.org/ , we're trying to get it to be a "Rails for GraphQL/React".

^^ I did lots of research on whether Meteor was the right move for us. I ended up learning about Vulcan.js, which is developed by the Sacha who built the very popular Telegram on Meteor back in the day.

I have to say I'm impressed so far. Lot's of nice things to get one up and running quickly. But it's been thought about in a way that should allow you to mix and match the defaults it comes with in a modular way as your application grows.

With Apollo/GraphQL at its core and React on the front end it really does make a lot of sense given current trends and I'd urge anyone looking at Meteor to check it out. Great active Slack group too.

Re: Ask HN: Is Meteor.js dead?

#93

Post by KajMagnus » Sun, Apr 15, 2018, 1:12 AM UTC

ramezrafla wrote: post #89

anonytrary wrote: post #18

I started using Meteor in 2014. I was active for two years, posting frequently on their forums, writing packages, building MVPs, etc. As I started building more things with Meteor, I realized that it doesn't scale well. It's great for proof-of-concept work. Frameworks can be incredibly productive for low-scale work, but they are painful to scale. No framework that can be simultaneously optimized for every use-case. N…

I respectfully disagree on some key points. - 'key' people left because they were service providers (including Arunoda). When the platform became mature and easier to use, they could not get business. - DDP works great, Apollo is a GraphQL layer, two separate projects and target users. If you have a lot of users you need to design pub/sub carefully regardless of tool. Reactivity makes it a bit tougher, but comes with…

About: "we are the proof" — who are you? :- ) It'd be interesting to have a look at your website or web app or Git repo or something. And, if you have time, I think it'd be interesting with a few words about how / why that shows Meteor works well? E.g. num concurrent users that get pub/sub messages? (Your HN profile is blank, there's a GitHub user though with your username, who seem to do lots of Meteor related work. I'm using Nginx and Nchan for pub/sub messages, and ... I'm curious about Meteor and other things too. No plans to switch from Nchan though.)