Hi all, I wanted to share the frustration of seeing yet another great new ORM feature blocked due to Oracle compatibility: https://github.com/django/django/pull/16417
In the past, I too have had to put a lot of effort trying to make a PR compatible with Oracle, making the overall contributing experience much less pleasant and holding me back from contributing, especially in the early days. Over the last few months, I've tried to encourage newcomers and young users to contribute to Django and they almost always ran into the need to provide compatibility to Oracle, so much so that they eventually gave up contributing. I stress that I am absolutely not criticizing the contributors (very few) in the community who help overcome the difficulties with Oracle. The point is that I think Oracle is a historical anomaly among the database backends supported by Django because it is the only one that is not Open Source, it has irrelevant usage numbers (see Django Developers Survey 2022 Results https://lp.jetbrains.com/django-developer-survey-2022/#horizontal-bar-chart-862) and the company that earns from it does not contribute in any way to its maintenance or support (see Carlton Gibson keynote at PyCon Italia 2023 https://youtu.be/AHjnGtaWDjU?t=836) To add to all this we consider that developing for Oracle is much more difficult than for the other Open Source databases supported by Django and above all the new contributors to the ORM have a frustrating experience and therefore they are less and less. I, therefore, suggest that we start a discussion on removing Oracle from supported databases. Ciao, Paolo -- Paolo Melchiorre https://www.paulox.net -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/CAKFO%2Bx6WXzhhKPoDVodD_dKQEkyLKT3hJOA26seC6%2B3Tb1QrXQ%40mail.gmail.com.
