codethief

Incidentally, Claude Code has been very buggy for me lately (much more so than before). Lots of TUI rendering issues causing, e.g., the conversation history to be garbled etc.

Same in Firefox for Android!

Great article. I would love to see a similar article about how POS credit card / debit card payments work in the US/Europe, depending on whether you use the card's magnet stripe, chip or your phone (Apple Pau/Google Pay/…) to pay.

As was mentioned countless times here on HN, the fork didn't get merged not because of any no-AI policy but because the Zig maintainers considered it to be of poor quality and were already working on more comprehensive improvements to the compiler which would bring the same (and more) benefits, but without the downsides and quality issues of the fork.

It's not even a fix for the harness, as the calling user account's permissions are usually still enough to exfiltrate or manipulate data. See also https://simonwillison.net/2025/Jun/16/the-lethal-trifecta/

As the sibling already said, this doesn't work/help in most cases. See https://simonwillison.net/2025/Jun/16/the-lethal-trifecta/ for a different explanation of the issue.

Interesting, I didn't realize Maps.me used to be open-source! I suppose this is the code (from five years ago): https://github.com/mapsme/omim

And here's the non-PDF link: https://www.biorxiv.org/content/10.1101/2024.11.14.623689v1

The sun in northern countries in summer is less intense?

To everyone saying that this has always been a problem: The issue is the scale of the problem. Deleting the occasional spam email by hand is not a big deal but once you're getting flooded with spam emails, you better have a good spam filter in place.

In the same vein, the early hiring funnel discussed in TFA did work in many if not most cases or otherwise people wouldn't have used it. This no longer seems to be the case.

That makes sense! I wasn't aware of min_version for some reason, thanks so much!

Bonus points for it running fine on Linux, too.

I haven't really been able to use outlook.office.com in anything but Edge, which on my Windows machine automatically authenticates with M365. In other browsers I regularly get stuck in an auth redirect loop between different Microsoft domains when I open the site. Sometimes it helps to clear all cookies and re-login (which is a real pain with 2FA and all) but it only ever helps once: If I close and re-open the site, I'll have to do it again.

How people voluntarily pay for this crap is beyond me. (In my case it's forced upon me by my client. On my own machines I switched to Linux in 2010 and never looked back.)

For anyone not familiar with the reference: https://m.youtube.com/watch?v=BzAdXyPYKQo

I wanna hang out with coders who care, I wanna read articles about caring and how you can achieve more with less code

This very much reminds me of an expression coined by Loris Cro (VP of Community at Zig Foundation): "Create software you can love".

Looks like it's even got a website these days: https://softwareyoucan.love/

Ha, I came here to share this! :)

Thanks so much for your work on mise! I used to be a heavy asdf user but nowadays I'm an even heavier mise user!

Random question while you're here: mise is undergoing pretty heavy development these days and I recently noticed that 1) my coworkers and I are not always on the same version, so some features/bug fixes are not available to everyone, and 2) package registries often don't have the latest mise version.

So I think we need a meta tool manager here to manage the tool manager version. :) Seriously, though, have you considered having mise manage its own version? I think that'd be pretty neat!

Thinking aloud, I guess one way to do this might be to distribute through package registries only a lightweight bootstrap application, which 1) reads the pinned mise version from mise.toml and downloads it as necessary, and 2) sets up a basic shell hook that the active mise version can then hook into(?) I know, this probably sounds a lot easier than it actually is.

Does anyone know who the authors of the study are and what the data basis was (how many people were interviewed, age brackets, etc.)?

Good point. Maybe there'll be companies that maintain your on-premise GPU cluster just like there are companies that service the coffee machine in your office?

AI is different.

I agree. The other thing here is that, once you can run LLMs on a single piece of commodity hardware (whether that includes one GPU or several), the difference between cloud vs. on-premise LLMs will largely be about where your hardware is located. There will be very little software configuration involved (just an HTTP endpoint that talks to the GPU). This is decidedly different from cloud products where the moat of hyperscalers is largely in the software and services on top of the hardware, not the hardware itself. (Sure, GPUs will eventually break & need replacement, too, but there's no state to lose, so that's already orders of magnitude easier than replacing hard drives.)

