Hi Andrew, Thank you very much for your answers here. I'm glad to have your explanations and opinion; I've read your answer too in the subject "What must Prototype JS do to become the library of choice?" (with the link you provided) and I will tend to say that I'm ok with your position (If I can say, not sure it is correct in english, sorry). Even if I don't have to care about "market share", even if nobody will never ask why I have used this or this library (I'm lucky compared to some of the others participants) - I can deal with a "niche library" as you say as I working in a "niche" too -, I really needed this kind of clarifications. I still have a last question, however, but I don't want "overload" the topic here. (nevertheless, I hope I could have your point of view for this one too)
Best regards, Vinc. On 23 août, 02:07, Andrew Dupont <googlegro...@andrewdupont.net> wrote: > OK, let's start from the beginning: > > On Jul 13, 9:36 am, Cantrelle Vincent <vcantre...@gmail.com> wrote: > > > I hope that I have a > > "truncated" view of the situation, and that the number of users for > > Prototype.js is still high enough, and the "motivation" of the core > > team too, so that this library will be still maintained / improved in > > the futur. > > Prototype's development over the past few years has been typified by a > few months of inactivity, then a furious week of activity, and I doubt > that will change anytime soon. It happens that way because I'm > juggling several different open-source projects on top of my day job, > and so I try to rotate between them every few weeks. > > So don't read anything into the periods of inactivity. I don't have > any plans to stop working on Prototype. > > On Jul 15, 12:49 pm, Phil Petree <phil.pet...@gmail.com> wrote: > > > I certainly have the resouces to host the forums and would have no problem > > in putting them up and maintaining them but it would take a consensus of the > > powers that be because if none of the guys that answer the majority of the > > questions are interested then it would just be like the french forums when > > no one replied. > > If people feel like this mailing list isn't serving their needs, I've > got no problem with someone wanting to start a forum somewhere else. > Frankly, I think the best solution would be to encourage people with > support questions to post on StackOverflow and tag their questions > with "prototype" or "prototypejs" or something, but I'm open to other > suggestions. Certainly, if someone were willing to maintain some > forums, I'd be happy to give them the vouch, because that's a task we > know we'll never have time for. > > On Jul 21, 8:42 pm, Walter Lee Davis <wa...@wdstudio.com> wrote: > > > The current documentation (1.7) is generated directly from the source > > code using a tool written by one of the core guys -- I think it's > > called jsDoc or something like that. Anyway, it's just static HTML, > > CSS and JavaScript (naturally) once that tool is done. > > > I think that if there was enough energy for moderation, or some sort > > of community moderation system, that a great add-on to the site would > > be something like Disqus, so the user comments and corrections could > > be added to the mix. > > Our documentation tool is called PDoc, and it's Tobie's brainchild. In > fact, he had spent some time modifying it to generate one HTML page > per method for precisely this purpose — so that we could enable Disqus > commenting on every page. I think the project got shelved when Tobie's > daughter was born, or else when he started working for Facebook. I'll > follow up with him and see if that's at a point where he can hand it > off to someone else. > > I share the concerns about moderation, because while I agree that > PHP's documentation comments are a net benefit, many of them contain > sloppy code and încorrect information. But I think Disqus's "likes" > are a good start. Hopefully the cream will rise. > > On Jul 26, 2:42 pm, Phil Petree <phil.pet...@gmail.com> wrote: > > > The core devs need to appoint a "Community Activist" whose responsibility it > > is to build the community and who has the decision making authority to > > implement these changes without bugging the devs with all our needs. > > T.J. used to serve in this role, but stepped back some time ago > because of other commitments. You can blame me for not seeking out > someone to take his place; that's mostly why the documentation tickets > have been languishing on Lighthouse. I'm happy to "appoint" whoever > you guys think would do a good job. > > On Aug 17, 10:04 am, Phil Petree <phil.pet...@gmail.com> wrote: > > > My fear is that prototype will ultimately face the same fate... be a > > technically superior product with a few guys pitching in and carrying the > > weight (anyone who follows this feed knows who the guys are who always pitch > > in with an answer) while marketing, support, easy access to developed libs > > and all the other goodies go ignored which causes adoption of the product to > > dwindle because these things exist on another platform. > > I know the major libraries have had a playfully-competitive > relationship for years, but I'm not altogether concerned with the > "market share" of Prototype. Someone asked about this on Quora, so > I'll link my answer [1] here so as not to re-state myself. > > I will say, though, that if we're crowning winners and losers, then > jQuery "won" a long time ago. It is certainly the _de facto_ > JavaScript library for web development. The good news is that the > "losers" of the war aren't looking so bad; libraries like Prototype, > MooTools, and Dojo still have loyal user bases, and I doubt they're > going away. > > So here are the next steps, I think: I'm going to touch base with > Tobie and learn the state of his Disqus project. Meanwhile, weigh in > and let me know who you think could fill T.J.'s gargantuan shoes in > the realm of documentation and community activism. Cool? > > By the way: I did stop watching this list closely a while back, but > told myself I'd check in from time to time. Clearly I've dropped the > ball. I'll try to do better. Meanwhile, I'm always accessible via > Twitter (@andrewdupont), GitHub (savetheclocktower), or at this very e- > mail address. > > Cheers, > Andrew > > [1]http://www.quora.com/What-must-Prototype-JS-do-to-become-the-library-... -- You received this message because you are subscribed to the Google Groups "Prototype & script.aculo.us" group. To post to this group, send email to prototype-scriptaculous@googlegroups.com. To unsubscribe from this group, send email to prototype-scriptaculous+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/prototype-scriptaculous?hl=en.
