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
Pnpm 12.0
21–30 of 72 posts
Re: Pnpm 12.0
#22The 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.
Re: Pnpm 12.0
#23I 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,…
Unless you care about security, stability, DX, speed and correctness then npm is fine choice.
Re: Pnpm 12.0
#24Whenever you see a lot of long dashes (—) in a writing, there's a high chance Claude has written it.
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).
Re: Pnpm 12.0
#25The 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.
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.
Re: Pnpm 12.0
#26Whenever 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.
Re: Pnpm 12.0
#27I'm curious, as it's not mentioned, are there any performance improvements as part of this rewrite?
Re: Pnpm 12.0
#28Earlier quoted context omitted.
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.
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 a…
Ditto. I've started to wonder if the real problem with many of these complaints about LLM writing is actually reading comprehension.
Re: Pnpm 12.0
#29Earlier quoted context omitted.
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.
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 a…
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.
Re: Pnpm 12.0
#30Whenever 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 th…
This is untrue and a naive understanding of modern model training.
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.