We have slightly more people in our office - approx. 65. We used GFI for a while - it sucked to administer and use, it just isn't good enough. While not inexpensive, I have been very pleased with the IronPort C series device. Very pleased. Even thought they were purchased by Cisco, they still operate independently. Their support (that I've used twice in 3 years) is also very good. I manage mine like yours - I manually review the stuff that gets quarantined - maybe 15 a day all of the rest of the "definite" spam gets bounced. We've only had about 3 false positives in 3 years.

To most, Shakespeare is art.

And at the time, Shakespeare's works were essentially the dime store novels and sitcoms of the day...

The real "smackdown" should be that most slashdot users should be able to craft a pretty nice blog out of php and mysql alone. This isn't difficult stuff to do. The best I can tell that's what most big sites like tech-recipes do.

Even if you are going to use one of these blogging tools, why limit yourself to the default code. You are the most geeky of the gurus! Hack the crap out of that code. These are in easy php code. Use their work as a building point... and rip out your own version of it.

What the heck has slashdot come to?

ATB

1. How about a plug-in architecture to the VM which takes code specifically designed for graphics primatives which have been put in the code. The idea of plug-in is a lot more fine grained than what you're saying.

2. LISP is a great example. It is the first example that people present. Ashame that LISP has such terrible syntax. Wouldn't it be nice to have an editor that displays code at a higher level, but the low level language is like LISP. Putting code in a different form allows that. I'm looking at doing a language in Argot ( http://www.einet.com.au/ ) which is binary. It will probably act a lot like LISP but will look like a format that the user is comfortable.

3. I disagree. Grammars and parsers are a pain to write. And grammars are especially hard to develop and get right. A format which is closer to AST is easier to parse. If we're going to get rid of this tower of babel we've developed for ourselves, we need to develop more flexible formats to describe code.