I am.

Ostensibly, they start along the lines of “my firm is implementing new systems, what software should we choose…”  Then, very quickly they become a mud-flinging game of mirrors, misdirected passion and other more general angst (Why does Program X hate me?)  They are littered with sarcasm, attempted yet misunderstood humour, and a few genuine users who take the time to relate their personal experience.

A great example is this ArchiCAD vs Revit discussion.  Please note that it is in the ArchiCAD group (meaning your submissions may be moderated by a pro-ArchiCAD discussion manager).


Another similar discussion:

Over at blog.gayarre.eu, there is a post that compares some of the main features of Allplan and Revit.  Judging by the review, it seems that Allplan has better PDF integration than Revit (which isn’t very hard).

I think some of his description of Revit is quite good:
Revit, Autodesk, is American.
After Archicad and Allplan, Revit was the last to arrive. Is a product of Autodesk and that, in principle, gives confidence. We can imagine that if we use AutoCAD, BIM from the same company it will be easier to learn. There will be many surprises. And it is. The learning curve is very fast. It’s very intuitive.

I like your work philosophy: everything is done in 3d and then generates the planes. This is not to make a BIM or so and then end up drawing in 2D as if we were in Autocad. It is demanding but more consistent. It requires but rewards.

Google Translate

Consider this recent article:
ArchiCAD vs. Revit By Ransom Ratcliff 2011-08-08.  As far as I can tell, it was birthed at this forum thread.

Inevitably, these X versus Y comparisons are often extremely biased.  He himself says that “I did not set out to write a balanced review of each program and this forum would not be the place for that.”

I found some of the statements in his document to be quite incredible.  Consider:

In other words, relationships are created automatically between building elements without the user initiating those relationships…This kind of automation may seem like it will ensure design integrity but instead, it eventually becomes a straight jacket where relationships are created on the fly that the users could not have anticipated. In Revit, the built-in relationships and constraints are a huge disadvantage in the real-world because they cause the model to be inflexible to design evolution and create dead-ends that cannot be anticipated but can only be resolved by deleting elements and rebuilding them in the “right” order.

Pretty bold claims, don’t you think?  Here are a few more (along with my thoughts in blue):

As Revit constraints get ever more complex in a large building, even expert team members start expressing reluctance to make design changes because they sense the risk of crashing the model.
How expert are they, really? 

Those who are new to Revit may think it seems easy to learn, but this “ease” is an
illusion that fades once someone works on a large project with other team members.
The ramifications of seemingly simple procedures can be difficult to anticipate,
catastrophic and irreversible. More than in most applications, new Revit users can know
just enough to be dangerous. 
So difficult projects are difficult in Revit too? 

Revit’s drawing graphics are often inflexible. For example, it is difficult to show raised flooring in section views with a different line weight from the concrete floor below it because both elements are simply “Floors” in Revit. 
Have you heard of Filters?

In Revit, you cannot dimension 3D projection drawings including perspectives and axonometric views. 
In a 3D Ortho view, set a workplane and give dimensioning a try…

In Revit, rendering textures, such as brick coursing, do not match the coursing, placement, or orientation of vector hatching of the same elements in Construction Drawing views, etc.
Set up your materials and model hatches to match.

ArchiCAD’s efficient engine handles and prints large sheet sets (over 200 sheets) without running out of memory like Revit. 
Buy a better PC.

What do you think of this document?  Feel free to comment.  Here is a link again:
revit_vs_archicad_288.pdf (application/pdf Object)

(NOTE:  bolding was done by me).