People move towards places with growing economic opportunities.
New York heavily restricts construction and infrastructure projects of all kinds. The tech and finance elite will stay here but normal people who are trying to make a decent living in construction and similar trades will end up following opportunities.
NYC population is declining after all [1] largely because the city would rather treat housing as a scarce resource for them to divy up than something to increase the supply of.
People move towards places with growing economic opportunities.
I hope people aren't expecting data centers to provide "growing economic opportunities". That's not really what data centers are about.
Data centers are infrastructure in the same way nuclear plants or canals are infrastructure. Water infrastructure carries the Colorado to Phoenix and other areas in the West. Unfortunately, this does little for people in Colorado. The idea is that the benefit of feeding water to people throughout the west is worth the cost of building and maintaining extensive water infrastructure.
AI infrastructure should be thought of in the same manner. If you're going to have a requirement that data centers provide all these jobs in the places they're built, then data centers are never going to be able to get out from under the PR hammer. And most citizens are going to continue to be disappointed. Because they're thinking about it wrong.
> People move towards places with growing economic opportunities.
Fleeting economic opportunities that don't survive the construction phase - a few months most. No one will move from New York to Texas for a chance to be one of the 17 long-term staff at a data center: no one wants to be a data center night man that badly.
> NYC population is declining after all [1] largely because the city would rather treat housing as a scarce resource for them to divy up than something to increase the supply of.
The Mayor is literally implementing stuff to build more affordable housing. I agree that ultimately a lot less regulation is needed to make it easier to simply build, but your take on it belongs in a New York Post editorial. It's not serious.
> The tech and finance elite will stay here but normal people who are trying to make a decent living in construction and similar trades will end up following opportunities.
Your dichotomy is bullshit. People in blue collar trades are no more "normal" than most of the people working white collar jobs in tech, finance, law, etc.
The mayor of NYC froze rent... rent controls are the opposite of building more affordable housing, since it disincentivizes building and renting units.
That's not the only thing he has done. There are also initiatives to actually build it, which I agree is the correct response over rent control (which is more of a bandaid, and a bad one at that).
I don't think rent controls disincentivize building more because not all buildings can be subject thereto.
Affordable housing is literally treating housing a scarce resource for the state to divide up. It’s good for people who are already in the system or able to get into it but bad for everyone else. We just need radically more market rate supply rather than trying more affordable housing which has been a total failure. It is time to try supply side reforms.
> Your dichotomy is bullshit.
Middle class is the 25th-55th percentile of income. Most workers in tech/ finance/ law are above the 55th and most people in the trades are below it. Teachers and the like aren’t going to directly benefit from construction, but would atleast benefit from property taxes.
It’s largely used for syncing external open source projects with the monorepo. Policy is to require source code imports over built artifacts. Though you can get exceptions.
Some projects are also developed in the monorepo and exported via Copybara.
My team also uses it to version Starlark rule sets internally.
Source code imports versus artifacts really neither here nor there. Go is source code imports too.
The key part for Copybara is that Google will make changes to the OSS projects from within the internal repo and everyone else will make changes to the OSS projects.
Well kind of, or you just end up copying the poisoned version directly into your repo rather than having it as a dependency. Same outcome.
I suppose if you're running some security analysis on code in your own repo, the fact that you've copied the code in means that it'll run on your third party dependencies too, since they no longer appear to be third party.
It just came out the Kalshi outright gave Donald Trump Jr a $300k stake in the company when it made him a “strategic advisor”. That’s the name of the game now
It's not all sunshine and rainbows. Countries are turning to coal as well. There aren't natural chokepoints for coal distribution like the Straight of Hormuz.
> For anything with native UIs, I suppose you could "remote desktop" into an app or a simulator running in the cloud
This does exist. The network isn't the main problem. The Emulator has to run under nested KVM. That + graphics rendering on the CPU makes it not so responsive. It's useable enough in many cases though.
