@romin
Because everything only gets further broken when they are attempting to fix it — true for software in general, GH just puts all that on display…
But that is probably completely unrelated to the context of your original post… TBH I don't have the slightest idea of what that might be 😅

@m0xee a piece of code I wrote (2 weeks ago) is 'solving' some unknown problem

@romin @m0xee the unknown problem of your poorness?

@hispanicweeb @m0xee that's unsolvable

@romin @m0xee i thought romin coin was going well

@hispanicweeb @m0xee if only you bought more..

@romin @hispanicweeb
We could all become a little happier (and richer) if we just complied and stopped refusing to update the Go toolchain…
But I refuse to refuse! This isn't the path of true Jedi master 😤

@m0xee @hispanicweeb retvrn to 1.11

@romin @hispanicweeb
Trve! But it was also a metaphor for conformance in general. See, I'm getting all philosophorical here…

@m0xee @hispanicweeb just never update, mitigations=off

@romin
What are these "mitigations" people keep talking about? 😏
Apple never cared enough to issue even the microcode updates for the old Mac Pros: "It's EoL, so it's your problem now, tehe 😜"
Of course I can always enjoy retropollinarius, courtesy of Linus Törvalds or even Microsoft® Mitigations™… with Total Recall™… powered by Autopilot™! But none of it makes much sense.
@hispanicweeb

@romin @hispanicweeb
> I refuse to refuse
Sorry, that didn't sound right, what I meant is that I'm going to keep refusing of course. I lack the brain capacity for cooking and typing weird shit at the same time 😋

@romin
I guessed that much, hence the remark: I didn't want to indiscriminately offend your piece of code solving… who knows what problem 😆