Pnpm 12.0(pnpm.io) |
Their benchmarks[0] report that a clean install with lockfile is about 3x times faster (7s -> 2.2s) and a no-op install is about 29x times faster (517ms -> 18ms)
And with the prevalence of AI, it rubs off on the smelly humans, who also find it useful and use it more as a result. (I used an en dash here instead of an em one – also valid, easier to type, and shorter).
The reason LLMs tend to use a lot of em dashes is that the human-authored texts they were trained on used a lot of em dashes.
Plenty? I don't think it's that many. And knowing how to use them, doesn't mean they would actually use them. In my experience, em dashes are mainly found in academic literature. Chances that an em dash in a new text comes from an LLM are pretty high.
Your use of it is dubious, I think. Commas would serve equally well --or better-- since it's a simple conjunction, not an interjection.
Opus 5 does not speak like a normal, average, or common English user. For example, it says “stated plainly” or “worth stating plainly” (two very uncommon English phrases) every two or three responses.
"1. All emdashes on this page were written by me."
I have switched to pnpm already.
It’s probably the worst package manager out of npm, pnpm, yarn, and bun.
I don’t see how it’s possible that the pnpm maintainers are unaware of the bun AI-rewrite-to-rust saga… so I’m baffled, befuddled, and overall at a loss to make sense of this decision.
https://github.com/pnpm/pn/commits/main/?after=e24c0b293f1f4...
I seem to be mostly unaware, at least, it's not self-explanatory to me why a Rust rewrite would be that baffling. What's the verdict on the Bun rewrite, and how does that relate to pnpm's decision? Also, wasn't Bun switching from Zig to Rust instead of from TypeScript to Rust like pnpm? I get the impression that many web infrastructure projects have been switching to more native languages.
I believe the objective verdict on the rewrite is “actually, everything went better than expected”, but it was and seemingly still is quite controversial and engendered a fair bit of bad blood, which I would have thought would be undesirable or demotivating to maintainers.
"This post covers what pnpm 12 adds that pnpm 11 never shipped."
they just don't recommend it.
nodejs stopped bundling corepack since node 25, maybe you're referring to that?
If you're going to serve us slop then at least serve us good slop, give it a pass through GPT 5.6 to clean up the English.
Why can modern LLMs basically not do that anymore? They each have their own very particular writing style?
It it all just beaten out of them in post training?
We really should stop jumping to conclusions and shaming people for using these tools just because you don't like the language of the LLM. How is a non native speaker meant to determine what is English slop and what isn't?
I should also note, I am a native speaker. There's absolutely nothing wrong with what's written in the part you chose to paraphrase, and it makes sense to me.
I've used `--` for years in place of an em-dash, which markdown renders as an actual em-dash.
You cant argue about this, just looking at github, i never saw dashes used pre AI. Today you see a dashes in code comments, PRs, issues etc EVERY time. Its all AI generated.
I normally use dashes when writing, never bothered myself with writing an em-dash properly otherwise.
The 3.5-4o era models were trained by RLHF primarily to write in a way that's pleasing to humans.
Starting with o1 the focus switched to reasoning, coding and benchmarks. If you remember when GPT-5 came out it introduced a new "colder" writing style (which was partly intentional) which made a certain subsection of Reddit Very Upset that Sam Altman had killed their AI boyfriends and they forced him to reinstate the warmer 4o.
The artificial default voice of modern models is optimized for reasoning efficiency rather than understandability. Unfortunately the artificialness has a tendency to leak out into the output tokens because reasoning tokens and output tokens are all still just tokens. You can prompt recent models to write in a more understandable style and they do a fairly good job of it, but it's not the default anymore, which means you will have to keep re-prompting it.
I don't think it's an unfixable problem, Anthropic in particular are just not very motivated to fix it because Claude is much less popular for chat than ChatGPT is.
So it simply cannot keep documentation or a codebase in the same style, and it cannot write <information> in <style>.
With 3.5 Turbo I used to give it bulleted information and paragraphs of what I wanted it to sound like and it'd replicate that style, then I'd edit the factual details it got wrong.
Now the situation has completely reversed! It can extract the data itself, but I have to write the stuff by hand. Humorously, it will do bulletpoints for me, and I write the thing.
In plain English, maybe it’d be more like “Package specifiers for git repositories should no longer include the HTTPS/SSH protocol. Instead, reference the repository name, and pnpm will resolve it through HTTPS. If SSH is still needed, add an override in your global git settings”
> For repositories on GitHub, GitLab, and Bitbucket, a specifier now names a repository rather than choosing a transport. github:owner/repo, owner/repo, git+https://…, and git+ssh://git@… all resolve through the host's canonical HTTPS URL, and the lockfile never records an SSH URL for those hosts. To reach a private hosted repository over SSH, configure the machine with git's own URL rewriting:
git config --global url."git@github.com:".insteadOf https://github.com/
There's nothing wrong with the English per se, it's grammatically correct, it just sounds so "Claude". Claude talks using pithy word soups that lack the niceties and structure of human writing.
FWIW though, you can ask an LLM to write in 'Simplified Technical English' (see: https://www.asd-ste100.org/), which at times reads like its written for a child, but it is much better for inclusion of non-native speakers.
The world existed before 2022.
As a non native English speaker I can also attest to this trade being extremely demanding of English fluency:
> public static void DoTheThing(Configuration config)
Isn't something you can not understand and still function as a software engineer. Yes, some schools and universities teach in other languages, but the entire ecosystem from code to documentation to articles is nearly almost always in English.
No they are not.
Claude isn’t the only option for such a person, as translation tools exist, and English-speaking colleagues exist to proof-read.
In any case, the article author writes perfectly well in English pre LLM era: https://www.kochan.io/nodejs/it-is-ok-to-keep-random-things-...