If he wins, he can move some government offices in there on long-term leases, then declare it all as 'official' business so it's untouchable.
fubarx
joined 2 years ago
Help us Karl!
Would love to hear the line of reasoning that led to the intersection of Kinder eggs, drugs, and bums.
Buying an election. Gotcha.
“The first rule of holes: When you're in one stop digging.”
― Molly Ivins
Now only have to wait for:
- pyenv release
- pycharm update (including terminal)
- 3rd party libraries
to catch up…
It doesn't go straight from wafer to retail. The margins will likely be much thinner. There's also the cost of chip packaging, plus manufacturing a board you can plug into your computer or server.
Besides, every time a new process is introduced, the yields fall. Some of it may be salvagable so they go ahead and sell the parts at a lower price. That's how we get M3 Max, Pro, and regular flavor.
One of the key advantages of AWS had been that you could rely on a service being around long term. Anyone building a product/service around Google knows they're taking a risk that the whole rug can be pulled when they get bored with it. This isn't just for consumer services, but enterprise ones, like Google IOT (https://www.techradar.com/news/google-cloud-is-closing-iot-core-leaving-devices-stranded).
Having said that, it's been really disappointing seeing AWS slowly close down access to services like CodeCommit (which will have impact on other Code*) services.
The article lists a bunch of duplicative or half-baked services. The dupes at least give people somewhere else to go. And the half-baked ones (like Blockchain) never really got much traction but are still useful since you get the whole AWS security model and IAM access rules.
But deprecating CFN and CDK is the most braindead idea I've ever heard. I have no love for CFN and hope to never see another line of it in YAML or JSON ever again. And that also goes for Terraform.
The reason CFN is so slow is directly because of its state management and drift tracking, including rollback. CFN also closely tracks service changes so each time there's an update, all APIs, docs, and CLI tools update as well.
CDK was built on top of CFN because going back and creating yet another IaC interface and keeping it uptodate would be prohibitive, given how many services there are.
CDK is a great idea. Their L1 stacks give basic access to all CFN. L2 stacks make it dead easy to bring up services with sane defaults and without messing things up. L3 stacks make you feel like god, smashing together planets and creating galaxies with a few lines of code.
The reason they're slow is because there's so much state/drift/dependency tracking. The reason they keep a local cache is to try to speed it up. The reason you check the context into repo is so others working on the same project get all the benefits of caching and settings without now having to add yet another layer of cross-team consistency checking.
Advocating for closing down more services is just plain stupid.
I had the same issue, but my wife loved it. We have agreed to disagree.
Good thing they stopped emptying train toilets on the tracks.
Watch out. A Trojan's Horse!