Is "pnpm installs the other package managers" what you're talking about, or something else? That doesn't quite read like removing corepack support to me, though I might be missing something obvious.
I was also bothered by this. I don't care if you use LLMs to write most or all of your code, but at least have the courtesy of actually writing your blog posts & readmes, to demonstrate that you at least understand what the LLM generated for you.
Hey Claude, write in the worst possible claudism way you possibly can, and make it sound like every other text on the internet that is published nowadays.
"This post covers what pnpm 12 adds that pnpm 11 never shipped."
The best way to ask for this is to send an email, to the email address which you can find at the bottom of the page (click on "Contact"). There's no guarantee that the mods will find your comment otherwise.
Saying @dang has no effect; it does not activate a batsignal or any other mechanism of mod summoning. The only way to be sure a mod see this is to email them; see the contact link in the footer and include a link to the comment.
Going from starting the project two weeks ago to already having a flashy marketing site is another tell, unfortunately. As much as I would love to see a trustworthy version of this idea.
Actually the flashy website was built 4 years ago by another person.
We actually tried to build it 4 years ago, but other ventures with higher upside kept our focus.
Now you get a VPN for free, no strings attached, although it is vibecoded you still complain :cry:
Partly. Partly because using EUF-CMA pins the record to the CA which makes membership deniability non-trivial which I don't love. It's not dumb, it's what Signal uses AFAIK and in transit message deniability is different than the signer. But still..
> `absorb` assigns the changes based on whichever previous commit most recently touched those files, which sometimes doesn't actually correspond to which commit should own these particular changes.
I’m pretty sure `jj absorb` (and its predecessors, `git-absorb` [0] and `hg absorb`) are smarter than this, instead looking at the actual diffs.
Ah yeah, you're right, that's a misrepresentation on my part - it's based on lines, not the file:
> [absorb] splits changes in the source revision and moves each change to the closest mutable ancestor where the corresponding lines were modified last. If the destination revision cannot be determined unambiguously, the change will be left in the source revision.
I use absorb fairly often, fwiw. It's great for when I want to make a patch to a commit that will easily absorb into its right place. And I also, sometimes, prefer the more intentional approach where I decide exactly where each hunk will go.
Yeah it’s smarter than that, but as a daily user of git absorb it still gets things wrong fairly often though—like a couple times a week often for me. Plus the changes it can’t absorb automatically (e.g. a lone doc change it can’t find peers for).
It’s possible this is just a Nest limitation? It appears that all the data is there to construct a diff with context, and I’d hope the CLI would do so…
Comments here seem to be talking like they've used this model for longer than a few hours -- is this true, or are y'all just sharing your initial thoughts?
My local tennis court's reservation website was broken and I couldn't cancel a reservation, and I asked GLM-5.1 if it can figure out the API. Five minutes later, I check and it had found a /cancel.php URL that accepted an ID but the ID wasn't exposed anywhere, so it found and was exploiting a blind SQL injection vulnerability to find my reservation ID.
Yeah it seems they did not align it to much, at least for now. Yesterday it helped me bypass the bot detection on a local marketplace. that i wanted to scrap some listing for my personal alerting system. Al the others failed but glm5.1 found a set of parameters and tweaks how to make my browser in container not be detected.
I always jump on the Chinese models when I'm trying to do something that the US ones chastise me for, they're a little more liberal, especially around copyright.
> Five minutes later, I check and it had found a /cancel.php URL that accepted an ID but the ID wasn't exposed anywhere, so it found and was exploiting a blind SQL injection vulnerability to find my reservation ID.
I'm happy I invested in setting up Codex CLI and getting it to work with ollama. For the toughest jobs I can use Github Copilot (free as an academic) or Gemini CLI. If we see the per token price increase 5x or 10x as these companies move to focusing on revenue, local models will be the way to go, so long as stuff like Gemma 4 keeps getting released.