[mochikit] Re: MochiKit Development
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 obviously show development. Frequent updates to the web site (there have been only two blog posts this year), new articles about how to use the library on web development sites, reviews in those JS library comparison articles that are oh-so-trendy these days, and of course updates to the non-SVN/stable version of the library are the kind of things that do demonstrate an active development community. If I'm a new JS programmer and I start comparing libraries, I'm most likely not going to make it to this group. Instead I'm going to look at the website, and if the library doesn't look like it's actively developed I'm going to go looking somewhere else (for the reasons I listed in my previous post). I would much rather MK stay lightweight I agree; however, I still think there are future uses for Javascript coming that will justify their inclusion in the Mochikit library (IMHO, anything commonly done by a large number of JS programmers that could be well implemented in Mochikit's sleek Python-esque style). I guess what I'm trying to say is not that Mochikit constantly needs to add new functions and packages to be a great library; as everyone has said, it's already a great library. What I'm trying to say is, even if tons of new functions/packages aren't constantly being added, an active development community (or perhaps more accurately, the appearance of an active development community) is still very important if this great library is going to be recognized as such and widely used. Jeremy On Jul 18, 9:05 pm, Kevin Triplett [EMAIL PROTECTED] wrote: 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 cents -- I get the distinct impression that the core development team uses MK in their commercial software, so they're motivated to patch the code as browsers change and strong user expectations develop. I would much rather MK stay lightweight and tight than bloat into some behemoth that offers 100 ways to do the same thing because someone thought it would be better to do it this other way. Look at Windows(tm) for a shining example of active development. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups MochiKit group. To post to this group, send email to mochikit@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/mochikit?hl=en -~--~~~~--~~--~--~---
[mochikit] Re: MochiKit Development
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 voluntary work, so anything can happen :). Anyway I closed 2 bugs and did a bit of cleaning tonight. There's still one issue (http://trac.mochikit.com/ticket/248) but I don't manage to reproduce it and it doesn't seem very important. I also moved Controls.js out of trunk, in the autocompleter branch, until someone decides to revive it. -- Thomas --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups MochiKit group. To post to this group, send email to mochikit@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/mochikit?hl=en -~--~~~~--~~--~--~---
[mochikit] Re: MochiKit Development
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 doing so will not screw me in the end. This is why I believe active development is important for Mochikit (as it is for any non-for-profit software library). I think you can rely on us to fix MochiKit problems we experience with our commercial software. There's not much overhead for you to isolate and fix problems in JavaScript. I don't think it's unreasonable to ask that you just submit a patch if you find something broken or lacking. If the patch is good, it's likely we'll apply it to MochiKit pretty quickly. Beau --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups MochiKit group. To post to this group, send email to mochikit@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/mochikit?hl=en -~--~~~~--~~--~--~---
[mochikit] Re: MochiKit Development
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 the bug fixes are done, IIRC it's a matter of auditing everything and making sure the docs are good. I've been really busy, and since MochiKit works as-is for us (svn trunk obviously doesn't bother me) I haven't needed to devote much time to it. I understand that this bothers some people, but I didn't develop MochiKit to do consulting and my company doesn't really do anything that would benefit from MochiKit being more popular. I also don't need a job and I haven't seen any AJAX conferences in interesting locations lately ;) Other than that, I think MK is near-perfect and find it interesting how people seem to feel that if a product/technology/etc. isn't constantly being developed, it is somehow not that great or not worth using; 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? Some things just mature and are then good enough unless major bugs pop up. That's more or less how I feel about it. I do plan on getting to a 1.4 release, but I've got all of these other internal releases to worry about before that happens :) -bob --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups MochiKit group. To post to this group, send email to mochikit@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/mochikit?hl=en -~--~~~~--~~--~--~---
[mochikit] Re: MochiKit Development
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 cents -- I get the distinct impression that the core development team uses MK in their commercial software, so they're motivated to patch the code as browsers change and strong user expectations develop. I would much rather MK stay lightweight and tight than bloat into some behemoth that offers 100 ways to do the same thing because someone thought it would be better to do it this other way. Look at Windows(tm) for a shining example of active development. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups MochiKit group. To post to this group, send email to mochikit@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/mochikit?hl=en -~--~~~~--~~--~--~---
