B-737/300 experience: Really liked the FMC for programming and dealing with stuff like "cross 25 miles S of VOR at FL190." Loved the green arc. Weakness was moving back and forth between the "managed plan" and whatever ATC wanted you to do at the time. Also, the automation in the approach environment was pretty weak (no autotune of ILS, couldn't engage autopilot to fly published MAP because INS didn't know where it was)
A320 experience: An overall superior effort of automation, but one that took some time to master. I still would take the Honeywell/Boeing box over this thing. The ACP is where the Bus really shines--does a decent job getting you down and meeting restrictions (especially if you start down on time), but most of my descents involve ATC fvcking with my airspeed, top of descent, putting in undesired level offs, etc. I like the "push for managed, pull to command" philosophy, and it seems easier to get back to managed when my apple cart gets upset. The Bus also really shines for normal approaches, MAPs, and S/E work. It is true that some of the oddball stuff is convoluted to fly (backcourses, arcs), but they just don't come up that often where I fly. Finally, I love the fact that Fifi figures out your flap extension/retraction speeds, approach speeds, etc. and displays them on the tape. Brilliant! I'm sure more recent Boeing stuff does this, but not in the 300/500.