Reason 11 For Not Building Data Centers Now

A few stories recently caught my eye about moving data centers away from where we live, far away, in fact.

 China's government plans to test space-based data centers starting in 2026, with a rollout of ones with costs as low or lower than earth-based centers slated for the 2030s. Meanwhile in the States, Amazon's Jeff Bezo has hatched similar plans. Not to be left behind by his billionaire rival, Elon Musk wants to use his Starship mega-rockets to orbit data centers. Then there's Google Starcloud, with a test planned for 2027. That system would also depend upon something like Starship to make the venture cheap enough to construct.

At first blush, it seems like a crazy idea, but as I considered the benefits versus costs, it makes sense to move this industry skyward:

• With reusable rocket boosters, costs to orbit per kilogram have dropped radically in recent years. If Starship prospers and others copy its model, we'll see the door opened for very cheap rocket launches.
• We have abundant solar energy in orbit. There's no need for generators, nuclear reactors, or natural gas.
• We also have easy cooling, without using water. Rotate a satellite and you have a solar heating on one side, the utter cold of space on the other.
•  Space-based data centers need not be huge to do their job. They could be a constellation of large satellites that talk to each other, as Starlink does already. Right now, however, big centers seem to be the model for space-based construction.
• If we do go big, we know how to do this already thanks to the International Space Station. 
• Parts of orbital centers can be replaced with one launch, and the old centers can be upgraded by robots or small enough to burn up on a deorbit. 
• Beaming data to ground stations 200 miles away on Earth is not a problem. We already do this.

My hope is that this technology will mature fast, to avoid more environmental and social disruption on Earth. And closest to home, I hope my County's Board of Supervisors pays attention, before we end up with a huge and obsolete building placed on agricultural land next to residences.

One issue that does bother me, beyond the possible climate-change effects of launching so many rockets?

It's called The Kessler Effect (or Syndrome). Readers may have seen the film Gravity, which one explosion in space results in a cascading set of collisions and, consequently, a massive cloud of space debris hurtling around 10 miles per second, chasing an underwear-clad Sandra Bullock.  

How serious is a collision in space? I once saw a piece of Space Shuttle Challenger's front windows, removed from a mission before the craft's 1986 catastrophe. The section of thick glass was damaged badly by hitting a tiny fleck of paint tossed off some forgotten rocket-booster, perhaps decades earlier. Now imagine millions of these objects, large and small, forming a cloud around the Earth, making any rocket launches an exercise in futility, destroying telecom networks, and grounding human space travel for many decades. Or centuries.

A center as large as Starcloud makes for a huge target, were the Kessler Effect to begin. 

Belatedly, firms and governments are considering ways to mitigate space debris and harden orbital infrastructure. Let's hope they get is right, as they'll only have one opportunity. I'd like to get my data from the heavens, not from Earth with more carbon pollution and wasted groundwater.

image: Starcloud center from Google video 

A Strangely Easy Idea No Writing Teacher Has Discussed

I may be out of the loop here, but I've come up with a simple idea that may be grant-worthy. Yes, steal it. Beat me to the grant. The consequences for students' learning may be too great for me to worry about being the first to put my name on it.

What I propose is simple: a writing environment online with the ease of Google Docs, but with one enormous feature disabled: copy/paste. In that regard, it would resemble the Respondus Lockdown Browser. 

The difference? Faculty would organize their classes and assignments there, as with a learning-management system, but they would pick certain AI tools that could employed at each stage of the writing process. The tools would work only from within the writing environment, and the final stages of each step--from rough-draft to revision to later drafts--would be sent from within the browser to the faculty member, along with how each writer used any AI tools permitted.

In that regard, my writing environment looks something like an educational version of Grammarly that an executive once demoed for me. In that product, all work copied and pasted into to interface would be watermarked and AI tools could be disabled or enabled by the user. I'd put that power in the hands of the course instructor, where it belongs. As students tell me again and again, using AI is simply the norm now, and we faculty are wasting time focusing on detecting plagiarism with AI detectors I don't trust. Time and again, studies I've read indicate that they turn up too many false positives. 

My idea requires some coders adept at building a good client and we'd have to negotiate licensing for AI programs such as Research Rabbit, an LLM, a image / slide-deck generator, and multimedia tools such as ElevenLabs' podcast and text-to-voice generators.

By placing the tools within the writing environment and forbidding copy/paste from outside, drafting by cognitive offloading would no long be an issue. 

I'm currently talking to a few colleagues who run our AI cluster on campus. I hope to have something sketched out, and if we can find the coders and money, tested in 2026.

Creative-Commons Image courtesy of oercommons.org