Some time ago I reported some issues that any sqldeveloper developer suffers everyday, like the complete sqldeveloper hang during plsql code package compilation when it is being used by other sessions, or the micro-hangs that the UI suffers on every database request. This program has critical bugs that might cause locked sessions to leak in prod environments, as you must kill sqldeveloper everytime it happens. It also doesn't behave properly on VPN environments or low bandwith environments as it makes lots of unnecessary requets when establishing the connection or listing contents, they could be sent in bluk instead of one by one.
It's quite annoying to lose some time reporting bugs with all required stuff required by Oracle support for evident bugs that any Oracle senior developer suffers everyday and just receive a reponse from oracle support just responding that this is "The current implementation and not feasible to fix". Since when a bug is not feasible to fix? A bug is not "An implementation".
Just for reference, said bug reported in Oracle Support is Bug 33527262 - SQLDEV HANGS WHEN COMPILING OBJECTS BEING USED BY OTHER DB SESSIONS
Sqleveloper is a great great program with very long term perfomance and stability issues that are not solved and seems that will ever be solved. So please, let us know if Oracle just doesn't want to make improvements and bug fixes to sqldeveloper anymore and we will consider just not using it.