>
> It's not about meteor being good or bad, I like meteor as a framework
> but I am actually a bit concerned about use of packages which comes
> with it's own merits and demerits. Basically about updating overhead
> and dependency upon package manager.
I think it should be more about meteor being a good fit or not for your
project.
Here are a few thoughts on meteor.js:
1. For the time being, on meteor.js you're more or less stuck with MongoDB,
there are *ways* to get it working with other databases but at the stage
the framework is right now, it's an unpaved road. Getting it to work with
other databases is not a feasible task if you're not a Meteor master
already. Why do I mention this? Because if the project is going to be
hosted on sourceforge you're going to have to use a MySQL database [1].
This might not be the case, Sean will have to shine some light on this
matter. This is something you should definitely take in consideration.
2. It might be overkill, unless you really want to turn the project into a
single page app [2] (which is meteor's feat of strength). Also keep in
mind, meteor is in preview status right now (hasn't reached version 1.0)
and there will be periodic updates.
All the best,
Mihai
[1] http://sourceforge.net/apps/trac/sourceforge/wiki/Project%20database
[2] http://en.wikipedia.org/wiki/Single-page_application
------------------------------------------------------------------------------
"Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE
Instantly run your Selenium tests across 300+ browser/OS combos.
Get unparalleled scalability from the best Selenium testing platform available
Simple to use. Nothing to install. Get started now for free."
http://p.sf.net/sfu/SauceLabs
_______________________________________________
BRL-CAD Developer mailing list
brlcad-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/brlcad-devel
