I'd assume "disaster" refers to "future of desktop GUIs", not to Eclipse.

Eclipse is also a disaster internally though, it's not CADT but it's extreme loose coupling, everything setting observers on everything else and keeping its own mirror copy of the data up to date with no idea of the context they'll run in, and if the updates arrive out of order you get state desyncs, and sometimes you get deadlocks because nobody really knows what's calling what, so you can't have a lock hierarchy.