Every product is built to solve a problem. Before its implementation, its creators ask a question and come up with an answer which is the product. How should we stick nails to a wall was the question the creator of the hammer asked.
This question can be asked pragmatically by looking back in time. For example, for centuries humans asked how can we travel faster and decided to breed faster horses. Then Henry Ford came along. He asked the same question, looking into the future and came up with the automobile.
Back to our case, Apex is first built in early 00’s looking back in time and asking the question: “How do people write web pages?”.
Formspider is first built in 2008, looking into the future and asking the question: ”How should we build applications?”.
These two are fundamentally different questions and as a result you get fundamentally different products.
In Formspider, the entire application is defined without using client side technology. Therefore, Formspider architecture supports streaming applications to any device and platform that exists now or will exist in the future such as a browser, a Windows PC, a Mac, a mobile device that runs iOS, Windows Phone, Android or even Google Glasses as far as I am concerned.
Formspider has a world class transaction layer, that is fully controlled by the developer. A framework to build enterprise applications that has no transaction layer, but issues mandatory commits at certain times, is unimaginable to us. It’s ludicrous. It’s just bad design.
For a long time, PL/SQL developers could procrastinate making a decision or just go with Apex because there simply was no other choice. This is not true anymore. The ball is on your court now. As PL/SQL developers working at IT departments, ISV’s and system integrators, it is now your turn to ask the question:
Do you want a faster horse or do you want a car?
Yalim K. Gerger