There are pretty good reasons for believing that a key to the improved environment on Earth will be the migration of many processes off the planet. I'm not a particular fan of Space Solar Power, but it's definitely in the running. According to experts in the field, SSP could eliminate all of the power plants on Earth (both fire-based and nuclear) and provide easy cheap power everywhere for less. (IMHO it would be cheaper in the short run to just build big solar facilities in the Sahara, 30 feet off the ground. This would generate plenty of power and provide a new resource underneath - shade where things could be grown.)

As someone who is involved (peripherally) in the "New Space" movement, IMHO the first purpose of space development will be the availability of new resources and technologies. An economist a couple of years ago predicted that space development would have the potential to increase the standard of living of everyone on Earth by a factor of 10. That seems optimistic to me, but a reasonable goal. One popular example (see Planetary Resources, Inc.) regards the availability of Platinum, which is a very useful industrial metal, but is unfortunately $1300 per ounce. Platinum mining is expensive, dangerous, and disastrous both ecologically and socially. This greatly restricts is usefulness although it is used in those expensive catalytic converters in your car - that's why they're expensive. The best astronomical physicists believe that some of the Near Earth Asteroids contain single-digit percentages of Platinum. If this is true, then a 100 meter asteroid would contain a dozen times as much Platinum as has ever been mined. Retrieving this material to Earth could drop the price to between $10 and $100 per ounce, and this would still be economically viable for the company to process in space and ship it down to Earth.

There are many other examples. Technologically, the range of industrial processes that are presently either expensive or impossible on Earth due to gravity and air, that could be done in the high vacuum and microgravity of space is broad but it is likely that an order of magnitude more new processes that have not even been envisioned yet will be discovered or invented. Orbital production of high quality integrated circuits might well be one - one of the most expensive aspects of IC manufacturing is the requirement to build a huge facility and maintain a high level clean room environment. In space that could be done with not much more than a bit of Mylar.

I expect those who grow up in space, or in a colony, to be habitually _very careful_. This puts 'kidproofing' at a whole new level.

Just fyi, an MSR can be built small enough (both weight and dimensions) to be driven around in a pickup truck.

Well the nice thing is that there would be plenty of open space. I'm not sure why one-inch steel - steel doesn't seem to be an ideal material for this. I don't know what the effects of all that sulfide would have on carbon, but if it can be made resistant I would think seriously about starting small with a probe that can produce a carbon-based skin and build a bigger balloon for itself.

Just to be clear - size is not largely irrelevant. The whole key to buoyancy is that the volume of a sphere goes up as the cube of the diameter while the surface area goes up as the square - for a non-sphere it's based on the three linear dimensions of course. So a very small craft can barely carry the skin, while a large one can carry much more in addition to the skin. There are other factors, but that's the primary one.

For example, a one-foot box made with one inch steel would not float well.

I can't imagine that the DoD would be happy with DHS clowns guarding something that they actually cared about. Though, if the alternative is G4S, maybe they'd take it. I'd certainly want to be rid of whoever thought that training with doctored MILES gear was adequate.

I recall not that many years ago when the prospect of a teraflop processor was science fiction. That was about 1992. A year or two before that I worked on some photometrically-correct ray tracing code, porting it to the Cray X/MP. That code took a month to make one 1024x1024 frame on the top-end Apollo workstation, and a few minutes to run on the Cray. It could probably run at close to 30Hz on my phone today, and today's supercomputers are in the 30+ petaflop range, i.e. 3x10^16.

So we're getting close - theoretically, if all of the top 100 supercomputers got together, the group performance would be in the 10^19 range. :) Actually that's not a bad idea - the powers that be could work a deal for all of them to work together for one week per year on the same problem, and the research time could be allocated the way that telescope time is allocated according to accepted/agreed value of a particular project.

The link - http://www.infoworld.com/artic...

