this post was submitted on 31 Mar 2026
-26 points (6.7% liked)
Programming
26304 readers
936 users here now
Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!
Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.
Hope you enjoy the instance!
Rules
Rules
- Follow the programming.dev instance rules
- Keep content related to programming in some way
- If you're posting long videos try to add in some form of tldr for those who don't want to watch videos
Wormhole
Follow the wormhole through a path of communities !webdev@programming.dev
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
I hate to admit it, but I do work with Oracle Apex quite a bit. 15 years of experience to be precise. I've created several big applications with it which are running in production right now.
And still, if I had the choice I'd avoid it like the plague. This is 100% vendor lock in with very little benefit.
The only reason I'm using it is because it was already in use when I came into the picture and there was some know how in the team already. But guess what, those people left and now I'm the only one who really knows what's going on and has meaningful knowledge and experience in PLSQL, which you absolutely need if you want to create anything non trivial with Apex.
And of course finding people who actually know PLSQL at the level required to maintain those systems is very'hard. Who is going to learn an archaic procedural language which will only ever work within an Oracle database? Nobody within their right mind.
We tried introducing several rookies into this - all of them run away.
Another big reason to avoid it is that if you ever have the need to do something which is outside of what the generator accounts for, you will be fighting the framework constantly to still make it work and pray to the gods that no Apex update will break whatever you had to hack in.
There is really no reason any sane company should introduce this. It is not cheap. It is not easy outside of trivial things. The vendor lock in is huge.
Avoid!
I remember a similar experience. So much time was wasted just keeping some small app limping along with security patches because no one knew or wanted to know how it worked.
Pair that with oracle's notoriously useless support which always required you to be on the latest patch before even providing an answer and it made the decision to leave it in the rearview mirror the easiest part of some modernization effort.