Well suited: for interfaces between machines data and applications. Made as a service. For web applications in factories where you don't have access to thick clients due to the environment. not well suited: quick measurements and fast data transitions between different applications. When time dependency is needed, then you better can choose other solutions.
Legacy applications already on VFP are a good candidate. If you plan to move to iOS and Android apps, VFP is not for you. Also, in future access to VFP programmers may be limited. You could use VFP as a powerful database tool. I know of many programmers who love to exploit the features of VFP to create easy to use applications.
Although MS has discontinued support of VFP there is a good community of programmers that are available for help. In fact we have several programmers at Apptread that are skilled not only in VFP but also .NET so that if there is a need to migrate some parts of applications to .NET , it is easy for us to do that.
We choose ASP.NET because our core business is working with the SAP HANA database using SAP Business One. We can develop state-of-the-art applications with Razor and Visual Studio 2022 fast and with excellent application performance response. Working SAP Hana with JAVA could be more challenging because it has fewer developers communities, and it could be harder to find a solution for a question.
We are only using FoxPro because it is the only way to add custom plugins into the software we use to manage our stock. FoxPro is a semi-oriented object language and should clearly not be compared with recent technologies.