My experience is that by stealing providers from Terraform, they failed to properly handle statically typed languages (Go) with certain providers (HCloud); I had problems with their ID type and had to abandon my Pulumi setup.
I don't like this solution because it is hostile to those who use solutions such as UMatrix / NoScript in their browser, who use TUI browsers (e.g. chawan, lynx, w3m, ...) or who have disabled Javascript outright.
Admittedly, this is no different than the kinds of ways Anubis is hostile to those same users, truly a tragedy of the commons.
Whether intentional or not, there is an obvious benefit to the website operator in forcing users to expose themselves to images and Javascript by requiring the use of particular software. e.g., a popular graphical browser from a company providing advertising services (Google, Apple, etc.) or partnering with one (Mozilla):
It makes (a) visual advertising and (b) tracking viable
I read the www text-only, no auto-loading of resources (images, etc.), and I see no ads
I find the audio-visual experience (tilted elements, slightly blurry or shaky, semi-kinetic and burpy cronchy weird noises) of this website jarring as the act of over-consumption itself. Nicely done.
financial and corporate transparency and privacy are a very different matter to the transparency and privacy of an individual.
despite the whackadoodle precedent that corporations are people, corporations are not people. they may be made of people, but the affairs of those people are within the course of their employment, acting on behalf of the corporation.
it also depends upon the mask type who you're protecting? IIR surgical masks tend to only protect other people, whereas you can protect yourself with FFP2/FFP3/N95/P99/...
but deciphering that is part of the problem, the layman had to come to terms with the difference between IIR masks and the other more protective to self standards.
the messaging was unclear but it required the avg person to do their own research.
imo, the real problem was the culture war?
i don't think there's any problem with someone making it clear that they're sick; society needs to be more accepting of the sick and more accepting of call-outs of work due to illness. this would help everybody in the long run.
That procedure (I guess you speak about fit tests, especially with a dust of saccharin) is important when you need to be 100% sure to be protected, such a dealing with with ebola or equivalent; but even a badly fitted mask will reduce the inhaled dose and improve the chances to develop a benign infection.
kubernetes is very complex and therefore any abstraction which completely glosses over the way the underlying systems work would make it very hard to avoid leaking or a bad abstraction to begin with.
the complexity in one way or another must be preserved within the abstraction (in all likelihood) or you will have cases you cannot create in that layer or breakages which now have the total complexity of both the abstraction itself AND kubernetes itself required to fix.
i would not say IaC is going to provide you a magic solution to learning k8s, although the value in using IaC (e.g. Argo CD / Flux CD + Kustomize + ...) in K8s land is that you are no longer imperatively managing your cluster resources and therefore can keep them within a repository, managed like code. the point of the solution is not to make it easier for newcomers, but to make it easier to have teams manage and work together on an established cluster for deployments, ...
in the case of Pulumi, you leverage the single language with typechecking instead of relying upon K8s flavoured YAML, which is itself beneficial in many ways (since you can use your regular developer tooling)
wrt pkl, pretending K8s manifest structure underneath does not help because you will need to know how the keys within a manifest interact with the underlying system regardless, especially to understand functionality, e.g. node selectors, taints and tolerations, node affinity, ...
i prior managed a terraform-based deployment of several k8s clusters and it still required knowledge of those keys and values, alongside knowledge of the underlying resource types.
without those you can't implement things like GPU-based node selection for jobs which require a GPU, ...
DO's K8S is more equivalent to AWS's EKS offering, so of course ECS which abstracts away pretty much all of the other parts of K8s is going to require less maintenance. It's sort of a false equivalence to say ECS == that solution.
On EKS, you need to do the same version updates with the same amount of terror.
You do pay the extra for the further management to just run containers somewhere!
(you might want to say "every" instead of over, "is" instead of "ist")
I definitely want to say is instead of ist but it is bugging me every couple of months. You do the upgrade and 6 months later it needs another one. No LTS in sight
It didn't work for me either, but apparently one of the issues is that it assumes window.speechSynthesis is available which may be disabled via about:config > media.webspeech.synth.enabled.
reply