Fatal's Journal

New interface in Adobe CS4 is even more bloated and slow than ever before. In addition to that it is big waster of space and time -- now you can't have only bottom property panel opened or it should be automatically collapsabele (you need to stop and wait until it opens). F4 key is the only "all or nothing" solution to that -- or you will have all panels opened around (left, right, bottom), or you will not see anything (and you cant open anything too)!

All these always showed iconic panels looks even stupider on standard 4:3 displays -- huge waste of space. Damn, I never hated GUI this big!
So, what we have in the end: very useful new features + damn slow and annoying interface = CS4
I agree with someones' comment somewhere that CS4 GUI may be pleasant for newcomers that will use CS4 applications occasionally, but very annoing to some who use Adobe apps a lot.
Will Adobe bother to fix it with paths? I don't now, but very hope for this...

P.S. Will update this post with other notes about other troubles with Adobe CS products.

Dreamweaver:
I still can't copy files (images, videos, etc.) from Assets to Files panel. Why not implement this?
Happenning pretty often sporadic selection of source code (CSS, XSL). This often happens when you copy/paste and navigating through code.
Changing keyboard layout in Dreamweaver causes the toolbars to be redrawn and mouse cursor constantly blinking.
http://forums.adobe.com/message/2175960
http://forums.adobe.com/message/2502063

Fireworks:
Not about UI, but anyway feature regression -- no system font antialiasing! Damn!
How you can release product with such regressions? I already accustomed to Opera regressions, but Adobe?

Originally posted by Alan Musselman (Adobe):

On the topic of the System Anti-alias...this is very difficult for us to implement. We actually had to re-engineer every feature that worked with text to support the new text engine. I know it may not seem like a lot to you now and sorry for that, but please understand there are only so many engineers on the fireworks team and we have to make the right choices. If we implemented system anti-alias and didnt implement core functionality like editing a text block and see the bounding box would you have been ok with that?
We are still seriously looking into system anti-alias implementation to see if its possible within the development cycle. We want to release a stable product and engineering a new version of system anti-alias is sketchy right now.

From Fireworks CS4 Beta tread (disable JS to view).

Another problem with new text engine.