Hacker News Reader

Comment by Retric | Hacker News Reader

Creating engineering jobs at NASA would be one thing, but creating jobs at a private contractor is vastly more expensive. That overhead is all about lining well connected people’s pockets.

It’s almost silly how much effort is put into making things as inefficient as possible. The federal government is intentionally given a bad reputation here, but it’s shocking how much more efficient they are internally vs outsourcing stuff.

View on HN

I had the same feeling. A lot of the things that NASA develops internally are mindblowing (e.g. the Mars rovers or the Casini probe, both developed by JPL), but everything subcontracted to Boeing or Lookeed endup uber delayed and hyper expensive.

If you are honest with yourself, the JPL missions are often insanely expensive.

The Curiosity rover was supposed to be 1.5 billion, but ended up 2.5 billion, and the main explanation of that was 'to develop a new landing mechanism'. Ok, I guess.

And now Perseverance is again 2.5 billion despite large parts of the rover, landing system and so on, were already 95% developed.

Not to mention it took 8+ years from Curiosity to Perseverance.

Space Nerds bitch less about these programs since they at least are successful compared to the human part of NASA but if you really look at the achievement per $ its not that fantastic.

Perseverance has plenty of sub-contracted parts.

For example, Maxar built several components: https://blog.maxar.com/space-infrastructure/2021/inside-pers...

> Not to mention it took 8+ years from Curiosity to Perseverance.

That is because the required orbit window is only once every ... 26? moments or such.

It's also worth noting that technically JPL contracts to NASA... It's actually part of Caltech under contract to NASA rather than a direct NASA organization.

I think it's somehow related to JPL's need to pay investors. Which doesn't exist.

John Carmack, of Armadillo Aerospace fame (and Quake too), once mentioned how they helped some NASA specialists in a project where their flying platform Pixel was involved. John said, that collaboration was the first opportunity for at least some NASA PhDs to actually work with flying hardware - years spent in NASA before that were all about papers.

> years spent in NASA before that were all about papers.

And the development of knowledge Armadillo relied upon.

Unless they developed their own CFD models for their rocket engine.

Reply on news.ycombinator.com