Beefy Boxes and Bandwidth Generously Provided by pair Networks Bob
good chemistry is complicated,
and a little bit messy -LW
 
PerlMonks  

Comment on

( #3333=superdoc: print w/ replies, xml ) Need Help??
(Note: you're entering into an area that I have a lot of interest in and have thought about for years, so please be prepared to back yourself up.)

You're presenting very real issues. Sounds like there's a number of excellent industries waiting to spring up. For example, garbage-collecting dead satellites and other debris. No, I have no idea how this would be done. Sounds like the perfect use for a field of some sort on a drone sweeping around the earth in an orbit that traverses the entire spherical shell of a given height. If all known satellites are in a database somewhere (another business opportunity similar to credit bureaus), there isn't a problem. If finding these satellites is a problem, that's another business opportunity. In other words, the cost of managing of all these items can easily be handled by entrepreneurs in the free market.

Now for lift costs. This is an interesting problem because it makes a lot of assumptions that may not be valid for more than a few years. So, let's talk about this.

Lets look first at what cannot be changed - the amount of energy it takes to raise the potential energy of a certain mass such that it is in LEO. That energy needs to be applied to the mass in such a way that it raises the potential energy without damaging the mass. The way that has been done thus far has been to use rockets which are extremely inefficient. And, they're more inefficient the closer to the ground you are. If we could only start our rocket halfway up, we would cut our energy needs by 75% (Inverse Square Law). There are easily a dozen solutions here, but they all have a rather high capital cost. Amortizing that cost is the key.

Now, why do we have to build satellites on Earth? Why can't we build them in orbit? If we could do so, we wouldn't have to make them so sturdy (to survive liftoff), which means they would require significantly less material. Since you'd have a foundry in orbit, you probably have power generation in orbit. Why not share that power generation capacity through beaming (a proven, if unused, technology)? Now, all you need is the actual purpose of the satellite. A lot easier to work with.

Furthermore, why do we have to have people in orbit to build these satellites? The cost of the ISS would drop by about 90% if it didn't need people on it. I'm not advocating a human-free space exploration program. In fact, I'm not advocating a space exploration program at all. I'm coming from the perspective of a space occupation program.

Basically, you find that the marginal cost of a given product (such as a satellite) drops dramatically if the proper infrastructure is in place. Very much like Perl when it comes to programming. I know you've discussed how productive you are in Perl vs. other languages in the past. That's due to the infrastructure you have. That infrastructure cost over 1_000_000 manyears (counting CPAN), but has been amortized into saving that many man-years every year. That's all that's needed in space, too.


My criteria for good software:
  1. Does it work?
  2. Can someone else come in, make a change, and be reasonably certain no bugs were introduced?

In reply to Re^3: "Practices and Principles" to death by dragonchild
in thread "Practices and Principles" to death by ack

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post; it's "PerlMonks-approved HTML":



  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • Outside of code tags, you may need to use entities for some characters:
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.
  • Log In?
    Username:
    Password:

    What's my password?
    Create A New User
    Chatterbox?
    and the web crawler heard nothing...

    How do I use this? | Other CB clients
    Other Users?
    Others making s'mores by the fire in the courtyard of the Monastery: (7)
    As of 2014-04-20 06:43 GMT
    Sections?
    Information?
    Find Nodes?
    Leftovers?
      Voting Booth?

      April first is:







      Results (485 votes), past polls