I'm not sure if you guys were aware, but Flotype moved on from nowjs to
make bridge, but is now no longer making that either. There is no one
actively maintaining the official nowjs codebase.
Ian
On Fri, Oct 12, 2012 at 12:01 PM, Matthew Baggett <matt...@baggett.me>wrote:
On Fri, Oct 12, 2012 at 8:59 PM, Ian Serlin <i...@ianserlin.com> wrote:
> I'm not sure if you guys were aware, but Flotype moved on from nowjs to
> make bridge, but is now no longer making that either. There is no one
> actively maintaining the official nowjs codebase.
> Ian
> On Fri, Oct 12, 2012 at 12:01 PM, Matthew Baggett <matt...@baggett.me>wrote:
>> Looks like the site is just down.
>> - Matthew Baggett
> On Fri, Oct 12, 2012 at 8:59 PM, Ian Serlin <i...@ianserlin.com> wrote:
>> I'm not sure if you guys were aware, but Flotype moved on from nowjs to
>> make bridge, but is now no longer making that either. There is no one
>> actively maintaining the official nowjs codebase.
>> Ian
>> On Fri, Oct 12, 2012 at 12:01 PM, Matthew Baggett <matt...@baggett.me>wrote:
>>> Looks like the site is just down.
>>> - Matthew Baggett
These were amazing projects. Can anyone recommend an alternative to nowjs that is actively maintained? Without anyone maintaining nowjs, it will eventually be incompatible with newer node versions, right?
On Friday, October 12, 2012 12:59:56 PM UTC-7, Ian Serlin wrote:
> I'm not sure if you guys were aware, but Flotype moved on from nowjs to > make bridge, but is now no longer making that either. There is no one > actively maintaining the official nowjs codebase.
> Ian
> On Fri, Oct 12, 2012 at 12:01 PM, Matthew Baggett <mat...@baggett.me<javascript:> > > wrote:
>> Looks like the site is just down. >> - Matthew Baggett
The nowjs paradigm of functions that can be called back and forth from
server and client is really inspired.
In my experience, the underlying "socket.io" module is not able to scale
well (more than 150 connections was a problem for me), so I had to retreat
from using "nowjs" or more specifically, "socket.io" in one of my
applications. On the other hand, I have another application that has been
running for 9 months now without any problems, but it only handles 2 to 5
connections at a time.
My other observation is that: The magic pocket for variable (across sever
and client) is not useful, because it does not have any notification events
(ie onUpdate, etc.), so you never know when the magic has occurred.
"An opensource project never has to die" -- R. Stallman
On Sun, Nov 11, 2012 at 10:32 PM, Jeff Wilde <jeff.wi...@gmail.com> wrote:
> Why did the project die? Were there issues with the project? Can someone
> else take over the project?
> On Friday, October 12, 2012 12:32:27 PM UTC-6, Joel Shapiro wrote:
>> I feel like this might be a stupid question, but is nowJS somewhere
>> besides the old .com?
You might check out shoe (https://github.com/substack/shoe) built on top of
sockjs, which is what bridge used on the JS client side. It isn't
explicitly an rpc library, it's a streaming library, but like any socket
library can sorta be used that way. Bridge is also open-source but requires
a running bridge server.
Creating a basic "these are my functions, make them available everywhere"
micro-lib could actually be cool. If anyone is interested in doing this
together, ping me.
On Mon, Nov 12, 2012 at 9:30 AM, Nate Morse <morse.n...@gmail.com> wrote:
> The nowjs paradigm of functions that can be called back and forth from
> server and client is really inspired.
> In my experience, the underlying "socket.io" module is not able to scale
> well (more than 150 connections was a problem for me), so I had to retreat
> from using "nowjs" or more specifically, "socket.io" in one of my
> applications. On the other hand, I have another application that has been
> running for 9 months now without any problems, but it only handles 2 to 5
> connections at a time.
> My other observation is that: The magic pocket for variable (across sever
> and client) is not useful, because it does not have any notification events
> (ie onUpdate, etc.), so you never know when the magic has occurred.
> "An opensource project never has to die" -- R. Stallman
> On Sun, Nov 11, 2012 at 10:32 PM, Jeff Wilde <jeff.wi...@gmail.com> wrote:
>> Why did the project die? Were there issues with the project? Can
>> someone else take over the project?
>> On Friday, October 12, 2012 12:32:27 PM UTC-6, Joel Shapiro wrote:
>>> I feel like this might be a stupid question, but is nowJS somewhere
>>> besides the old .com?
>> On Fri, Oct 12, 2012 at 8:59 PM, Ian Serlin <i...@ianserlin.com<javascript:> >> > wrote:
>>> I'm not sure if you guys were aware, but Flotype moved on from nowjs to >>> make bridge, but is now no longer making that either. There is no one >>> actively maintaining the official nowjs codebase.
>>> Ian
>>> On Fri, Oct 12, 2012 at 12:01 PM, Matthew Baggett <mat...@baggett.me<javascript:> >>> > wrote:
>>>> Looks like the site is just down. >>>> - Matthew Baggett
I'm no longer maintaining NowJS. I don't have much time to devote to NowJS
as I'm working full-time on another startup. I'm sorry to drop the ball on
development and bugs! You might want to look at other projects like dnode
which are still being actively developed.
If I or someone else wanted to take of maintenance of NowJS could we? Are there issues with NowJS that lead you to abandon it or is it just a time constraint?
On Friday, November 16, 2012 3:34:00 AM UTC-7, Darshan Shankar wrote:
> I'm no longer maintaining NowJS. I don't have much time to devote to NowJS > as I'm working full-time on another startup. I'm sorry to drop the ball on > development and bugs! You might want to look at other projects like dnode > which are still being actively developed.
Until an alternate page is availalbe/project taken over by somebody else, etc. you can still find the old page in the web archive: http://web.archive.org
PS: I am also interested in taking care/part of the alternate project if you need volunteers. (Unless people strongly recommend other projects like substack's dnode or sock).
On Friday, November 16, 2012 8:19:32 PM UTC+1, Jeff Wilde wrote:
> If I or someone else wanted to take of maintenance of NowJS could we? Are > there issues with NowJS that lead you to abandon it or is it just a time > constraint?
> On Friday, November 16, 2012 3:34:00 AM UTC-7, Darshan Shankar wrote:
>> I'm no longer maintaining NowJS. I don't have much time to devote to >> NowJS as I'm working full-time on another startup. I'm sorry to drop the >> ball on development and bugs! You might want to look at other projects like >> dnode which are still being actively developed.
Can you pass over the control to the community? I guess there are plenty that you love to take further part into it. The code is not a problem since people can fork the code. I guess the web page is more important because many go through it to learn about NowJS. The twitter account is also another asset that might be interesting to be migrated together with the project.
But please share us some of the reasons about your retreat besides the fact that you are now dragged into the startup you mentioned. Are there non-obvious, hidden, or difficult issues with the project that people should be aware of. Do you recommend that people migrate to other projects (e.g. dnode, sock)? I also understand the scalability issue with socket.io, but probably there are projects where this doesn't matter.
Please share your experience and let's either completely kill it or move it further!
On Friday, November 16, 2012 11:34:00 AM UTC+1, Darshan Shankar wrote:
> I'm no longer maintaining NowJS. I don't have much time to devote to NowJS > as I'm working full-time on another startup. I'm sorry to drop the ball on > development and bugs! You might want to look at other projects like dnode > which are still being actively developed.
On Saturday, November 17, 2012 8:26:40 PM UTC+1, Gabriel Petrovay wrote:
> Until an alternate page is availalbe/project taken over by somebody else, > etc. you can > still find the old page in the web archive: http://web.archive.org
> PS: I am also interested in taking care/part of the alternate project if > you need volunteers. (Unless people strongly recommend other projects like > substack's dnode or sock).
> On Friday, November 16, 2012 8:19:32 PM UTC+1, Jeff Wilde wrote:
>> If I or someone else wanted to take of maintenance of NowJS could we? >> Are there issues with NowJS that lead you to abandon it or is it just a >> time constraint?
>> On Friday, November 16, 2012 3:34:00 AM UTC-7, Darshan Shankar wrote:
>>> I'm no longer maintaining NowJS. I don't have much time to devote to >>> NowJS as I'm working full-time on another startup. I'm sorry to drop the >>> ball on development and bugs! You might want to look at other projects like >>> dnode which are still being actively developed.
It appears that the fork hasn't been maintained at all in the last 4 months - I wonder if there's a suitable replacement for now.js (which seemed very promising before it was abandoned).
What are they doing now if they've abandoned both nowjs and bridge? Is any kind of replacement for nowjs and bridgejs being developed, or is the project entirely defunct now (and lacking a suitable replacement?)
On Friday, October 12, 2012 3:59:56 PM UTC-4, Ian Serlin wrote:
> I'm not sure if you guys were aware, but Flotype moved on from nowjs to > make bridge, but is now no longer making that either. There is no one > actively maintaining the official nowjs codebase.
> Ian
> On Fri, Oct 12, 2012 at 12:01 PM, Matthew Baggett <mat...@baggett.me<javascript:> > > wrote:
>> Looks like the site is just down. >> - Matthew Baggett
> It appears that the fork hasn't been maintained at all in the last 4
> months - I wonder if there's a suitable replacement for now.js (which
> seemed very promising before it was abandoned).
> On Saturday, November 17, 2012 3:46:50 PM UTC-5, Velojet wrote:
On Fri, Dec 21, 2012 at 8:00 PM, Nate Morse <morse.n...@gmail.com> wrote:
> I know that it is not exactly the same but how about dnode and shoe?
> On Dec 21, 2012 7:48 PM, "Andy Green" <jar...@gmail.com> wrote:
>> It appears that the fork hasn't been maintained at all in the last 4
>> months - I wonder if there's a suitable replacement for now.js (which
>> seemed very promising before it was abandoned).
>> On Saturday, November 17, 2012 3:46:50 PM UTC-5, Velojet wrote:
