What’s the problem with that? Seems to make sense to me with the example and it’s important to point out. I’d expect an llm to explain in more detail to be honest.
Maybe the author is a non-native English speaker, and this enables him to communicate things he's not able to do himself. Should OSS maintainers start hiring professional translators? Are you going to fund that?
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.
This is a recent degradation; they've been writing blog entries for years.
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.
It doesn't matter. I work with people who aren't native speakers (in a country where English-education is a very high standard) but are mostly fluent in day to day conversation and meetings and they are not comfortable writing long-form texts - and it shows. Your expectations are unrealistic.
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)
I got to the conclusion that boring is good enough, for me NPM is the best tool, is not that fast, but the installation speed is not that bad, considering how many times I need to run from scratch, the difference does not matter, it is stable and it's the default Node package manager, so I don't need to bother to install in CI any other tool, etc. My experience for long living projects is to stick with the defaults, because in a few years third party tools will change, it happen to my team with Yarn classic, now that we are with vanilla Node and NPM no worries, same with 3rd party dependencies, just use as less as possible.
Had to check the calendar to be sure it wasn’t somehow April 1st. No, it’s August. Huh.
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.
To be fair to the pnpm maintainers, they have been working on this well before the bun AI rewrite. The first commit in their rust experiment is in 2021.
This heuristic is commonly believed — and expressed on this website — but is idiotic. Plenty of people have known how to use em dashes when writing on a computer since the 1980s. (This was true even before UTF-8 was invented to make extended characters work across platforms; instead of ⌘⇧-hyphen, we'd just type "--" to approximate it.)
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.
In this case, the emdashes are just tip of the iceberg. The writing is so Claude that it’s painful to read (and in fact I stopped reading to save my mental health).
just why pnpm? you are stable, you are loved by the community. Now you feel the need to throw it away to rewrite for what? Can anybody give me a good explaination
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."
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.
The more I read these ass Claude Opus writings the more I believe AGI is further away from us.
I thought 'how bad can it be?', yet only three paragraphs in "a specifier now names a repository rather than choosing a transport"
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.
I remember the most interesting things to do with 3.5 Turbo was to ask it to rewrite paragraphs in different styles.
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?
What’s the problem with that? Seems to make sense to me with the example and it’s important to point out. I’d expect an llm to explain in more detail to be honest.
Maybe the author is a non-native English speaker, and this enables him to communicate things he's not able to do himself. Should OSS maintainers start hiring professional translators? Are you going to fund that?
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.
This is a recent degradation; they've been writing blog entries for years.
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.
It doesn't matter. I work with people who aren't native speakers (in a country where English-education is a very high standard) but are mostly fluent in day to day conversation and meetings and they are not comfortable writing long-form texts - and it shows. Your expectations are unrealistic.
Ditto. I've started to wonder if the real problem with many of these complaints about LLM writing is actually reading comprehension.
> It is a rewrite of pnpm in Rust
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)
[0]: https://pnpm.io/benchmarks
I got to the conclusion that boring is good enough, for me NPM is the best tool, is not that fast, but the installation speed is not that bad, considering how many times I need to run from scratch, the difference does not matter, it is stable and it's the default Node package manager, so I don't need to bother to install in CI any other tool, etc. My experience for long living projects is to stick with the defaults, because in a few years third party tools will change, it happen to my team with Yarn classic, now that we are with vanilla Node and NPM no worries, same with 3rd party dependencies, just use as less as possible.
Unless you care about security, stability, DX, speed and correctness then npm is fine choice.
I have the same experience - npm was bad, now it is fast enough.
I'm curious, as it's not mentioned, are there any performance improvements as part of this rewrite?
Had to check the calendar to be sure it wasn’t somehow April 1st. No, it’s August. Huh.
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.
To be fair to the pnpm maintainers, they have been working on this well before the bun AI rewrite. The first commit in their rust experiment is in 2021.
https://github.com/pnpm/pn/commits/main/?after=e24c0b293f1f4...
https://bun.com/blog/bun-v1.4 has some pretty nice numbers indeed.
Whenever you see a lot of long dashes (—) in a writing, there's a high chance Claude has written it.
This heuristic is commonly believed — and expressed on this website — but is idiotic. Plenty of people have known how to use em dashes when writing on a computer since the 1980s. (This was true even before UTF-8 was invented to make extended characters work across platforms; instead of ⌘⇧-hyphen, we'd just type "--" to approximate it.)
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.
[delayed]
In this case, the emdashes are just tip of the iceberg. The writing is so Claude that it’s painful to read (and in fact I stopped reading to save my mental health).
just why pnpm? you are stable, you are loved by the community. Now you feel the need to throw it away to rewrite for what? Can anybody give me a good explaination
Hooray!
Good to see the maintainers don't care enough to take the time to write a release blogpost themselves. sigh
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."
Time to hop off I guess. They don't even bother to write changlog on their own.
Same here, what if the internals get the same absence of care? No thank you.
Am I the only one that hates the decision to no longer support corepack?
pnpm 12 supports corepack (or better phrased - corepack supports pnpm 12).
they just don't recommend it.
nodejs stopped bundling corepack since node 25, maybe you're referring to that?
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.
Same here. Corepack was fine and there is already too much churn
First I'm hearing of it, and it does dampen my enthusiasm for v12 a bit.