I *am* curious as to the effort to get us to an official '1.4' release -
seemed like there was a bit of momentum a few weeks/months back to get all
bugs fixed and get it shipped, but then it seemed to die.
Other than that, I think MK is near-perfect and find it interesting how
people seem to fee
On 18 juil, 17:16, "Jason Bunting" <[EMAIL PROTECTED]> wrote:
> I *am* curious as to the effort to get us to an official '1.4' release -
> seemed like there was a bit of momentum a few weeks/months back to get all
> bugs fixed and get it shipped, but then it seemed to die.
It's all about volunt
"if MochiKit fulfills the measure of its creation (i.e. if its current
state meets the goals set out for its original design/purpose), then
why does it need to be continually developed?"
1) Nobody wants to tie themselves to a dead horse. In other words,
nobody wants to take the time to learn Moc
On 18-Jul-07, at 1:42 PM, machineghost wrote:
> But Mochikit is a WONDERFUL library. It's better than any other JS
> library I've worked with, and I've tried a few. So I (and I imagine,
> many others in the Mochikit community) would like to be able to user
> the library with confidence that doi
On 7/18/07, Jason Bunting <[EMAIL PROTECTED]> wrote:
>
>
> I *am* curious as to the effort to get us to an official '1.4' release -
> seemed like there was a bit of momentum a few weeks/months back to get all
> bugs fixed and get it shipped, but then it seemed to die.
I think that most or all of
> Any developer who has been in this business for any length of time
> should no better than to blindly use a library, no matter how cool,
> unless:
> A) they expect it to be actively developed in the forseeable future
> B) they don't ever expect to want a new version of the library
Just my 2 cen
Several people have responded (both in group and out) that MochiKit IS
updated regularly. This is great and ... not really news to me; I've
lurked in this list for a few months now. My point however, still
remains, because a few Google groups posts saying "development is
active" does not obviousl
Jeremy,
an additional way to evaluate MochiKit is to look at who is using it:
for example the PyPy guys for the really bleeding-edge application
demos like "Terminal in a website" or "Python interpreter in a web
site"
As long as the really cool guys use a library, it's on the right side
of the
SomeHow as long as TurboGears folks use it and people like me use it
in large enterprises I have a feeling MochiKit will continue adding
features when it needs to. The Key being when it needs to. Just adding
code for no reason gets you Prototype. And we all know what happens
then. MochiKit is JS f
