117
edits
Fr/How the FlightGear project works: Difference between revisions
Jump to navigation
Jump to search
Fr/How the FlightGear project works (view source)
Revision as of 10:07, 16 January 2016
, 16 January 2016→Lack of Support and Backwards Compatibility
| Line 111: | Line 111: | ||
== Lack of Support and Backwards Compatibility == | == Lack of Support and Backwards Compatibility == | ||
(traduction en cours) | |||
FlightGear is a volunteer effort and no one is paying several thousand dollars a year for software and related support each year. Since legacy support is expensive (IE. time/effort) one of the ways a project like FlightGear deals with this is to limit legacy support. If this were not the case then time/effort would be expended on legacy support that could be used for new features and bug fixes. Like most things there are trade offs involved. Which do you want - more advanced FlightGear and aircraft or better support for older versions? This is a common issue for open source software and most prefer to look forward rather than looking back. | FlightGear is a volunteer effort and no one is paying several thousand dollars a year for software and related support each year. Since legacy support is expensive (IE. time/effort) one of the ways a project like FlightGear deals with this is to limit legacy support. If this were not the case then time/effort would be expended on legacy support that could be used for new features and bug fixes. Like most things there are trade offs involved. Which do you want - more advanced FlightGear and aircraft or better support for older versions? This is a common issue for open source software and most prefer to look forward rather than looking back. | ||