if ibm is where companies go to die, microsoft is where companies go to intentionally punish, hurt, torment and traumatize their users
-
@paul_ipv6 well mysql went to oracle and it just punished every mysql user
-
i cant help but think that this reality we've painted ourselves into is because we gave a bunch of charismatic techbro types the ability to make decisions, big ones, that affected the top-down architecture of big orgs and how they work, and it turns out they had no fucking idea how computers worked, they just learned enough buzzwords to be human mockingbirds, and made chainaw sounds with their mouths and we went butthead_huhuhuh_cool.wav
-
this is, incidentally, the same angle i have against k8s and docker.
if you build a thing that is supposed to have the ability to do firewalling, natting, do acls, rules, follow policies and whatnot - and its intended use is "on a linux box", and you decide "to reinvent the entire fucking universe as npm, js, and custom shit instead of using the already inbuilt stuff in linux" you have made a serious architectural error and it will haunt you forever.
assuming your thing lives that long
this extends beyond just github yaml.
home assistant lives here too -
@paul_ipv6 well mysql went to oracle and it just punished every mysql user
i think oracle just wanted to have all mysql users kill themselves so it could claim it wasn't the killer for a change but yeah...
any company email stating "we have been acquired by oracle" is a sign for customers to bolt and employees to start the job hunt.
-
@Viss Its why tech executives think LLMs are AGI and conscious ... Because they think at the same level. Word salad slop.
@varx hey its vince with slaptchop, and yer gonna be in a great mood all day!
-
@Viss most kubernetes has this pain everywhere too. One setup I worked on I counted 5 layers of template processing between the config in git and the config the application would read.
-
this is, incidentally, the same angle i have against k8s and docker.
if you build a thing that is supposed to have the ability to do firewalling, natting, do acls, rules, follow policies and whatnot - and its intended use is "on a linux box", and you decide "to reinvent the entire fucking universe as npm, js, and custom shit instead of using the already inbuilt stuff in linux" you have made a serious architectural error and it will haunt you forever.
assuming your thing lives that long
-
@Viss most kubernetes has this pain everywhere too. One setup I worked on I counted 5 layers of template processing between the config in git and the config the application would read.
@richardstephens and 100% of the layers that exist inside of k8s do not need to exist at all, and function only as performative puffery nonsense so k8s people can gloat to other k8s people about how good they are with k8s.
and 80% of the compute goes to those layers and abstraction, and not 'whatever the actual container is doing'
-
if ibm is where companies go to die, microsoft is where companies go to intentionally punish, hurt, torment and traumatize their users
@Viss Do you have a link to the original post? -
@Viss Do you have a link to the original post?
-
if ibm is where companies go to die, microsoft is where companies go to intentionally punish, hurt, torment and traumatize their users
-
so when my customers are doing incident response for the stuff I find, and that stuff is 'i have abused the shit out of some of your github actions, you should see what the log artifacts look like so we can write detections for it all' flavored - this is what we collectively grapple with.
microsoft, i remind you, is the company that CHARGES EXTRA FOR LOGS if you want to see if someone is trying password stuffing on your o365 instance
they make it intentionally painful, so they can sell a fix
@Viss they don't want a fix, as they rely on the cottage industry of #Scareware-Blob vendors to continue peddling their garbage #Govware-OS!
-
this is, incidentally, the same angle i have against k8s and docker.
if you build a thing that is supposed to have the ability to do firewalling, natting, do acls, rules, follow policies and whatnot - and its intended use is "on a linux box", and you decide "to reinvent the entire fucking universe as npm, js, and custom shit instead of using the already inbuilt stuff in linux" you have made a serious architectural error and it will haunt you forever.
assuming your thing lives that long
-
- We should use #YADL instead.https://github.com/greyhat-academy/yadl
-
R AodeRelay shared this topic
