On 09/26/2012 11:07 AM, jgdavid...@mac.com wrote: > > Every few years we talk about what's next for the strategic direction of > AOLserver which is great. In addition to the ideas below (which are cool), I > always bring up this question: Should we dump the Windows port in favor of a > clean Unix code base, configure, build, and install? > > I wrote most of that weird Windows code, including the goofy nsconfig stuff. > Some of it was curious, maybe even clever, but in the end it was a > distraction. It's impact on the config/build process in particular was > pretty significant. Today's Linux and OS/X environments are so much more > amenable to Aolserver, with threaded Tcl ready to go, gcc/make all pretty > stable. It wasn't like that in the early days! For me, a purge of the > Windows code and then an aggressive scan for anything still not 64-bit > compatible and cleanly build-able using standard configure/gcc/gmake tools > would be quite refreshing :) >
Yes! I think so. I wanted to add that to my list but I was afraid it was too controversial. But I think dumping windows support would be a great thing. I worked on this in a local branch was very happy with the results. -ayan ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ aolserver-talk mailing list aolserver-talk@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/aolserver-talk
