That doesn't tell anything about who is to blame for that. It doesn't tell anything about 9i's "immaturity". I'll give you oposite examples:
Originally posted by charlton
For some reason or another Oracle 9i listener just stops. All you have to do to fix it is restart the listener or bounce the box. But this is strange, cause it will just stop when it feels like it. Where have the same problem with our production box also running 9i. We logged a tar, but no reply.
That's entirely your problem, not Oracle's. You can't blame Oracle for choosing the same word for some new database element. And AFAIK, TIMESTAMP is part of ANSI standard. Besides, TIMESTAMP was a reserved word in PL/SQL allready in 8i, so you should be wise enough not to use it anywhere.
Another problem when i moved the scemas and tried to recompile, it gave me errors, to find out that Timestamp was causing the problem. Timestamp is a reserved word in Oracle 9i. So i had to maually change the coding to use the timestamp our developers created.