HN user

tom_

3,521 karma

Long-time pseudonymous HN commenter, now posting under my real name.

Posts0
Comments1,675
View on HN
No posts found.

You misunderstand. They are going to force everybody to pay $5, then force everybody to use chatgpt. 8 billion times 5 isn't much money, but the advertisers will surely pay a lot for that many captive eyeballs!

(I have no MBA either)

I never liked xargs either. My replacement is kind of like "xargs -n 1 -d '\n' -J '{}'", which experience has taught me is almost always what I want. It consumes all of its input before starting, so it knows how many files it has to process, and it can print progress to stderr and/or the terminal title as it goes. It can run each command via the shell if you want. It has --dry-run and --keep-going. It can read the file names from a file rather than stdin. I have a few more ideas for things it could do, but I haven't needed to add them yet.

(For enumerating files, I use find or dir/b/s, possibly combined with grep, then pipe the result in.)

People moaning about avoiding non-basic use of xargs and bash (and inadvertently demonstrating in many cases why some of us think that xargs sucks) miss a large part of the point, which is that it's nice to have a tool that does exactly what you want, and works in a way that's convenient for you, and isn't so widely used that you have to worry about modifying it. If you find the tool doesn't work the way you like, you can just change it. You don't have to be answerable to anybody else. I think tptacek's quite good essay could be relevant: https://sockpuppet.org/blog/2026/05/12/emacsification/

(You don't have to use LLMs for this! I wrote my program by hand, it's only like 250 lines of Python, and you could write one too. But, whichever barriers to entry prevent you from creating your own tools for yourself, using an LLM would probably lower at least some of them.)

It's just less effort all round to have everybody using the same supported set of tools. I don't know if I've ever worked on a project that's gone so far as to actually mandate this, but a "should" (possibly in the RFC sense) is fair enough I think. Every project I've worked on has ended up with everybody eventually settling on using the same tools, because it's just overall less hassle that way.

(Regarding Emacs, I'm typically using it anyway for org-mode, so if I need to do some one-off edit or other - probably some keyboard macro thing - then I can just load the problem file into Emacs and save it back out again afterwards. I've only once been in the situation of neither being allowed to install it nor remotely connect to another machine to use it.)

The iPhone is normal phone size width and depth, but it's meaningfully shorter than just about everything else. It doesn't sound like much on paper but I've always found it adds up once in a pocket. (All dimensions height x width x depth, in mm, rounded up to the nearest mm)

* iPhone Mini: 132 x 72 x 8 (https://support.apple.com/en-gb/111877)

These two alternatives are noticeably larger:

* Vivo X300: 151 × 72 × 8 (https://www.vivo.com/in/products/param/x300)

* Oppo X9S: 157 x 74 x 8 (https://www.oppo.com/en/smartphones/series-find-x/find-x9s/s...)

In fact, they're more like the size of the full size iPhone, which, if you're sticking with your iPhone Mini because the iPhone is annoyingly large, means they're too large.

* iPhone 17: 150 x 72 x 8 (https://www.apple.com/uk/iphone-17/specs/)

My current theory to explain this phenomenon: a lot of the posts I read on HN, possibly even the majority of them, are made by different people, and those different people sometimes have different opinions.

Resetting Xbox 16 days ago

XBOX here presumably refers to the entire division, so it's not limited to just people playing on the games console.

Slightly struck by the term "builders" here. What is this trying to say, that, say, "developers" wouldn't?

("build" does seem to have been settled on as the word for the thing you do when you have the LLM write your code for you, but I'd have thought that "developer" is vague enough to cover both that and also doing it the old-fashioned way?)

I'm inclined to believe them too, so when he said he used LLMs to tweak the wording, I'll accept that was the case.

Perhaps the opening post was ill-phrased, but I think the second post clarifies it a bit: https://news.ycombinator.com/item?id=48677597 - and I was certainly getting some vague LLM vibes from the writing, so I was curious about this too.

So, whatever it is in the LLM output that is detectable, it's clearly detectable, even with the latest LLMs, and even when it's present possibly only in trace quantities.