By big applications i mean applications with large code base that should be able to scale and with high performance on both client and server side .
Ask HN: Is Meteor.js mature to enough to use it for building big applications?
1–10 of 61 posts
Re: Ask HN: Is Meteor.js mature to enough to use it for building big applications?
#2Do you ask because you are rewriting an existing large scale application (if so, why are you rewriting and why are you considering a different stack altogether?), or because you are starting a new application (there is a 95-99% chance it will never need to scale so the question is not terribly important unless it's between this and one similar technology for some reason)?
Re: Ask HN: Is Meteor.js mature to enough to use it for building big applications?
#3Yes.
Whether it's a good idea? Who knows. Depends on how the ecosystem will develop. Currently it's impossible to judge its health and growth reliably because of the massive hype surrounding it.
But the question isn't really whether it's mature enough. The question is whether you can / want to support a meteor application for the lifetime of the application you're planning to develop. And if you don't, how easy it will to replace you.
Re: Ask HN: Is Meteor.js mature to enough to use it for building big applications?
#4This is a poor question. You are asking a for a lot but providing little. The answer, at the same time, can be yes and no.
You leave out critical information, such as what the scaling is for. Is it to support lots of users or lots of computation? Lots of concurrent connections? Are you talking about meteor.js alone, or are you looking at other technologies? And what is high performance to you? What is a large code base? Why do you presume it will require a large code base?
You provide no requirements, and the question is purely subjective.
But pc86 makes a good point: it probably doesn't matter at this point. With the information you provided, that's the best answer anyone can give.
tl;dr: Yes and no.
Re: Ask HN: Is Meteor.js mature to enough to use it for building big applications?
#5Yes
Re: Ask HN: Is Meteor.js mature to enough to use it for building big applications?
#6As long as you don't get trojan'd when you first install it, I don't see why not.
http://curlpipesh.tumblr.com/post/107681088292/https-www-met...
Re: Ask HN: Is Meteor.js mature to enough to use it for building big applications?
#7No, meteor is still missing quite some, basic I'd say, things.
Have a look at https://trello.com/b/hjBDflxp/meteor-roadmap , but I can make a quick resume for you:
* There is no easy/official way for doing joins in subscriptions (you can't join "Posts" and "Comments" in a typical blog example). I'm aware of several plugins that try to implement that, but they all lack official support and quite of them just fail at doing it properly.
* No server-side rendering. Say goodbye to SEO, unless you're willing to follow the prerender.io way.
* No i18n. Should I say anything at all about this one?
* Not even basic forms support. This is the abc of any framework, and yet Meteor doesn't have it.
* Bad routing support
* Not-that-good documentation and examples
So, no, MeteorJS is just not there yet. But the idea is cool and I'm sure if those things get fixed/implemented, it will get quite a big user-base.
Re: Ask HN: Is Meteor.js mature to enough to use it for building big applications?
#8No, meteor is still missing quite some, basic I'd say, things. Have a look at https://trello.com/b/hjBDflxp/meteor-roadmap , but I can make a quick resume for you: * There is no easy/official way for doing joins in subscriptions (you can't join "Posts" and "Comments" in a typical blog example). I'm aware of several plugins that try to implement that, but they all lack official support and quite of them just fail at d…
You missed that the MeteorJS ecosystem has a lot of packages that take care of i18n, routing support (iron router), SEO (spiderable), basic forms support (autoform).
I agree that there is room for improvement, but I am confident that the team behind MeteorJS will make MeteorJS a success.
Re: Ask HN: Is Meteor.js mature to enough to use it for building big applications?
#9No. Even pagination still requires 3rd-party plugins.
Last time I tried (granted about a year ago) none of the existing plugins were very good (the only reactive one added the new page's items to the table before removing the existing page's items maybe .5 sec later--horrible user experience).
Perhaps the plugins are better now, but still it seems like something so fundamental it should be in the core distro; the meteor team is punting if it isn't. I won't try it again until that is integrated into core, which at least as of a month or so ago, it's not.
Re: Ask HN: Is Meteor.js mature to enough to use it for building big applications?
#10No, meteor is still missing quite some, basic I'd say, things. Have a look at https://trello.com/b/hjBDflxp/meteor-roadmap , but I can make a quick resume for you: * There is no easy/official way for doing joins in subscriptions (you can't join "Posts" and "Comments" in a typical blog example). I'm aware of several plugins that try to implement that, but they all lack official support and quite of them just fail at d…
You missed that the MeteorJS ecosystem has a lot of packages that take care of i18n, routing support (iron router), SEO (spiderable), basic forms support (autoform). I agree that there is room for improvement, but I am confident that the team behind MeteorJS will make MeteorJS a success.
No, I didn't. I'm aware of the existance of those. But those , as you say, external packages are lacking any type of official support. And that is just no acceptable for any serious/big project.
A project manager will be rofl-ing hearing those words, I'd say.