incubator-wave-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Thomas Wrobel <>
Subject Re: NodeJS for Sever-Side Wave Code
Date Thu, 30 May 2013 07:07:55 GMT
Niceness is in the eye of the beholder though - personally I'd much prefer
Java then Javascript. ;)
Theres nothing "better" about JS for server side stuff, its all just
relative to peoples experience. People side with a language they know.

If there was the manpower to do it, re-writing waves server in any language
would probably make it better though, simply as normally the second time
something is coded goals are more clear and better ideas form how to
achieve them. Currently its a mess of many years of code with many people,
most now no longer actively working on it. Its very hard for a new person
to jump in as its all so vaste and complex.

Rewriting from scratch is just too unrealistic though at this point -
 focusing on separating out the client is a more logical first step. It
also helps in the longer road to updating (simplifying?) the code overall
[/2 cents]

On 30 May 2013 06:40, Angus Turner <> wrote:

> Nothing about it not being appropriate, everything about having the man
> power. Right now it's hard enough to maintain the code we've got.
> I personally would rather wave was written in a 'nice' language like JS or
> Python, but right now it's not worth the effort.
> Thanks
> Angus Turner
> On Thu, May 30, 2013 at 12:53 PM, John Blossom <> wrote:
> > Hello,
> >
> > Looking through some documentation on Wave-derived products, I am seeing
> > that there is some good use of Node.JS coding for server-side functions.
> > Why would it not be appropriate to replace some or all of the demo-model
> > code from Google on the server side with a light and powerful language
> such
> > as this?
> >
> > Good analysis of Node performance at:
> >
> > Thanks for your feedback,
> >
> > John
> >

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message