Using Meteor as a front-end library
frozeman.de
Using Meteor as a front-end library
1–10 of 14 posts
Re: Using Meteor as a front-end library
#2Thanks for this. I have similar requirements (back-end already provided), which is why it was natural to choose Angular. But with the work done in Meteor 0.6.5 and guides like yours, I would have chosen Meteor.
For those curious as to why I would choose Meteor over Angular: reason #1 is existing familiarity with Meteor, but a close #2 is that I would have to write much less code to accomplish the same things.
Re: Using Meteor as a front-end library
#3Thanks for this. I have similar requirements (back-end already provided), which is why it was natural to choose Angular. But with the work done in Meteor 0.6.5 and guides like yours, I would have chosen Meteor. For those curious as to why I would choose Meteor over Angular: reason #1 is existing familiarity with Meteor, but a close #2 is that I would have to write much less code to accomplish the same things.
I would be very curious to know how the code would be "further" reduced when you move from angular to meteor. Could you elaborate on this point? Are you talking about meteor (backend+frontend ) or just meteor-frontend reducing the code size?
Re: Using Meteor as a front-end library
#4Very interesting. I will give this a try. I've been a fan of Meteor for a while and have worked with both Ember and Angular. I usually end up longing for certain aspects of Meteor in both of those frameworks.
Re: Using Meteor as a front-end library
#5Meteor looked interesting until I discovered it's dependent on node v.0.8.25 :(
Re: Using Meteor as a front-end library
#6Thanks for this. I have similar requirements (back-end already provided), which is why it was natural to choose Angular. But with the work done in Meteor 0.6.5 and guides like yours, I would have chosen Meteor. For those curious as to why I would choose Meteor over Angular: reason #1 is existing familiarity with Meteor, but a close #2 is that I would have to write much less code to accomplish the same things.
I would be very curious to know how the code would be "further" reduced when you move from angular to meteor. Could you elaborate on this point? Are you talking about meteor (backend+frontend ) or just meteor-frontend reducing the code size?
I almost did an edit to my comment to say "less" instead of "much less". Generally speaking, Meteor is less verbose.
Re: Using Meteor as a front-end library
#7Isn't there the spark rendering engine that can be used independent of meteor? https://github.com/meteor/meteor/wiki/Spark
I haven't tried it, but it seems like cleaner approach than cutting the patient in half.
Re: Using Meteor as a front-end library
#8Isn't there the spark rendering engine that can be used independent of meteor? https://github.com/meteor/meteor/wiki/Spark I haven't tried it, but it seems like cleaner approach than cutting the patient in half.
The recent release of 0.6.5 intends to make it possible to take only the parts of Meteor you need while still benefiting from the surrounding ecosystem (i.e. leveraging smart packages like minimongo, deps, and third-party ones like ironrouter).
In practice though, I wasn't able to get a client-side only Meteor example app running, so I'm waiting for Meteor to iron out the rough spots.
In the meantime, techniques such as the one by the blog post author can tide people over.
Re: Using Meteor as a front-end library
#9Did meteor ever fix the big startup delay that makes your app look like a blank screen for 5 seconds when you first browse to it?
Re: Using Meteor as a front-end library
#10Did meteor ever fix the big startup delay that makes your app look like a blank screen for 5 seconds when you first browse to it?
Not sure, but you can time how long it takes to load their site: http://www.meteor.com/
It uses Meteor itself so the framework is sent down the wire and rendered client-side like any other Meteor app.