Likes from 16 June 2024

When Regal was just a linter, its code was roughly 60% #Rego and 40% #Golang. Making it also be a language server has shifted that balance to 40/60. And while it was the right call at the time — we didn’t know the protocol, and no one else had done anything for that in Rego —I wasn’t too happy about it. So I’m now looking at rewriting parts of the LSP implementation in Rego too. So far so good! Expect to hear more on this next week 🤓

who the fuck is scraeming "good girls dont cum" at my house. show yourself, coward. i will never stop cumming

lmaoooo on the one hand i get it and i can see how denial would be pretty hot but on the other it's just so funny for "doesn't make her cum" to be turned into a purposeful kink in a heterosexual relationship. no you don't get it, it's actually on purpose

Trivy 0.52.1 on age v1.1.1 > Total: 31 (UNKNOWN: 2, LOW: 0, MEDIUM: 13, HIGH: 14, CRITICAL: 2) govulncheck v1.1.2 > No vulnerabilities found. govulncheck is correct. All the vulns reported by the other thing are provably false positives. When I did the initial design of govulncheck, I made minimizing noise a priority, to give devs a chance to actually triage potential vulns. I suspect I was wrong: if the tool is too good, it will find nothing most of the time, and devs will not trust it.

How to sabotage software productivity, in the style of CIA

In this post I'll describe the tools and services I use to run my SaaS business. From programming languages to open source libraries to Kubernetes tools for easy deployments.