The migration sharing is admirable and useful teaching, thank you!
I see the DigitalOcean vs Hetzner comparison as a tradeoff that we make in different domains all day long, similar to opening your DoorDash or UberEats instead of making your own dinner(and the cost ratio is similar too).
I work in all 3 major clouds, on-prem, the works. I still head to the DigitalOcean console for bits and pieces type work or proof of concept testing. Sometimes you just want to click a button and the server or bucket or whatever is ready and here's the access info and it has sane defaults and if I need backups or whatnot it's just a checkbox. Your time is worth money too.
> Sometimes you just want to click a button and the server or bucket or whatever is ready and here's the access info and it has sane defaults and if I need backups or whatnot it's just a checkbox. Your time is worth money too.
You're describing Hetzner Cloud, which has been like this for many years. At least 6.
Hetzner also offers Hetzner Cloud API, which allows us to not have to click any button and just have everything in IaC.
I personally find Hetzner's Console even better than DigitalOcean's one, especially since DigitalOcean now looks like three slightly different consoles depending on which page you're in. It feels like they've been migrating to a new system, but they haven't finished it yet.
One is about all the steps of zero downtime migration. It's widely applicable.
The other is the decision to replace a cloud instance with bare metal. It saves a lot in costs, but also the loss of fast failover and data backups is priced in.
If I were doing this, I would run a hot spare for an extra $200, and switched the primary every few days, to guarantee that both copies work well, and the switchover is easy. It would be a relatively low price for a massive reduction of the risk of a catastrophic failure.
Cute; I'd somehow missed ever seeing that one. The omitted con of electric engines (costs way more to build batteries than a gas tank so you're likely to have more expensive storage AND less of it) makes the XKCD joke miss. BUT... since there's probably something that Digital Ocean offers that Hetzner doesn't, that might actually be a very appropriate XKCD for the situation, precisely because there's a tradeoff the XKCD didn't mention. (I haven't used Hetzner so I don't know firsthand what the tradeoff is, but a quick search suggests Hetzner doesn't do Kubernetes so that might be the tradeoff for some people. Or it might be something else, everybody has their own situation).
Ah the golden rule, classic, but it is so simplistic that it could encourage bad behavior. You can never assume that something you want or don't want applies to anyone else.
I think a better formulation is the so-called "platinum rule", i.e. to treat people as they want to treated (with the important qualification that you ∈ people). But even then it's not without issue (what if someone's wants are harmful to them, e.g. a child refusing to eat anything but candy?), and it's still a far cry from illuminating "objective moral principles" and fairly useless as a calculus for balancing different people's competing interests.
They look kind of translucent to me, maybe the first of this kind of slug just had a digestive problem that didn't break down the chloroplasts, and the minimal energy through their bodies made those individuals more successful because they didn't need to eat as often as those who digested theirs. Yada yada other errors among the indegestible-chloroplast population showed further advantages when it's closer to the skin, they outcompeted their peers, etc.
Well we can easily see that the "abundance" people are wrong(for example everyone can't have a penthouse apartment overlooking Central Park, no matter how capable the robots become).
An alternative possibility that inequality is about to explode between those who profit from AI/robotic labor and those displaced by it.
Training ASICs (like Google’s TPUs) can generally run inference too, since inference is a subset of training computations. TPUs are widely used for both.
Mining ASICs (Bitcoin, etc.) cannot be repurposed…they’re hardwired for a single hash algorithm and lack matrix math needed for neural networks.
There will be a blinding flash which signals the superintelligence singularity. When the smoke clears, you'll see a 50-foot tall Altman/Borg hybrid. He is about to destroy humanity with his death ray. Suddenly, a 50-foot tall Musk/Borg hybrid appears out of nowhere, and stops Altman just in time. Then they work together to destroy all humans.
I haven't noticed any problems with large context requests through OR to e.g. Opus (other than the rate at which my budget gets spent!). Is this a performance thing?
I love this concept but the introduction is very odd. It feels like the first, third and 4th paragraphs make the same point (1/4 of cement is imported). It gets better as it gets technical.
I see the DigitalOcean vs Hetzner comparison as a tradeoff that we make in different domains all day long, similar to opening your DoorDash or UberEats instead of making your own dinner(and the cost ratio is similar too).
I work in all 3 major clouds, on-prem, the works. I still head to the DigitalOcean console for bits and pieces type work or proof of concept testing. Sometimes you just want to click a button and the server or bucket or whatever is ready and here's the access info and it has sane defaults and if I need backups or whatnot it's just a checkbox. Your time is worth money too.
reply