Joe Baker wrote:Chuck(G) wrote:X3J3 for me--you guys remember FORTRAN, right?

You mean FORTRAN 90, 77, IV? (Altogether now... the great thing about standards is that there are so many to choose from.)
Actually, the goal was supposed to be FORTRAN 88, but there was just too much er, "discussion" to make that deadline (I don't think anyone was really happy with the end result--I'd moved on long before the standard was adopted).
Language standards are a funny kettle of fish. They initially defined the minimum supported subset (e.g. USA BASIC FORTRAN--you'd really have to be a relic to remember that one) and extensions were a free-for-all game.
Well, if you alow extensions, then every vendor has his own extensions--and the vendor's customers will use those extensions--and then you have IBM FORTRAN, CDC FORTRAN, DEC FORTRAN, etc. And you're back where you started without standards.
I think it was the COBOL 75 group that first drew the line and said "if you want to claim to be a standard implementation, then you may not implement extensions to the language without the explicit consent (e.g. a command-line switch) of the user and you must not be silent on nonstandard usages."
For F8x, there was a different question: "Are we here to certify existing practice (e.g. do we call IBM VECTRAN standard) or do we write a new language?" That was a hard one--no vendor wants his implementation of a neat feature to be called "nonstandard". and there were threatened walkouts of major participants. I think much of the discontent came from the committee authoring in essence, a brand new language.
But at the end, I think, while standards evolve, the results are worthwhile.
30 years ago, if you walked into a bicycle shop and asked for a bottom bracket, you'd have to know what kind: BSC, French, Italiian or Swiss, which differed from one another in almost every conceivable way--in diameter, spacing, thread direction, thread pitch and thread profile. Did any offer advantages over the others--sure, but the advantages were slight and, in most cases, of little tangible value.
I think we could do with a standard for mouthpiece shanks--this doesn't preclude a manufacturer of mouthpieces from offering special-order products for some vintage receiver type (so-called "deprecated" usage). But it does provide a strong impetus for new products to conform to the standard.
Forgive the OT rambling.
