So, you're blaming gcc for having "non-standard" extensions?
To, presumably other compiler writers, who can write their own if they wish?
So, your first culprit should be other compiler writers, for not supporting versions of these extensions, if so many people want to use the extensions with other compilers.
And then, you also blame gcc for widget makers who *also* wont recode to compiler independent formats.
No, I don't think so.
The end result occurred because gcc was good enough, and has had competition to become better (even from within the codebase).
>> But the end result is about the same as what Microsoft ended up doing with J++.
Really? As far as I know, J++ is not very widely used, while gcc is. So, it can hardly be claimed that this is true or both would have the same fate in the marketplace.
In fact, one might expect Microsoft J++ to have more market share than gcc if they are using the same strategies, since they have much more weight to leverage things.
On the other hand, you could be talking of some other type of 'end result', so please elucidate if that is the case.
Regards.