Re: [Beepcore-c-users] State of the BEEP

[Marshall R. <mr...@db...>]

> 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