eThreads work

Friday, September 21, 2001, at 07:57PM

By Eric Richardson

So I've spent most of the evening finishing up some eThreads work for Gospelcom. Have I ever mentioned that I love eThreads?

The eThreads code these days is a finely tuned fighting machine. A lot of software claims to do forums, but when you really compare them to eThreads you find they're just hacks. eThreads is an application. It has architecture. It has framework. The code is documented (how this happened I'm not sure, but it really is).

The problem is that most people only see eThreads from the front. From the front eThreads looks like other forum software. It displays posts, it does threads... Yadda yadda yadda... Seeing eThreads from the front is no fun. eThreads begins to shine when you turn it around and look at the back. Everything is stored in the database. Settings apply recursively down the inheritance tree. Domain roots allow clean paths on virtual hosts. The rights system allows utter flexibility. The glomlet system allows functionality free expansion. The glomule modules allow radically different kinds of content to fit into place.

Granted, there are places where eThreads does not work. eThreads is not for little homepages that want one forum. eThreads is not for those who are afraid to get intimate with understanding the system.

What eThreads does, it does very, very well. As an ISP-caliber forum and weblog package, eThreads is untouchable.

And yet the only ISP'ish entity to use eThreads extensively did so because I worked there. Where does that come from?

I really don't care, though. eThreads is fun to work on, and it performs perfectly at all that I call it to do. What else would I want?