Yeah... at the point of defining where script tags should go, etc is more along the lines of patterns and implementation practices, not so much coding standards.
There's a thin line between "standards" and "preferences." Some would call moving all the display state/control logic into a separate class a lovely preference, some of us call it a Presentation Model. To some of us, the use of a PM is mandatory; it's a way of life. It's black and white, and if you break the rule, you should be outcasted. To the rest of us, it takes too long to make an extra file in a package, and make sure that when we abstract it into it's own class we don't break references or dependencies. To use an MVC or not? To use Singletons or not? To use.... you get the point... These arguments extend the existence of Flex, any SDK, and as Omar said, the "discussion" (read: argument) will NEVER end.
