3 ms·
The reason why ACS was any good was because AOLServer was an awesome multithreaded webserver with a great API. Tcl was only there because it was the easiest lan
by menloparkbum 19y ago
The reason why ACS was any good was because AOLServer was an awesome multithreaded webserver with a great API. Tcl was only there because it was the easiest language to embed into a multithreaded app at the time (now that distinction goes to lua). I'm not sure the Tcl code in the ACS was a good example of anything... in places it was as bad as the worst Perl script you have seen. (I know, I probably wrote 20% of the codebase.)
- mechanical_fish 19y agoI'm not sure the Tcl code in the ACS was a good example of anything... Pragmatism? And, yes, I understand that nobody really chose Tcl at the time... nor would anyone choose Tcl again. It was more a matter of lemons and lemonade. And not always very tasty lemonade. ;)
- menloparkbum 19y agoI guess pragmatism is valid, but there were quite a few half-baked modules tossed in there just to make it look like the toolkit was more comprehensive than it really was. Also, I think openACS expunged them, but in the initial releases at least 25% of the code was dedicated to Philip's rambling comments about how a particular function would be much more elegant in common lisp.
- mechanical_fish 19y agothere were quite a few half-baked modules tossed in there just to make it look like the toolkit was more comprehensive than it really was. Has there ever been an open source toolkit that didn't look like this? I assure you that Drupal is just the same, only the half-baked modules are numbered in the thousands... Your statement about Philip's rambling comments is both ROTFL-funny and 100% believeable. ;) Hey, just because you're being a pragmatist doesn't mean you can't complain about it at great length...
- menloparkbum 19y agoYeah, I've worked with Drupal, it is far worse. However, new things like Rails, Merb, even Django suffer from this far less.