Now, while I’m always up for some healthy debate on the strengths and weaknesses of different tools, there were some details in that article that I definitely couldn’t disagree more with. One that stood out was -
Apex is too proprietary compared to JDeveloper and is worse for your developer career path.
Too proprietary? Well APEX requires the Oracle DB to work if that is what he means, but as I commented on his blog, I wouldn’t expect to be able to take my PL/SQL procedures and compile then in MySQL either.
As for ‘worse for your developer career path’, I’m not entirely sure what that means? How do you measure that? Is there a statistic somewhere that I’ve missed that compares the number of out of work JDeveloper Developers versus the number of out of work APEX developers?
Another quote which leaped out at me was this one -
JDeveloper’s ADF will provide a higher educational stepping stone away from the old Forms market than Apex will
One of the other career benefits is, unlike if the Forms or Apex market dies
I’ve heard this argument many times too, it is always along the lines of “Use X, because if Y dies then we’re locked in”. Well what if ‘X’ dies first? Sure, sometimes you can make an educated decision about which market is more likely to survive, but what makes Chris think that APEX is more likely to die in the short to medium term than JDeveloper is?
If there is one thing I’ve learned in IT, is that there is *always* something new coming along, now that something *new* might be a completely new technology, or it might be an improvement in an existing technology, however the way that I have always looked at it is this….what can I use that will make my development easier *right now*?
APEX might die out one day, JDeveloper might die out one day, the Oracle DB might die out one day? Heck…I’ll die out one day, but does that mean that I can’t use a great tool because it *might* die out one day?
That argument just doesn’t stand up for me, in many businesses there are old COBOL systems still running decades after they were first written. Why couldn’t an APEX (or JDeveloper) application written today still be working in 3/5/8/20 years time, even if the development tool has long gone? I do not use a development tool, to use the tool itself, I use the tool to help me to achieve a specific *requirement*, for example developing an application to do ‘XYZ’. If I develop that application and it works, do I really care if the tool disappears in 5 years time?
Anyway, Chris said he wrote the article for this reason -
The other purpose behind this post is to start discussions about which *is* better, JDev + ADF or Apex.
So it will be interesting to see what other comments (beside mine) his post receives.