> Very true, it has less I/O delays but for now our app is going to be
> light on database I/O and instead comparatively heavier on CPU
> computations ( I think so, can anyone confirm? ). I can add about all
> the single threaded nature of node.js to tell how that makes it bad use
> case but my real reason of hesitation with node.js is below.
I am not exactly sure if the computations are on the server side. Once you
have the .obj file on the browser, most of the
rendering will be done on the browser itself. (Point me if I am wrong).
Computations will be on the server side if there is an option to render the
frames on the server.
Node being single threaded is one of its biggest advantage. Deadlocks are
eliminated from the scene and handling a single
thread is much easier. Plus to take advantage of multicores, node.js has
now included the cluster module
(http://nodejs.org/api/cluster.html). It sets up multiple node workers that
can listen on a single port and compete to
accept new connections.
There could also be an option to maintain a database of the geometry or
.obj files (example http://www.turbosquid.com).
The user could directly select the model from the cloud and upload his work
as well. Node could come in handy here.
> Yes, same language across the web is great but we must admit that
> express framework is not as powerful as Rails, Django, CakePHP or
> Laravel specially when it comes to simple CRUD apps.
Node has a very active community and its coming up very fast. I can't think
of anything you can do in php, django, rails that you can't in node.js. A
lot of organisations are already using node. Yahoo uses Cocktail, a forked
version of node.js & Mozilla uses Playdoh, a forked version of Django. So
there are enough large scale projects using newer frameworks.
The V8 interpreter is faster than those of PHP, Ruby and python and with
Google backing it, it is expected to get even better. Javascript on the
frond end and back end would be a lot more cleaner and easier for the
developers.
This discussion could go on for ever but I think node (or django/ruby)
would be a better option for such a large scale project. :)
------------------------------------------------------------------------------
CenturyLink Cloud: The Leader in Enterprise Cloud Services.
Learn Why More Businesses Are Choosing CenturyLink Cloud For
Critical Workloads, Development Environments & Everything In Between.
Get a Quote or Start a Free Trial Today.
http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktrk
_______________________________________________
BRL-CAD Developer mailing list
brlcad-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/brlcad-devel
