Re: Node.js port, current thoughts

2020-05-14 Thread Sam Ruby
On Wed, May 6, 2020 at 6:58 PM Sam Ruby wrote: > > The difference wouldn't merely be one of language syntax. The result > would likely be closer to an actor model than an object oriented model. > > https://en.wikipedia.org/wiki/Actor_model > https://en.wikipedia.org/wiki/Object-oriented_modeling

Re: Node.js port, current thoughts

2020-05-07 Thread Matt Sicker
I like the actor model idea and prefer it where possible. It’s also why I’m an Erlang fan even though I don’t use the language for anything. It would probably be easier for me since I’ve been using functional programming patterns for a while now, so Ruby-style OOP throws me off a lot. On Thu, May

Re: Node.js port, current thoughts

2020-05-07 Thread Bertrand Delacretaz
On Thu, May 7, 2020 at 12:39 PM sebb wrote: > On Thu, 7 May 2020 at 08:38, Bertrand Delacretaz > wrote: > > Serving that data from a specific subdomain like > > data.whimsy.apache.org might help with statistics and if data use > > A subdomain would need a change to DNS and probably the existing

Re: Node.js port, current thoughts

2020-05-07 Thread sebb
On Thu, 7 May 2020 at 08:38, Bertrand Delacretaz wrote: > > Hi Sam, > > FWIW, I don't have much time to work on Whimsy at the moment but I'm > interested in keeping track of what's going on and help with the > design whenever that makes sense. Especially around helping make the > Board's work more

Re: Node.js port, current thoughts

2020-05-07 Thread Bertrand Delacretaz
Hi Sam, FWIW, I don't have much time to work on Whimsy at the moment but I'm interested in keeping track of what's going on and help with the design whenever that makes sense. Especially around helping make the Board's work more asynchronous. If I end up writing some code, I'm more familiar with

Re: Node.js port, current thoughts

2020-05-06 Thread Patricia Shanahan
I am going to have to push Whimsy down to third priority for the next couple of weeks, behind an urgent bug and preparing for the May board meeting. However, some of my prior experience may be useful in thinking about this. My last job was working on design of multiprocessors - I was performa

Re: Node.js port, current thoughts

2020-05-06 Thread Sam Ruby
On Wed, May 6, 2020 at 7:11 PM sebb wrote: > > On Wed, 6 May 2020 at 23:58, Sam Ruby wrote: > > > > TL;DR: it would be feasible to port the entire Whimsy code base over to > > Node.js, get it up an running on whimsy-vm6 hosted on Ubuntu 20.04 > > (Focal Fossa). There would be a number of advanta

Re: Node.js port, current thoughts

2020-05-06 Thread sebb
On Wed, 6 May 2020 at 23:58, Sam Ruby wrote: > > TL;DR: it would be feasible to port the entire Whimsy code base over to > Node.js, get it up an running on whimsy-vm6 hosted on Ubuntu 20.04 > (Focal Fossa). There would be a number of advantages to doing so. > > The difference wouldn't merely be o

Node.js port, current thoughts

2020-05-06 Thread Sam Ruby
TL;DR: it would be feasible to port the entire Whimsy code base over to Node.js, get it up an running on whimsy-vm6 hosted on Ubuntu 20.04 (Focal Fossa). There would be a number of advantages to doing so. The difference wouldn't merely be one of language syntax. The result would likely be cl