Added Meteor.

[dirkk0]

Hi,

thanks for your website -great approach!

I think Meteor can be considered a 'noBackend' solution as well, since one of the key features is that both client and server code can be contained in one file (if one wants to) and meteor automagically syncs client and server.

Best, Dirk

[gr2m]

Sorry for the late response @dirkk0 and thanks for the positive feedback and the pull request!

I personally don't think that Meteor is a noBackend solution, because noBackend is all about doing frontend only, not touching any backend code, while Meteor is a full stack solution. But at the same time I agree that it goes in a similar direction and we should definitely mention it as another highly interesting solution, that has it's very own benefits.

But I'm not a Meteor expert myself, so please prove me wrong if I misunderstood something. For example, I don't think you can add a meteor implementation of our example app with only frontend code, the meteor backend being hosted somewhere else, can you?

But I also do not want to decide what gets in and what stays out on my own, I'm working on improving the documentation and to allow for a better discussion with the community.

At the moment, I'd just leave the pull request open and get back to it is fast as possible, I hope that is all right?

[dirkk0]

np @gr2m regarding the time :-).

Maybe I didn't fully grasp the noBackend concept and I am in no way a Meteor expert - but: I currently play around with Firebase (like here: http://jsfiddle.net/dirkk0/p9dnT/) and to have a trivial Firebase implementation, you only need to include their JS and save data with messagesRef.push({name:name, text:text} or get it by adding messagesRef.limit(10).on('child_added', function (snapshot){...}.

That's not much to do, but if that passes as a noBackend solution (in terms of you only need to add a couple of lines and don't need to know if you are working against a local or remote DB), then Meteor should pass, too. In Meteor you simply create Collections (a mongoDB) and your client replicates against a server without adding extra code for that. Like in Firebase, the Meteor folks host you application for you which is as easy as typing meteor deploy myApp (you need their environment though). Unlike Firebase you can also host a Meteor application yourself, but of course this is a different discussion.

Btw: I am in no way affiliated to Meteor or Firebase - I am fascinated by both concepts, also I try to look into your example services. Of course it is ok to leave the pull request open - in fact, I would be interested what you and other people think of this issue, and I am glad to stand correct as long as I learn something from it. :-)

[gr2m]

Closing it, as Meteor is not a noBackend solution per definition. But if you're still working with Firebase it would be great to have an implementation of your example app using it