61–70 of 93 posts
MDG has been focused pretty heavily on Apollo for quite some time. I’m not convinced Meteor has been shown much love. The package ecosystem has dramatically declined in quality over the last year.
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…
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.
I built a major project in Meteor last summer, and it was a big mistake. For the most part, Meteor itself is stable and being actively developed, but many of the packages are experiencing severe rot, and one of the developers of a few of the most used meteor packages recently went out of business and took all their documentation down with them.
But can also poorly choose NPM packages, thus the mistake in this case is on the poor choice of third party packages by the developer and not on the framework.
This comes up every so often here on HN: "Is Meteor.js dead?" - 19 days ago https://news.ycombinator.com/item?id=16622231 "Is Meteor.js still a thing?" - 5 months ago https://news.ycombinator.com/item?id=15624623 "Is Meteor(JS framework) is dying slowly?" - 1 year+ https://news.ycombinator.com/item?id=13303345 Personally I still use it but I think MDG made a big strategic mistake in organizing its marketing around DD…
The nice thing about Vue.js is that you can also combine it with Ruby on Rails. For the backend that gives you a very mature ecosystem. At our company that has been a great success https://about.gitlab.com/2017/11/09/gitlab-vue-one-year-late...
Anecdotally, everyone I knew who tried it complained about lock-in (environment too prescriptive and has behavior you can't opt-out of) and no longer uses it. There is development activity in the repo, but I would say the 'hype' has moved to other projects.
Of course if you use all the aspects unique to the stack (reactivity, accounts, blaze, pub/sub etc.) then you'll to re-implement those when switching, but then again that's an architecture choice, you can choose to ignore those and just use Meteor as a build tool.
We spent a fair amount of time going back and forth over whether to use Meteor or not for our in-house development (in late 2017), before we bit the bullet and moved ahead with Meteor. Finding people is the hard part for us as a business, so finding a balance between technology and available skills was a priority. Since Meteor is a public framework, it has a ready ecosystem for onboarding (tutorials, etc), plus with…
This for us is also the main selling point, it allowed us to group client, server, routing, assets, static files all in one package thus enabling architects to split web apps and by extensions teams vertically instead of the typical horizontal split (client/server) thus full functional ownership instead of code ownership.
This architecture pattern is discussed here: https://micro-frontends.org/ and enabled (I believe uniquely by Meteor's build system).
We spent a fair amount of time going back and forth over whether to use Meteor or not for our in-house development (in late 2017), before we bit the bullet and moved ahead with Meteor. Finding people is the hard part for us as a business, so finding a balance between technology and available skills was a priority. Since Meteor is a public framework, it has a ready ecosystem for onboarding (tutorials, etc), plus with…
"Since Meteor is isomorphic, it gives us a very interesting advantage of tying code ownership to both front and backend code, which results in functional ownership not just code ownership. That emphasizes full-stack development, which is a priority for us. Our mantra is to do more with few people as we can, and Meteor lets us do that very well." This for us is also the main selling point, it allowed us to group clien…
Earlier quoted context omitted.
What do you mean by it does not scale well? number of users using it or size of the project?
The server "publishes" particular queries as a kind of feed, and the client "subscribes" to some number of these feeds and behind the scenes, a miniature mongodb-like-api (mini-mongo) in local storage gets filled with all the published data you are subscribed to, so both the number of documents needed should be limited, as well as the scope of the query itself, for performance reasons... Scaling in the sense of: 1) n…
DDP is a simple protocol that runs on top of WebSockets, which runs over TCP. Back in 2013, someone achieved 12 million concurrent WebSocket connections on a commodity server. There is no reason why Meteor should not be able to handle a comparable number:
https://mrotaru.wordpress.com/2013/10/10/scaling-to-12-milli...
Meteor fully supports the NPM ecosystem. Meteor does not have to always use DDP. You can implement RESTful APIs and serve static pages using the many router packages available.
Earlier quoted context omitted.
I’m using it for a side project which has been running for over a year. It’s not something to which I can devote much time and Meteor is easy to set up for what I need. I suppose that if it dies I can re-write the application using some other framework (I’ve done Android/Java and iOS/RubyMotion versions), though it would be a bit of a pain. For now, with no new features planned, I can keep it running as long as the M…
Technically you can run it indefinitely. Meteor is open source and the Meteor team has been actively working with community members to do PRs and what not. There are enough people on it that the ball (to some extent) would be picked up by community folks. Perhaps not a bad thing, either, as it could breathe some new life into it.
>Is Meteor.js dead? Yes.
No. https://github.com/meteor/meteor
Apparently it’s not the only thing that is as good as dead with activity on GitHub.
Meteor might not literally be dead, but it may as well be. Don’t use it. Even MDG seems mostly focused on GraphQL these days (and that sucks, too. But that’s a whole different topic.)