Yes, more than 5 years in a few components (mostly as smart reverse proxies as I said in another comment). They are high-loaded entry points on the client front, with a few hundred thousands clients. But I cannot say details due to NDA, even where it's used.
I did not compare performance with other alternatives such as OpenResty. I tried, but Nginx is very immune to resist loading it well from home network :)
Please move to Hetzner. If you miss payments even they might pull the plug, but at least they have humans who respond to emails and can get you back online quickly once you pay.
This isn't really helpful because it's true until it isn't true or you get locked out in a way that you can't prove ownership or something.
All businesses need to at least consider BC and DR, even if they eventually decide they have to risk it. There are loads of reasons why a dependency goes down which you have no control over so even basic spreading between providers or having a less-capable but simple DR system can go miles towards having a business not get killed in this way.
As much as I love Hetzner and can recommend their legal department, they are very risk averse especially with new customers and might not even let you open an account.
Any sort of weirdness from your server will also result in a very harsh email and a threat to suspend your services in way less than 10 days. I had the pleasure to experience their grumpy network admins when IPFS decided that node discovery included dialing 900+ RFC1918 IPs.
Oh great, it seems like this year he made the sarcasm about Larry Ellison a lot easier to pick up. Frankly I was still unsure how he really felt about Larry after his review from last year[1]. After reading this, it confirms to me that he doesn’t like Larry :).
Just to be pedantic, nix actually supports macOS and runs on top of Apple's kernel and userland (which I've tried, which is why I'm being pedantic), it's nixOS which runs at ring 1 that's being discussed here.
The biggest issue is that M1 is undocumented Apple Silicon. It has to be fully reverse engineered, primarily by the Asahi Linux team.
Other Linux distros will have to piggyback off the work of Asahi, and I think that generally they're avoiding jumping in yet because the hardware support is not very mature.
As much as I love the project, the work is far from done. Any macOS update can change the firmware of the GPU or the display controller, which would break the Asahi driver. And there are going to be a lot of macOS updates for at least the next five years.
I'm cautiously hopeful. Apple did break things a couple times already, but along with one of the breakages, they also introduced a new "we won't break this thing again" mode.
I've been sitting on the fence wrt Terraform and other such tools for quite some time now. After being _forced_ to finally write massive k8s YAML files (and ansible YAML files) for a consulting gig, I've been wondering whether these tools should be developed as _libraries_, that you glue together using a full-fledged programming language, instead of shoe-horning a programming language in YAML.
For example, could the following be library functions that you could glue together in the programming language of your choice: (a) get current state of infra, (b) calculate diff between desired state and current state, (c) perform a single step (safely) that represents a granular change in infra, (d) perform a series of steps representing infra changes with safe rollback?
You‘re pretty much describing the idea behind Pulumi which got a lot of traction lately.
Personally, I‘m still undecided on whether the unlimited freedom of a fully fledged programming language is a good or a bad idea in terms of footgun potential.
I‘m also still a bit unsure whether to play early adopter for an extremely hyped VC open core project even though it feels tempting.
Pulumi sounds interesting. Spent 10 mins with their marketing website and I'm not very clear whether it is a standalone set of libraries, or do they only work in conjunction with their cloud services. Do you know?
I've been using Pulumi for a new project after using Terraform for a long time. It's a little weird at first, but then it clicks and actually feels quite nice. The Input/Output logic with its async behavior is the weird part, but it works fine when you understand how it works.
The only (minor) problem that I've seen in it is that the JavaScript/TypeScript support seems more mature and featureful than the other backends. So, I'll simply use that.
I'm closely tracking an effort by Microsoft that aims to do a lot of what you're describing since I find myself bridging between these tools and deploying stacks that span tools and roles. [CNAB](https://cnab.io/) and the front-running implementation, [Porter](https://porter.sh/), enable one-step infra deployments, packaged as a single OCI-compatible container, with any number of steps, using the best tools for each of those steps. Think of using aws-cli for some initialization step (create or verify presence of a state bucket), applying some terraform to create infra, and finishing with a helm chart to complete deployment of app components. Each stage in a bundle packages not only the code to run it but also the execution binary of the tool that runs it. The spec and porter are still a moving target but it's a promising space and a nice adjacent evolution of the current state of tooling.
My team does something similar to this. We write our Terraform configuration as Python literals with list comprehensions, conditional expressions, etc., then use a script to dump it to JSON which the Terraform command line can parse.
I feel horrible whenever I end-up damaging an electronics product in such a way that repairs do not make any monetary sense. Mostly this is because the manufacturer doesn't bother in building out a healthy service network for their product because they'd rather force you to buy a new model.
If priced right, I'll buy this as my next laptop. And the next phone as well -- if they ever launch one.
AMD is colloquially referred to as "Team Red" in computer hardware circles. Intel is "Team Blue" and Nvidia is "Team Green."
The phrase "seeing red" is a fairly common idiom in my experience in American English. This refers to the matador's traditionally red sash used in bull fighting. Red is believed to draw inordinate amounts of bull attention and make them angry.
The use of "seeing red" is a bit strange, as the idiom is typically associated with anger and a pending bull charge, potentially metaphorical.
