Hi TomTom wrote: ↑Mon May 05, 2025 1:28 am Nowadays, nobody would build an ERP system like it was done in the 90's. An ERP system should be build in a modular structure, highly scalable and on the user side completely platform independent. Tools like Kubernetes, Docker, Istio, Kafka are used for the microservices and their environment, Java, C# and others for the backend technologies. Whatever you add to your Xbase++ biotope, it's located on a lonely planet and completely lost in space.
This is true when you want to build something that lasts a while, created by a bigger team for a bigger company and/or market.
If you work for a company that can afford to work mainly with Windows monoliths, which may involve additional backend structure with web frontends, then you can also develop large parts of something like that with Xbase++. However, I can't imagine that there will be a generation change for Xbase++. The community is getting older and smaller, and there is no future for this in sight. You still can build highly integrated, genius applications with Xbase++ (we all do or did), but you will be the last person working on it.
Languages such as C, C++, Java etc were already in existence before the creation of xbase++ but we opted for xbase++. I recalled Roger wrote a beautiful article on why xbase++ choice is prefer even over visual basic, Delphi etc. For me going back to any of those is like Israelites going back to Egypt and is not a choice at all.
I am equally not sure that Alaska will agree with you that their product is becoming obsolete.
The most important language understood by developers is productivity and that is what xbase++ brings to table.
Joe