Block.00/00

/*Legacy Meets Innovation – Reimagining DataFlex For the Future*/

Colleague, profile, blog, orange, dataflex
By Harm.Wibier

One thing’s for certain: technology doesn’t stand still for very long. While the rate of change varies, for development frameworks like DataFlex, it’s a necessity. That’s why an ever-growing number of devs have put their trust in our robust and reliable coding framework.

Our dedicated and vibrant global programming community has grown up around the DataFlex product. While we’re proud of this legacy – long may it continue – we recognize the need to broaden DataFlex’s appeal for the future, reimagining our framework, so it stays relevant and innovative for the next 50 years.

That’s why 2025 is set to be a big year for DataFlex. It’s the start of a new era. Here’s a flavor of why and how our flagship coding framework is changing.

Here’s why DataFlex is changing

Change is part of the Data Access DNA. Born in the late 1970s, over the last 40 years or so, DataFlex has never stopped evolving. In that time, the framework we know and love today has effortlessly adapted to changes in technology. It’s outlasted multiple development fads and accumulated advancements that offer genuine value and increased longevity for software products. It’s also rare for features to exit DataFlex unless they’re technologically redundant or radically underused.

We’ve always strategically evolved DataFlex to accommodate new technologies. For decades, we’ve made iterative improvements, adding new features and functionality, but the runtime stayed the same. Today, we know that to better serve new and emerging devs – as well as retain the loyalty of our existing user base – it’s time to overhaul the runtime as well. We’re talking about the new Technology Stack...

Coming next in the DataFlex evolution

With the new Technology Stack we’re rebuilding the runtime from the ground up. This doesn’t mean we’re going to sacrifice all your favorite features and functionality from the past four decades. The goal is to take our single language and framework forward by rebuilding the runtime, all the while evolving the Studio, framework and language. Just like we’ve always done.

DataFlex has always been different, putting all your code in one language and one framework. There are good reasons for this. When code contains multiple dependencies on third-party tech, it can lead to unwanted technical debt. Just one insecurity in a single dependency can create a vulnerability or lead to compatibility problems. That’s why upcoming iterations of DataFlex will take development beyond Windows and web apps.

In the future, the updated DataFlex framework can potentially become compatible with a range of OS including Linux, macOS and Windows, as well as giving you the ability to code offline apps. All of this via one codebase. No other programming language and framework can do that. 

Want a closer look at the new Technology Stack plans? Rewatch one of the livestreams where Bram and I reveal the roadmap and answer every question from the live Q&A.

 


 

Note: This blog is based on a great chat with Harm, written by our copywriter.