The F-22 and F-35 have a very important shared purpose: to keep my company stock shares up and my pension healthy.
@X3 Skier , you are absolutely correct - add the word "Joint" to any military program and you've doomed it to cost overruns, delays, and enormous inefficiencies. The objectives and methods of each service are different (which is why we have them), so when we write a "joint" requirement spec we often have to cover the entire skyline of each service's needs. This drives the hell out of the cost.
And it's not just the obvious requirements, like weight or airspeed. Consider electromagnetic interference (EMI), for example. The USN shipboard environment, with surveillance and landing radars in very close proximity to the planes, drives additional shielding, filtering, signal processing, protective grids, etc., way beyond that required for a strictly USAF application. Similar concerns find their way into almost every subsystem - electrical power, computer systems, flight displays, sensors, and on and on and......
We should chat sometime,
@X3 Skier . I was one of the developers of the IRST system as part of the YF-23 team. Kind of a weird tale, with the sad result that the F-22 does not have an IRST capability. I also had a hand in the development of the EOTS on the F-35.