No one:
Claude Opus 4.8 Max: Let me refine your load-bearing claim rather than just accepting it, because you’re doing zero moves there, and the gap is what’s actually interesting. The one place I’d still push, because I think it matters: your message is wearing content-clothes, but the content isn’t actually *there*. The tell: it’s just an empty string. But the emptiness of the string IS its lack of content. Pull one, and the other goes inert. That’s the structural spine.
@gtrakGT@korulang with some perfsplaining about how Linked List's Aren't Really That Great After All (helpful, as if I haven't been working on latency optimizations since before most Rust fans were an itch in their daddy's pants) - gave me a "this language can't *possibly* be it" vibe:
@geofflangdale I mean, basically, these days Javascript _is_ compiled, Typescript moreso, and it's GC'd and it's the application lingua franca. Most of the insane JS/TS tools/frameworks these days go through a lengthy build step.
It's hard to stop looking at images like this from AP.
Dana White, the UFC chief preparing the fights on the White House lawn, told NPR he has his reservations about the outdoor space. 1/2
@geofflangdale Rust will win the application-side over, I think. I do not prefer it to C++, but it's simpler so doesn't require a decade to learn, and its tooling is vastly superior. It's not really a systems language, though. Likely it will eat Java's lunch, too, as it's portable.
@geofflangdale Core theses I have to remind myself of constantly: everyone is high now, no one knows how to read, everyone is addicted to online conspiracy theories.
@geofflangdale 8-9 years ago I was in the office building elevator, full of people, and a business-y guy was cursing obnoxiously, being aggro. I asked him to stop, and he went full "let's step outside." Lawyers to the left and right, I would have come away owning everything he had. Insane.
I've pretty much wasted the past decade of my life building cursed open source dependencies in a CI pipeline when in 2002 I'd've just committed the DLLs to CVS and been done.
Fork your dependencies, trim them to only your use case, never update unless it breaks for your users. I’ve been vocal about this for 10+ years. I’ve always said that updating is way riskier than latent bugs (which can be tracked and CVEs monitored).
If you are updating a dependency, it’s on you to analyze every single commit in the full transitive set of dependencies. If you dont see anything compelling, dont update!
I remember at HashiCorp once in awhile an engineer would try to update a dep or replace a DIY lib with an external one and id always ask “show me the commit we need.” Dont update for the sake of it.
Feeling pretty swell about this mentality with all the supply chain attacks happening.
We are investigating unauthorized access to GitHub’s internal repositories. While we currently have no evidence of impact to customer information stored outside of GitHub’s internal repositories (such as our customers’ enterprises, organizations, and repositories), we are closely monitoring our infrastructure for follow-on activity.
@geofflangdale this is the art exhibit itself, right? challenging the very conception of Australian identity, right? the next gallery is just video compilation of Crocodile Hunter?
@primal0xF7 it kills me watching people try to string prompts together in a defined sequence when state machines are foundational to computer science and cost nanoseconds to compute