The surprising thing to me was that you seemed to be saying there was a hard cap of 20% you couldn't ever exceed. I'm not surprised you aren't allowed to use all the shared resources all the time.
5,740 karma · joined June 10, 2017
The surprising thing to me was that you seemed to be saying there was a hard cap of 20% you couldn't ever exceed. I'm not surprised you aren't allowed to use all the shared resources all the time.
> Plans (CCX) with dedicated vCPUs have their CPU resources exclusively. Here one vCPU equals one thread of a physical CPU core. Instances with dedicated vCPUs offer continuous and predictable high CPU performance. We recommend them for systems with high production loads and CPU intensive applications. They run on high-performance hardware and come with a generous allocation of I/O and network power.
Of course that implies there is some throttling. But I see nothing about a hard 20% cap.
This is also how I'd solve it in Rust, except the defer would be implicit.
func doSomething() error {
f, err := os.Create("foo")
if err != nil { return err }
defer func(){ _ = f.Close() }()
if _, err := f.Write([]byte("bar"); err != nil { return err }
return f.Close()
}(There's two methods, one with a timeout. In an ideal world maybe that would be one but I totally understand how initially they maybe assumed format on save would always be reasonably quick and then had to backtrack)
So to give an example if I enter http://geder in my browser I want that to resolve to 100.100.5.10 regardless of if I am on my home network (where geder is) or if I am on a train.
From my perspective half the reason to use tailscale is that it replaces why I'd want mDNS with less bugs.
That's my point
I agree there's near infinite confounding factors. But I think the correlation is striking enough that it's relevant to this conversation especially considering that the post I'm replying to cites only non-Anglosphere countries.
I agree it's not enough evidence for anything conclusive. But I think it's enough evidence to say arguing about what will happen to the US based only on Sweden data is unsound.
This is especially true for second-generation immigrants. First generation immigrants are general less likely to commit crimes, but in countries like Germany and France the rate rises significantly with the second generation. That doesn't happen in the US or Canada, for example.
The children of immigrants in English speaking countries tend to do better financially than their parents whereas in many non-english speaking European countries the children of immigrants slide into poverty.
Edit: Here's a related article with some charts illustrating the correlation https://www.ft.com/content/c6bb7307-484c-4076-a0f3-fc2aeb0b6...
If you asked Elon Musk to tell you his life story he'd tell you about what he's done. If you ask a warehouse worker their life story they might tell you about things people told them to do. But that's a lagging and pretty boring indicator.
One handy feature this enabled is that you can include their open source go library in your program and avoid needing to install anything besides your own binary.
I also use zellij locally so I don't have to learn more than one set of keyboard shortcuts and so on. There are plently of alternatives but zellij is just convenient.
(This data dump exposes lots of customers that should have triggered KYC issues, like an American dog-walking startup remotely operated from Pakistan )
My phone did have that API, and I subjectively still found the experience janky. But that's just my opinion.
So the password is sent for a specific feature that legitimately wants it.
You could have the app connect to a special WiFi network and then communicate directly with an API exposed by the router. That's what my router does. But the experience of using a special-purpose WiFi network is janky on many common devices so I understand not taking that choice.