As I see it, the complete deprecation of the Gauge API presents developers with a dilemma.
If they wish to support both MSFS 2020 (and earlier versions up to a point) and MSFS2024 they will be forced to make a big decision:
-
Continue their existing and future development using only the deprecated Gauge API, which will enable their application to run both MSFS2024 as well as earlier versions, or
-
Focus new development on using the newer Vars API, Event API etc… to future-proof their products.
Taking option (1) is easy. It demands no significant changes in code, will continue to run OK on all versions of MSFS (and others, probably). However, it runs the risk that new features introduced in MSFS2024 and later may not be available because they can only be accessed via the new APIs.
Option(2) would mean developers will need 2 versions of their application if they wish to develop comprehensively for both MSFS2024 as well as earlier versions – one using the legacy APIs to run MSFS,2020 and earlier, and one using the new APIs to run MSFS2024 (and beyond?).
New developers just starting will also need to make the same decision. Do they develop only with the future in mind (ie use the new APIs), or do they also target versions of Flight Simulator earlier than 2024? If they only develop with the new APIs, their work won’t run on versions earlier than 2024. That’s a lot of market to miss out on!
The connotations here are obvious (I believe) so I won’t dwell on them
I suspect many developers will be forced to take option(1) because they won’t be able to absorb the difficulties of supporting 2 versions.
Maybe I’ve missed the point completely and if so please let me know (politely!).
I make the assumption that making the new APIs backwards compatible with earlier versions is not a possibility.