22437 Posts in 7073 Topics by 2750 members
|Go to End|
17 March 2011 at 12:51am
I'm very impressed with the new look of SilverStripe v3.0 and the future direction. Well done indeed.
However I have what may seam like a slightly off the wall question, but given the rewrite of SilverStripe has any thought been given to having the back end written or a port to Node.js?
Reason I ask, in my own opinion I wonder if there is a long term future for php as I expect it to be eclipsed by Node. That is unless php pull a rabbit out the hat. (Obviously existing systems need to be maintained but I thinking about brand new developments.)
Just wonder what your thoughts are on this.
9 February 2012 at 6:40pm
I really don't see Node outdoing PHP at any time. Both are very different beasts. Node has its advantages and PHP has theirs. For instance, take a look at CouchApps. Man, those things are awesome, simple, infinitely scaleable and super easy to deploy. One could suggest that CouchApps will outdo Node. However, I doubt that, too In reality, All three are viable options for many projects, but its just as viable to use all three in one app.
I do a shed load of Node.JS development, and it's fun stuff. Node is great for Cloud dev, handling huge numbers of connections and interacting with databases. However, I wouldn't like to use it for heavy file access. In fact, file access can be a big bottleneck for Node. PHP on the other hand is great for file access. Building CMS's in PHP is far simpler and more useful than doing so in Node.JS... Just direct me to a single CMS platform for Node! I'd struggle to find any that were any good. This isn't really because Node hasn't been around that long (even two years is long enough to build a simple CMS), but because a CMS in Node would be an altogether different beast.
My opinion? Use Node alongside PHP. Use Silverstripe to handle the CMS, while Node handles the connections. This is perfectly feasible and very flexible.
|Go to Top|