On a fairly regular basis I’m asked questions along these lines:

• “We’ve been asking for multi-threaded Revit for years. How hard can it be? <Insert usual ADSK expletive>…”(1)
• “Why doesn’t Revit utilise all my PC’s cores like <insert application>…”
• “Revit isn’t a real database, and it’s slow according to our DB expert…(2)”
• “If ArchiCAD can use multiple cores then there should be no reason Revit can’t do it.(3)”

More...

 How incredibly childish Autodesk. A very experienced AU speaker and organiser dropped because he had the audacity to question decisions…

Thank you though, it makes my comments in this post all the more pertinent. Looks like the headless chickens are still out of their cages…

For Phil I have one word, bugger…

Maybe everyone just needs a holiday ;-)

Yes I have taken my medication and no, I have no crystal ball or prior knowledge ;-) I’ve generally stayed out of the debate over the ribbon UI in Revit 2010. However, this post says too much about Revit development within Autodesk to go unchallenged. No, I’m not saying “if they don’t fix the ribbon in Revit 2011 the world will end”. The issues I’m going to discuss are considerably more fundamental than that…More...

I’ve been intending to start blogging on the Revit API for quite some time. I’ve finally settled on BlogEngine as a platform because it’s based on asp.net which will allow me to take advantage of some .NET features over time. More...