Not really. Frankly, if I had a time machine, I'd go back to 2002 and pull the plug on the F-35 program. The problems - well one of the big ones anyway - with the F-35 can be best explained in comparison to its predessor the F-16.
The F-15 predated the F-16. When the F-16 came along, it took F-15 technology, modestly improved upon it, (full fly-by-wire, side stick, bubble canopy, better avionics), and put it in a single engine aircraft. They're cousins.
The F-35 started as a derivative of the F-22. But it grew into something very, very far from the F-22. It's almost entirely different. There were some good reasons for that. The F-22's Cray Supercomputer is notoriously difficult to program for, highly insecure, poorly documented, and not at all suited for a "plug and play" open architecture that was desired for the F-35. But putting aside the airframe compromises made by the Marine's inclusion, the F-35, the first real information age fighter, was just too far removed from the F-22 compared to the relationship of its predecessor. Had it been largely an F-22 in a single engine, smaller package, the program would have been in full scale production years ago. Instead, they basically tried to do a sixth generation fighter with fifth generation technology. The Air Force, Navy and Marines presented a wishlist, and Lockheed didn't really say "no".
In that alternate world, where the F-35 is significantly less advanced, but also wholly replaced the F-16 years ago, than the US would probably be flying F-22 successor aircrafts now. Instead, because of protracted development, the key question is, if the US restarts F-22 production, to just start making old F-22A's or integrate as much F-35 tech as possible on the F-22 and make an F-22C. It's a pretty shit situation overall.
It's too late to abandon the F-35. But the F-35 also is a real quantum leap forward in many respects. We can only just hope to do better next time.