Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Pnpm 12.0

pnpm.io

Post reply on HN
Print view View original

41–50 of 72 posts

Re: Pnpm 12.0

#41

Post by flohofwoe »

deanc wrote: post #25
zarzavat wrote: post #22

Earlier 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…

A non-native speaker most likely writes more 'understandable' English than the weird convoluted Claude style.

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.

Re: Pnpm 12.0

#42

Post by cpursley »

knlam wrote: post #21

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

Check the benchmarks, hopefully even more JS slop is converted to Rust for the sake of humanity.

Re: Pnpm 12.0

#43

Post by sevg »

deanc wrote: post #32
fredrikholm wrote: post #29

Earlier quoted context omitted.

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…

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.

> Your expectations are unrealistic.

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-...

Re: Pnpm 12.0

#45

Post by zarzavat »

IanCal wrote: post #33
zarzavat wrote: post #22

Earlier 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.

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.

If you spend all day talking to Claude then its mannerisms begin to grate on you like fingernails on a chalkboard.

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.

Re: Pnpm 12.0

#46

Post by tgv »

veidr wrote: post #26
1matin wrote: post #15

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 th…

> Plenty of people have known how to use 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.

Re: Pnpm 12.0

#47

Post by raincole »

fwlr wrote: post #16

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.

Bun rewrite seems like a big success story.

Re: Pnpm 12.0

#48

Post by codeflo »

fwlr wrote: post #16

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.

> unaware of the bun AI-rewrite-to-rust saga

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.

Re: Pnpm 12.0

#49

Post by dkdbejwi383 »

tgv wrote: post #46
veidr wrote: post #26

Earlier quoted context omitted.

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…

> Plenty of people have known how to use 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, no…

Markdown is ubiquitous in the kinds of places Hacker News visitors also tend to visit, like GitHub, various ticketing and project management systems like Jira, note takers like Obsidian and Notion (or an approximation of Markdown).

I've used `--` for years in place of an em-dash, which markdown renders as an actual em-dash.

Re: Pnpm 12.0

#50

Post by _leom »

veidr wrote: post #26
1matin wrote: post #15

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 th…

The text also includes en-dashes, I struggle to believe that someone actually manually typed those.
Post reply on HN