I had an idea a while back, that actually relates to TFA. Genetically engineered bacteria or simple organisms that could float and live in the Venusian atmosphere and gradually begin to 'fix' the sulfides and whatever - maybe pooping out metallic sulfur. For the first long while, they would be working at the top of the atmosphere. Their poop would drift down and re-vaporize (absorbing energy and lowering the temperature). When they died, they would drift down into deeper layers and get to the point where their bodies would be heated back up to the point where the materials would be turned back into gas. But as they became more populous, gradually they would reduce the amount of solar energy (especially if their bodies were reflective), and the temperature. Eventually the might be able to reduce the temperature to the point where their poop, or that of their successors, would fall to the surface, permanently eliminating the sulfides from the air.

You are trading off a shutdown to fix a pump versus a meltdown. The trade-off is a short controlled shutdown, a quick fix, and a fairly quick start-up which is probably measured in days to a week versus an emergency shutdown because your pump failed which means that your reactor is offline for a number of weeks at a minimum. The chance of a meltdown due to a single pump failing is infinitesimally small (though if the other employees are like you then the risk of an incident increases greatly).

1. Not all startup founders are 'white people' and not all of them are 'privileged' either

2. Most of the startup founders do not commit suicide

3. Stress level for startup founders - no matter what kind of startup - is high, but this is natural, as the journey of starting up a new company (in any industry) is a rocky road filled with a mix of excitement / trepidation / frustration

As for the percentage of the excitement versus that of trepidation versus that of frustration largely depends on

A. The regional / global industrial environment in which the startup is involved with

B. The structure of the startup

C. The corporate culture of the startup, ie, the attitude of the close-knit of people working in the startup

D. The personality type of the founder himself or herself

I personally have involved in quite a number of startups and every single one has their own perculiar 'pain of labor' - and for each of the 'pain of labor', if the founder sees it as a 'challenge' it would be tackled with zeal. However, if the same 'pain of labor' is seen as 'trouble' then the thing could become a protracted problem for the company

The above is based on my own experience

YMMV

The 'feature' occurred on Windows Phone first, not sure exactly what version. I assume that it made a great pitch to prospective carriers, since they all love offloading customers onto anything that isn't their data network as often as possible, and typing passwords into your phone is a pain, so automating it likely increases network offload considerably.

Just as they say, in the context of backups, that 'if it isn't automated it won't happen'; there is likely to be a considerable difference in the rate of unintended leakage between a 'yeah, I guess I did tell Bob the password, he could pass it on' and 'the password spreads through your entire social group like a bad chain email'.

This sort of 'friend/acquaintance' attack attack is also exactly where slightly-too-automatic automation makes it really easy to bypass what limited good sense about security humans do have.

If, say, Alice and Bob have just had a messy breakup; it would be fairly obvious to any mutual friend of the two that sharing one's wifi password with the other, or a known friend/agent of the other, is something that they wouldn't like. They might do it anyway; because people are assholes like that sometimes; but it would be deliberate. Social-engineering somebody in that situation into telling you the password might be vaguely tricky. Social-engineering them into making you enough of a contact/friend/whatever on the services that this 'wifi sense' system uses to receive the password should be absolutely trivial; quite possibly already done.

I suspect that it isn't for nothing that this 'feature' first appeared on Windows Phone; carriers adore the idea of getting the filthy customers off the cell data networks they pay for and onto wifi as often as they can, and don't much care about a bit of collateral damage inflicted by dumb implementations.

The job of the init system is actually to change the system state, and hopefully to be able to guarantee that it does so. Scripts have some inherent limitations in this regard, which is why even OpenRC relies heavily on C libraries. Understanding why people have been trying to replace SysV init for the last two decades would make a lot of Systemd's design decisions more clear to you, I feel. However, I do feel you are entirely mistaken if you think there is some propaganda movement to label it as 'just' an init system. System initialization is only a subset of the problem at hand, and even the name was chosen to reflect that.