That and people have completely switched to MDMs to provide a lot of the old functionality that macOS Server used to provide.
The popular ones for macOS are Jamf and Mosyle. There are some other ones as well that are more cross-platform oriented, but both Jamf and Mosyle more or less cover the features that macOS Server provided for administration of a set of devices.
Tbh, I don't think Server was popular as a NAS service ever. The only thing I've ever used Server for was managing devices.
Right now, this is pretty specific to our use of it, specifically our use with Terraform EC2 instances. We'd happily suggest changes to make it more generic. But you can see the parsing logic there.
Sure, I could imagine that is the case in fields like nuclear engineering. All the PEs I know are smart and have technical chops. Though, most of my PE friends are fairly young (early 30s) and are maybe on their way to that destination.
It's the only thing that most SaaS things charge for now-a-days. Slack, Dropbox, Github Enterprise, etc. They know that regulated businesses have requirements to have SSO and things like this, so they can charge out the nose for it. You can go for a very long time with paying little to nothing for most of these services until you need SSO.
You need to account for the delay to death in your model here. People don't die the second they're infected. Most of the people in that estimated infected number were infected in the last week. They couldn't possibly have died of the disease. I believe most epidemiological models have a infection to death delay factor to estimate death rate. Your mortality rate with ~300/100k~=flu is too low.
We’re building a Bitcoin derivatives exchange all written in Haskell. We use ansible and terraform for our operations automation. Trading industry experience is a plus.
We’re building a Bitcoin derivatives exchange all written in Haskell. We use ansible and terraform for our operations automation. Trading industry experience is a plus.
We’re building a Bitcoin derivatives exchange all written in Haskell. We use ansible and terraform for our operations automation. Trading industry experience is a plus.
I too have vim muscle memory in the terminal, so what I do is alias vim to emacsclient. It's actually really great! Terminal emacsclient with evil is basically indistinguishable from terminal vim.
The TCP and IP protocol specifications do not mention routing either. There are many routing algorithms possible, and many of them are used simultaneously. The same will be true for the lightning network. Lighting has a long way to go, but writing it off as a cute but useless experiment because of current limitations is short sighted.
Absolutely. Though, when people say cookies vs JWT, what they mean is:
Cookies: a simple session ID, a random number, stored in a cookie.
JWT: a JSON object stored in local storage that specifies authorization of some user that is authenticated by public key cryptography. JWTs can be configured in many ways, but this is what people usually mean because they want their sessions to be "stateless."
Way way more often than not, the "cookie" solution is better because it's far simpler. JWTs come with a tremendous amount of complexity with few benefits.