What toothbrush do you have? I've been looking for a USB-C charger for mine (standard Oral-B toothbrush) but the only ones I've found were from no-name Chinese brands and didn't work at all.

Meanwhile, some projects are doing the opposite, like going from Rust to Zig, here's an example from a podcast I recently listened to: https://www.youtube.com/watch?v=XSXGf3oN2yU

Thanks for the link! Unfortunately, contrary to what the title suggests, that video seems to be more about AI than about the migration? (Sigh…) I did, however, find the following document where they explain why they migrated to Zig. It makes for a nice read: https://gist.github.com/rtfeldman/77fb430ee57b42f5f2ca973a39...

That's all good and well but the UX sucks. I usually have dozens of commands like

  git commit -m "PROJECT-XXXX Foo the bar to baz the qux"

Also, having the ticket number in the subject line means every git-related tool I use will always display it (even if the rest of the message gets cut off).

Of course when we switched to GH issues, we largely abandoned JIRA and years later the instance got turned off and deleted. Now all those JIRA tags are entirely useless.

I agree that this is a problem but at the same time associating commits with a ticket number is useful, especially if I have dozens of commits on a single ticket and am doing trunk-based development (so not all commits are on the same short-lived branch). Maybe the lesson here is that, once completed, tickets should be exported and stored in the Git repository.

Do we know what the situation looks like with other popular indices such as MSCI World, MSCI ACWI, MSCI ACWI IMI, FTSE All-World, …? Do they have any requirement of 12 months of trading or of profitability or similar?

to settle bar bets

As I learned just yesterday, this is exactly how the Guinness World Records books came about. :)

https://en.wikipedia.org/wiki/Guinness_World_Records

Why would documents have menus? Menus are for applications.

s/menu/navigation

And there was nothing wrong with tables for layout, especially back then when the alternatives were very brittle.

I never said there was anything wrong with tables. OP said there was nothing preventing the design from being responsive, to which I responded yes, there was, at least in a lot of cases.

(Responsiveness was also mostly irrelevant back then because smartphones were not a thing yet.)

Right but how would you even display a vertical menu back then? `float: left` was rather bad, so you went back to using tables[0]. Good luck making these responsive.

[0]: and to using dozens of images sliced to fit your table cells, for that cool hover effect as well as round corners. :-)

I had the pleasure to talk to Loris about this topic just last week and I've liked his take very much.

His point is not coming from a place of LLM demonization. He very much acknowledges their usefulness, especially in a business context, e.g. for implementing yet another standard CRUD application and for shipping all the other "average" (in quality) business features quickly.

His point is a different one entirely: Say Andrew Kelley is attending the Zig Day. Why would you ask an LLM about a Zig programming problem you're struggling with instead of learning from the man himself? There's simply no LLM as knowledgeable about Zig as Andrew and the other people working on it or with it on the daily.

In other words: Zig Days are an opportunity for people to learn from each other and to spend time together (= the "Community" in "VP of Community"), and LLM are diminishing this opportunity.

Besides, Zig itself is mainly a language for people who care not just that a problem is solved but also about how it's being solved. ("Create software you can love.") While LLMs don't prevent anyone from doing so, they make it much more appealing to just vibe-code everything and not look too closely at the implementation.

What's needed is a global "Hide AI Dreck".

As a German, I couldn't think of a more appropriate usage of the word "Dreck".

Interesting talk, thanks for sharing!

they want to move the permission management from Flatpak into the service layer, through a new service called systemd-appd. Systemd-appd gives applications an identifier and stores their permissions, and then this data can be queried by the rest of the system. In turn, this enables a slew of other features, not least of which is subsandboxing.

This is fantastic news! As I've argued here on HN many times over the years, proper permission management is probably the single most important piece that's been keeping us from sandboxing everything by default, like on Android and iOS.