Re: State of the BEEP

Good intentions aside, I probably have to agree with Marshall.  I
have not made the time to address the bugs in the current implementation
much less do some of the mods I have thought about.

I have been rather hoping that we'd get some more folks jumping in
and writing code, which happened for a bit, but did not continue.

I think the current implementation is far to grandiose in the way
that we designed how the components work together.  We were trying 
to do too much and make its the whiz bang fully extensible plug
in whatever you wnat thing.

Perhaps the biggest problem in the current design is the threading,
which does not allow you to actually have a single threaded 
implementation.  Fixing this requires rewriting significantly parts
of the wrapper.

So, in the end I guess, it's pretty much in the closet and I don't
se myself putitting in the time it needs in the near future, and I'm 
the only one actively supporting it right now.  

-bill


On Tue, Jan 27, 2004 at 07:55:03AM -0800, Marshall Rose wrote:
> > Can anyone comment on the state of beep and beepcore-c?
>     
> hi. this is just my opinion. people should feel free to disagree...
>     
>     
> > There seems to be no real activity in the past year (no news, no
> > announcements, only 6 source code files modified during the entire
> > year).  10 of the 13 bugs are assigned to 'nobody' and 9 of the 13
> > are over a year old.  The mailing lists are also fairly quiet.
>     
> i agree. all this tells me is that beepcore-c is dead. any signs of motion
> is merely rigor slowly setting in.
>     
> i tried to get the guys with a commercial c implementation of beep to
> loosen up their licensing a bit to make it accessible to a larger
> community, but wasn't successful in this.
>     
>     
> > So my question is are these signs of a mature, bug-free, robust
> > software project, or one that's been mostly abandoned?  Are folks
> > using beep and beepcore-c?  How well used and widely deployed are
> > these technologies?  How large is the user and developer communities?
> > How active are they? Is beep a going concern?
> 
> in order:
>     
> abandoned.
>     
> not me, i use the tcl and java ipmlementations, am learning the cool
> python implementation, and have looked at a few others, e.g., the perl
> implementation and liblogging (the minimal beep stack written in c).
>     
> i use the tcl version in some internal projects.
>     
> i know a couple of companies that use the java version in commercial products.
> 
> go to http://beepcore.org/
>     
> tcl is bug-fixes only; java is fixes + minor enhancements; python just
> put out a major functional release. perl and liblogging appear stable.
>     
> based on the email i get on the topic, yes.
>     
> /mtr
> 
> 


-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn