One mistake that the article seems to make is to assume that the data center is in one huge satellite.
I think a better model would be a fleet of rack or server level satellites. That significantly reduces the heat and cooling requirements and improves redundancy since losing a single satellite sure to radiation would be less significant. Further, due to economies of scale these satellites could be produced in mass, similar to the starlink satellites of today.
One issue is that these satellites would be to be connected via high bandwidth free space optical links instead of Ethernet, requiring precise formations, but that is currently being tested by multiple companies.
That being said, I don't see this ever being cheaper than terrestrial data centers. I just don't think the idea is as stupid as the article implies - it just requires doing things differently than NASA has done in the past.
It doesn't help that new builds seem to focus on the high end for housing (because that is where the profit is). If we keep building more expensive housing it shouldn't be surprising that the average cost of housing increases.
People buying their first house almost never got new housing - ever. They’d buy a starter home, which was older, needed some work, etc.
A big issue here is expectations - people are complaining because they can’t buy their own standalone house in a good neighborhood right next to work - while work is in a high demand, high pay area.
Also, well paid work is centralizing, so so the gradient is getting steeper (or was, pre-remote work).
Guess what, that was never the norm!
But a lot of people did buy in what were at the time low demand, high supply, areas that later became high demand areas! Like early Los Angeles.
Also, everything is getting more expensive relative to ‘hour worked’ because of centralization of capital, and more work force participation.
No, what doesn't help is that the new builds aren't nearly enough. If they were quantitatively sufficient, it wouldn't matter if they all targeted the high end, because the people moving in to it would be pulling demand away from other existing units, with a ripple effect across the whole market.
What many people don't realize is how badly the total housing inventory has fallen behind what is needed for the population since the Great Recession.
It absolutely helps - people who move to high end housing free up other, cheaper apartments (recent economic paper has clearly showed that this works, you can easily find it)
To be fair, in that particular instance they were only welding the back door. They left the front door alone so that people could go out (at their assigned days and times). They got rid of the back door to make it so that community enforcement of these restrictions was possible.
At the level the epidemic reached in some area of China that may have been necessary to slow the flood, no different than rationing during famine.
I have some issues with China (corruption, nepotism, pervasive tracking), but this is not really one of them.
There was a total revamp to GMail called "Inbox" that Google was working on for a while, but it got deprecated and cancelled before it was released. From what I heard, they were testing it internally and most people liked it. It just was more search focused so the backend costs were more than they thought they could bear and it was scrapped.
I loved Inbox, it was way better at organizing than gmail. In true google fashion, as soon as people started to like it and use it, they unceremoniously killed it.
That's exactly right. For a long time people of color were relegated to lower paying jobs and faced higher police scrutiny. Similarly, less than a century ago women were practically property - unable to even get a bank account without a man's permission.
Over the past century we've made significant progress in remediating these injustices. Unfortunately, this has caused the recent rise in reactionary politics. "Make America Great Again" = take me back to when women were property and people of color knew their place.
As for me, I'm willing to put up with a few tantrums if it means that we're that much closer to treating people as people.
As for the benefit of restricting the Ladies rooms to people that are assigned female at birth, that is less of a benefit than you seem to believe. How do you expect they will enforce such a rule?
So far this has resulted in countless women being groped in attempts to prove that they don't belong in the Ladies' room and a comparatively small number of trans-women with no where to go to the bathroom. Can't you see that this effectively punishes those women who don't meet a stereotypical view of women? Catching fictional trans-women peeking on women in restrooms is just the excuse! (Of course even you would understand that if you understood even the basics of gender dysphoria disorder).
As for your other point, well racists always have that one black friend - you know, to prove their not racist. And it seems like it's pretty profitable to be a token black or Hispanic person in the maga MAGA movement.
The reason I get so mad for people to push all this shit is because it's so disingenuous and it's all lies. It's all lies mostly fed by the media machine. So fucking glad it's all dying.
Why complicate things? Existing taxes are the ones which it would be sensible to start with, and existing taxes on things which we can't easily make more of (land, air, water etc.) are the sensible things to start with of those again.
Skilled labor is not currently taxed as a specific thing, and we can make more of it by educating people, so why on earth bring that up unless it's a setup for some odd rhetorical point?
It's impossible because actually removing precarity from people's existence would mean that they wouldn't need to to toil so existing capital owners could capture the value they create in return for being permitted to have a home. The implicit threat of ruin is a feature, not a bug. It's why housing must always be kept scarce.
It's pretty good at Rust, but it doesn't understand locking. When I tried it. It just put a lock on everything and then didn't take care to make sure the locks were released as soon as possible. This severely limited the scalability of the system it produced.
But I guess it passed the tests it wrote so win? Though it didn't seem to understand why the test it wrote where the client used TLS and the server didn't wouldn't pass and required a lot of hand holding along the way.
I've experienced similar things, but my conclusion has usually been that the model is not receiving enough context in such cases. I don't know your specific example, but in general it may not be incorrect to put an Arc/Lock on many things at once (or using Arc isntead of Rc, etc) if your future plans are parallelize several parts of your codebase. The model just doesn't know what your future plans are, and in errs on the side of "overengineering" solutions for all kinds of future possibilities. I found that this is a bias that these models tend to have, many times their code is overengineered for features I will never need and I need to tell them to simplify - but that's expected. How would the model know what I do and don't need in the future without me giving all the right context?
The same thing is true for tests. I found their tests to be massively overengineered, but that's easily fixed by telling them to adopt the testing style from the rest of the codebase.
Yep, LLMs are basically at the "really smart intern" level. Give them anything complex or that requires experience and they crash and burn. Give them a small, well-specified task with limited scope and they do reasonably well. And like an intern they require constant check-ins to make sure they're on track.
Of course with real interns you end up at the end with trained developers ready for more complicated tasks. This is useful because interns aren't really that productive if you consider the amount of time they take from experienced developers, so the main benefit is producing skilled employees. But LLMs will always be interns, since they don't grow with the experience.
If you're not using separate domains then I hope you don't have any kind of sensitive information stored in cookies. You can't rely on the path restrictions for cookies because it's easily bypassed.
Strict cookies crossing root to subdomains would be a major security bug in browsers. It's always been a (valid) theoretical concern but it's never happened on a large scale to the point I've had to address it. There is likely regression testing on all the major browsers that will catch a situation where this happens.
I think a better model would be a fleet of rack or server level satellites. That significantly reduces the heat and cooling requirements and improves redundancy since losing a single satellite sure to radiation would be less significant. Further, due to economies of scale these satellites could be produced in mass, similar to the starlink satellites of today.
One issue is that these satellites would be to be connected via high bandwidth free space optical links instead of Ethernet, requiring precise formations, but that is currently being tested by multiple companies.
That being said, I don't see this ever being cheaper than terrestrial data centers. I just don't think the idea is as stupid as the article implies - it just requires doing things differently than NASA has done in the past.