Le 2010-11-11 à 07:21, Anjo Krank a écrit : >> I have a question that I kept to myself for months, but let's go public. >> People talks about moving away from WO or even writing WO/EOF replacements. >> But AFAIK, Wonder shows that we can extend the core frameworks a lot. > > The core problem being that "we" means a very, very tiny amount of people. > Basically, it means "I" have to fix stuff that "I" want done. While it's nice > to be able to do that, it's hardly economic. I really can't remember the last > time I had someone else solve a problem for me (not counting Mike fixing up > the IDE).
Indeed, that's part of the problem. But in the last year, we did have more committers. And from the comments we get from the surveys, I got a couple of people who said that the Wonder "process" is not open enough. Using Github is an option for that. Having more committers is another one. And we are planning to do some sort of membership (that will include the WOWODC recordings) where the revenues of the membership would be used to give awards to contributers and pay for tools or major fixes/improvements. > So on the top of my head, where is: > > - s3 adaptor > - lucene adaptor > - session failover > - app engine deployment (probably impossible without serious hacking) > - chunked http support > >> Sure, extending WO so that EOF become multi-threaded or anything like this >> would be a huge task, but from my point of view (a non-technical one), we >> can do a lot on top of WO to "fix" problems. And to me, it make more sense >> to extend WO than trying to rewrite it... > > Depending on how you understand "multithreaded", that's already implemented > or in fact pretty easy to do. Andrus (I think?) has done some work on that > years ago. > _______________________________________________ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list ([email protected]) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to [email protected]
