asking for news!

[jg]

Hi again,

I really like narwhal but I've been disappointed by the activity on
github, the traffic on this list or on Twitter where communication
stopped about 6 months ago. The same with Rhino itself, you might say!
I came across ohloh analysis (https://www.ohloh.net/p/narwhaljs/
factoids/4230488), and you might tell which of their hypothesis are
the right ones. As being a project I like, I'm concerned about it,
mainly because of the nice combination Java/JS/commonJS. NodeJS, which
gets all the attention as yet, doesn't allow reusing stuff I'm more
familiar with. I know RingoJS is somehow concurrent, but there are
differences (require("file") or require("fs")?). Could you clarify the
position of the two projects one to the other?

So I hope you tell this project is still alive!

Thanks
jg

[Nathan Stott]

RingoJS is similar to narwhal.

I'm not sure what the status of narwhal is. Kris Kowal has moved onto
mostly node.js development. Tom Robinson is probably still using
Narwhal with 280north. They were bought out and I'm not sure how
interested Motrola is in narwhal as opposed to pure cappuccinno. It
would be nice if Tom would give us an update on that.

> --
> You received this message because you are subscribed to the Google Groups "Narwhal and Jack" group.
> To post to this group, send email to narw...@googlegroups.com.
> To unsubscribe from this group, send email to narwhaljs+...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/narwhaljs?hl=en.
>
>

[Christoph Dorn]

I am planning on contributing to narwhal-lib again and promoting it once
I get more of my infrastructure up and running and have done a bunch of
refactoring. I will likely stay clear of the narwhal sandbox, loader and
packages modules (will be using other CommonJS loaders for that).

I am using narwhal extensively on the server, in the browser and in a
browser extension with good results. Have only needed to make minor
changes in general (other than the major packaging stuff I did a while ago).

So if it was up to me I would say narwhal (or at least narwhal-lib) is
going to stick around even though it is going through a bit of a slow
period right now.

Christoph

--
http://www.ChristophDorn.com/Tools/

[Simon Oberhammer]

On Tuesday, February 1, 2011 5:40:27 PM UTC+1, jg wrote:

The same with Rhino itself, you might say!

Rhino has a new mailing list: https://groups.google.com/forum/#!forum/mozilla-rhino

Rhino is still being developed, right now they are working on some kind of performance optimizations. A lot of work happens in the github fork that might not be easily visible until it lands in main repo.

I know RingoJS is somehow concurrent, but there are
differences (require("file") or require("fs")?). Could you clarify the
position of the two projects one to the other?

What would you want to know? I'm a RingoJs contributer and can relay questions. As already said: they are very similar. RingoJs tried to stay more narwhal compatible in the past but there just weren't enough people using both so that has faded a bit.

[Nathan Stott]

Tom, do you want to give us a narwhal update? It would be much appreciated.

[Kris Kowal]

Tom and I, at this point, are both working on other things but
occasionally fix bugs as we find them. We have no major plans to
extend or overhaul the architecture; if we undertake such a venture,
it will be a new project.

I've personally been working on applying lessons learned in the
Narwhal architecture to explore the wider world of packages on a
variety of engines, especially Node. It's pretty clear that Narwhal is
entrenched in synchronous IO, and my interests lie in exploring
asynchronous implementations at this moment. Particularly, I am
creating versions of CommonJS/Narwhal modules that use the same
calling conventions but return promises and forEachable streams.
Narwhal is quiet, but we have been busy.

Anyone with a project depending on Narwhal who wishes to have a
governing hand in the future of the project should let us know.
There's plenty of room for more contributors.

Kris Kowal