Thanks for the clearing up on this. I was worried that advice seen as a sales opinion would raise some concerns.
In this particular case, the customer was asking for differences between two vendors solutions. I now understand that its considered 'bad form' for VAR's and vendors to offer a third solution to a 'Best Practises' question based on designing a new network, as we will have a natural inclination to promote solutions that we know best. Sorry, please be aware that my answer wasn't meant to be a sales pitch. I will keep this in mind in my future responses :)
Ref, "The poster even confuses trunking and port channels, which I am sure could cause quite a bit of confusion."
Just to clear something up. The original poster was asking the question, "Do I really gain by trunking the switch to the router?" and was proposing to use an HP ProCurve switch to a Cisco Router. How would you define this question, knowing the following:
In Cisco, the term trunk refers to an interface that you configure to support 802.1Q VLAN tagged frames. That is, an interface that you configure to support multiple VLANs is a
trunk interface in each VLAN in Cisco. In the HP ProVision operating system an interface that supports multiple VLANs is a tagged interface in each VLAN.
In addition, HP ProCurve refers to aggregated interfaces as a trunk, while in Cisco it is EtherChannel.
This is common misconception that needs clarification, hence why I asked for them to Define Trunking.