On Wed, 06 Aug 2003 15:39:50 -0500, Sam Ewalt wrote: > On Sun, 3 Aug 2003 14:04:21 -0400, Roger Turk wrote:
>> We NEED secure shell capabilities AND javascript capabilities in Arachne as >> soon as possible. > What we need and what we're going to get may be two completely > different things. That is understood. OTOH, it is certainly in our interests to at least try to work with what the rest of the world uses. 20 years ago, a lot of people knew that Beta was a better system than VHS for home VCRs, but where are they now? > Glenn has done a truly outstanding job of keeping Arachne development > heading forward. We all owe him a debt of gratitude and appreciation. We do indeed! I certainly admire what he has done. I wish that I could do half as well. > Maybe some sort of team effort can be orgainized after Micheal > officially releases the latest version with the source code. That's if you can get Michael to correspond with anyone. I emailed him a while back with the message "Does anyone read the email to this address?" He replied: "Why not?" I answered his email with the reasons for my question but I never received a reply.... > Obviously, major improvements are going to require major investments > of time and effort from skilled people. But is there enough interest > to make major improvements? There probably is enough interest already. What we really need is someone with that interest AND the necessary skills to develope a solution. One person would be enough, but more than one person means the chances are greatly increased. Communication is the answer (see below). > Only time will tell. We can only hope. True. > Does anyone have any constructive ideas about how to encourage > Arachne development? > Please speak up if you do. Communication. If we keep discussing what problems we find, then it is possible that one or more of the people we correspond with may come up with an answer to them. This approach has worked with a number of other problems, as evidenced by the messages in the arachne-list. There is a chance that someone may have an idea that could lead to a breakthrough with the more difficult problems like Javascript compatibility. But the surest way to fail is to think that all we have to do is blame the problems on the people causing them, such as MicroSnot. M$ is not about to rewrite all their code to accomodate Arachne. It is up to us Arachne-lovers to find ways around the obstacles that M$ puts in our path. Greg -- Arachne V1.71;UE01, NON-COMMERCIAL copy, http://arachne.cz/
