'long' object names

Today it happened again. A developer made a database independent program and gave me the ddl to install it in a - in this case - Oracle database. Given the fact that the application is developed as database independent, this should give no problems.
During the installation I got many ORA-00972 identifier too long error messages. This surprized me a little. Checking the code, it appeared that table names had horrible long names and as we all know, Oracle has always had a limit on the identifier lengths.
So before throwing it all back I tried a workaround, trying to use synonyms with the long name pointing to the tables for which I adjusted the name to keep within the current limits.

lets try:

create table z as select * from dual;
create synonym verylongnamethatnoonewantstohaveoruse for z;

This runs without any issues.

select * from VERYLONGNAMETHATNOONEWANTSTOHAVEORUSE;

gives ORA-00972 identifier too long :-(

That is a pity, my trick is not going to work.
What synonym is created?

select synonym_name from user_synonyms where table_name = 'Z';

SYNONYM_NAME
------------------------------
/5bba812b_VERYLONGNAMETHATNOON

A little different than expected ...
The leading '/' makes it unusable, unless quoted:

select * from "/5bba812b_VERYLONGNAMETHATNOON";

DUMMY
-----
X

Check the documentation: Oracle® Database SQL Language Reference - CREATE SYNONYM

Leaving me no other option than to return the code to the developer. Question that remains is: is this 30 characters limit still valid? If appearantly many others allow longer names, why does Oracle still stick to the 30 characters limit. Now we have to persuade developers to adjust for Oracle, where the same code runs without problems om other databases. For this project the choice was easy: deploy on sqlserver. This is not what we want, is it?