That's not a move of a company that thinks it can still grow. That's a Netflix "we have 90% of the market, let's squeeze them" move.
This is the beginning. We have all seen this pattern over the last 5+ years. You know their next few moves.
100% agreed. I don’t understand the point of throwing all conventions out the window and building their own brittle scripts on top of it. All their images require docs to configure because none of the upstream documentation applies.
> For the longest time, surgeons, dentists and optometrists weren't part of the medical profession. You'd have a barber who could give you a shave or pull your teeth, or a butcher who could cut up a hog, or cut off your gangrenous leg. Optometrists were craftsmen who made the spectacles in their shop. Doctors were University educated in Latin and Greek to read ancient medical texts and despised the uncouth yokels.
> Surgeons muscled their way into the medical profession, originally with the help of the Royal Navy, who only had space for one or two people in charge of both cutting off legs and looking after crew health on their ships.
> Dentists and optometrists never did, so they started their own universities, certification boards, etc. By the time they became respectable enough for people to try to merge them with the medical establishment, in the 1920s, they had no desire to give up their independence.
> The first insurance policies were private contracts with groups of doctors and the system developed from there.
Details vary from country to country of course, but the gist of it generally holds true.
Agree with all the positive takes in here. Just wanted to add that the graphic design is chef's kiss. Especially the image transformation of the album art!
Some of them are hard to parse and it almost becomes a game, and then there are others where it's clear as day that e.g. the band is posing for a picture. Also just recognizing covers that you know is fun.
7 lines into the README buddy:
> The command essentially looks at the lines that were modified, finds a changeset modifying those lines, and amends that changeset to include your uncommitted changes.
devils advocate: Is this maybe a case of discarding an 80% solution because you can’t do the last 20%?
I understand the constraints, but imagine how legible you could make code by replacing some key parts with a graph type that everybody knows.
I honestly think that having a type that supports a small subset of possibilities and only has the simplest algorithms implemented would go a long way.
I never understood the appeal of service meshes. Half of their reason to exist is covered by vanilla kubernetes, the rest is inter-node VPN (e.g. wireguard) and tracing (cilium hubble). Unless I’m missing something encrypting intra-node traffic is pretty silly.
K8S has service routing rules, network policies, access policies, and can be extended up the wazoo with whatever CNI you choose.
It’s similar to Helm, in that Helm puts a DSL (values.yaml) on top of a DSL (go templates) on top of a DSL (k8s yaml), just that it is routing, authentication, and encryption on top.. well, routing (service route keys), authentication (netpols), and encryption.
In that case whoever is linking the script is “breaking” it, I’d say. There’s stuff that is simply outside the responsibilities of the script/maintainer.
If you start worrying about that for “simple” scripts, the logic for handling that is quickly going to outgrow the initial logic itself.
> The files the threat actor obtained in the Okta compromise comprised HTTP archive, or HAR, files, which Okta support personnel use to replicate customer browser activity during troubleshooting sessions. Among the sensitive information they store are authentication cookies and session tokens, which malicious actors can use to impersonate valid users.
I know that troubleshooting for pwms is hard, but leaving unencrypted files to access accounts on a server that’s not governed by the same threat-model seems very negligent to me.
When talking about security updates it most certainly is. You can’t blame LE for that. That responsibilty lies squarely on manufacturers who are not even maintaining the bare minimum of security patching like an up-to-date root cert list.