These days low-code development is en vogue. Various research groups, such as Gartner, put the low-code application development platform market at ~$10M billion in 2019 and project CAGR to be greater than 20% from 2020 to 2027. In contrast, the market for developer tools has largely remained flat, and growth is estimated to be under 5% at best, largely driven by the wide proliferation of open source.
Why is this important for Delphi developers? Let me first start with a quick overview of low code, since many developers are not familiar with the concept. Low code is a software development approach that requires little to no coding in order to build applications and processes. A low-code development platform uses visual interfaces with simple logic and drag-and-drop features instead of extensive coding languages. Low code is hardly new. Twenty years ago, 4G scripting languages aimed to simplify development by abstracting low-level languages, such as C++, into more simplified scripting languages. Some of these were purpose built (e.g., SAS), and others were more generic (LANSA, UNIFACE, etc.). Many of the latter have now evolved into low-code platforms.
Frequently porting these pieces of the app into the IDE is not that easy, or at least the low-code aspect is lost. For example, you can “expand” Mendix with Java.
While many low codes promise no-code approaches, this is frequently not practical for robust apps that are scalable and performant. It is no accident that all low-code platforms rely on armies of consultants and professional services.
The main benefit of low code is that you need fewer developers, and people can learn the system fast. Well, that is the secret of Delphi. You need few developers, and learning Delphi is probably as easy as learning any one of these low-c-code platforms. The real Delphi experts know Delphi. The real experts for these other platforms have to know so much more. The Delphi community, which may not be as large as that of C# or C++, is vast compared to any one of these low-code approaches. Finally and importantly, RAD Studio comes at a fraction of the cost of any other low-code solution.
So next time someone asks you to explain why you love RAD Studio and Delphi, just tell them: It is just like having a low-code solution but much better!
Design. Code. Compile. Deploy.
Start Free Trial Upgrade Today
Free Delphi Community Edition Free C++Builder Community Edition
Hi Atanas, yes VCL RAD components has allways been fantastic, an buying Firemonkey has proved to be a genious move that enables Delphi RAD on mobile and even Linux, or more platforms. And styles is a great addition that makes everything look great magically.
But when you speak about web,then buying Extjs is another great idea. A great idea, that I believe,
And maybe he does not want to sell, but it’s where little compagny make the most money, when they get sold to big ones, it should be their goal.
And no it’s not a problem for good competitors like TMS, they wait anyway until Dephi compiles to WebAssembly 😉
VERY WELL SAID
I SECOND THAT — GREAT COMMENT AND I AGREE .. buying UniGUI would be a great move loved by the comunity .. WebAssembly as compile target for Delphi is a scenario to dream for as a future road ahead .. i think for all in the comunity even that some has not realised it until they see it AND if it is there.
As newly employee at University in 1982, one of my prime works was to be responsible for an Altos 8000/7 4 user Z80A based computer to help the secretaries to do a better job, but also let other employees (professors etc) and students give better opportunities, but the effect was that one of the secretary started a war againt the institute leader and me and put forward lots of lies and scaremongering about using computers like health threat by dangerous irradiations and lot of other.
Same may apply to Delphi if the developers feel their boss will fire 90% of staff because Delphi makes it so much easier to make a product that works.
Instead, why not focus on the possibility to make the products more scalable by dividing development woerks having one group tying together the components used and when functioning, let another group that risk getting fired do the work to intorduce using interfaces and make the code MVVM functioning.
And if still to many emplyees, use those to make new products after lets say a run of crowdsourcing challenge, like using Something liike Spigit Engage, (https://www.google.no/search?q=spigit+engage)
By the way, maybe there should be a market for a Java -> Delphi tranlator ??
Low code tools and frameworks hide the engine, but in order to create optimal solutions, you have to aware of what going on under the hood, so when things go wrong (crash, slowdown,…), you can diagnose and fix things.
With Delphi you can always take a look under the hood (codes with a full source), examine the engine and figure out if it’s the problem in the engine or your code.
But, at a fraction of cost? It’s like comparing a rollsroyce with a mars mission, the car costs a fraction, but still few spend money for it.