Yea, fiber is great. They can do hundreds of terabits/s per fiber today, and petabits/s is not far away. Bandwidth is fundamentally cheap enough that my ISP offers 50Gbps residential service!
I live in Oregon. The price was $900/month last time I checked. I believe they do provide a QSFP+ module to plug into your equipment. They also allow residential customers, at any tier of service, to announce their own IP blocks via BGP.
Yea, I suppose if you gave the land to an organization dedicated to building parks then you could reasonably expect to get a park out of it. Of course, they might decide to build a garage to house and maintain their fleet of mowing and gardening equipment instead.
No, Kessler syndrome is pretty unlikely in this case. All of the guilty satellites are in Molniya orbits. Debris from destroying them would not greatly effect geosynchronous orbit or the low earth orbits used by Starlink.
Small power plants are less efficient and more polluting than larger ones. They are also harder to inspect and certify on a regular schedule. A single 1GW power facility in your county is much better than 10000 small power plants, one for each business.
True, centralized power generation using a grid that can carry that load would be the best solution. But in absence of that, the alternatives only seem to be between inefficient decentralized green and inefficient decentralized non-green solutions. In that case, I'd opt for the green ones. (Or of course: no datacenter at all)
LOL. You’d need thousands of acres of solar panels to provide power for a single data center. Of course the exact area needed depends on what part of the world you’re in, but are you going to put up with 4 square miles of solar panels in your city? That’s a square two miles on a side, or 3.4km×3.4km. Or are you going to let them install hundreds of wind turbines in your neighborhood?
There’s no reason that has to be a serious impediment. Just release all of the components, plus a terraform file that sets it all up properly.
In practice a lot of those components can be simplified when you don't have to support a huge number of players. A server that only supports dozens of players can just use SQLite instead of a big multi–az database cluster. The cache can just be an in–process cache instead of a connection to an external Redis instance, etc, etc.
You only need that fancy database when you have lots of users. When you release a server binary that anyone can run it doesn’t need to support quite so many. Have a compile–time flag that excludes the fancy database when set, and have it fall back to something simpler like SQLite or Postgres or whatever you want.
reply