Not necessarily. It has a lot of room for useful and even positive applications. For example, I have worked on a non-profit project to track class attendance around Cape Town and it proved being quite effective.
I sometimes use this - that was built as a call-center simulation - to get quick-and-dirty figures to have an idea of the actual queueing strategy tradeoffs. Queueus are okay, depends on what you want to do with them.
http://queuewiz.queuemetrics.com/
Was looking to something that looked more like the life-cycle of Java servlets. The problem was avoiding to connect to web services before they are ready to serve requests, and creating an easy template for deployment. Try it!
Interesting idea, but my eyes bleed. And I'm a Java programmer. Would rather use Akka or SlicedBread (the latter trading almost all features for the added simplicity but working well and being super-simple).