No need for the extra tap step, this works fine alone:

    brew install Arthur-Ficial/tap/apfel

They certainly have more choices than implementing in this manner, and can choose to not implement it as well.

Absolving Apple of responsibility gives more than they deserve.

They actually have very few choices, and they had only a few months to get it done. Just like the rest of us.

great for astral, sucks for uv. was nice to have sane tooling at least for a few years, thanks for the gift.

I really hope they don't kill off uv or turn it into some way to sell OpenAI services. But I suspect that's exactly what's going to happen :(

I don't know. yarn never really turned into a vehicle to sell Facebook, though you always kind of transiently knew it was FB that offered it. I imagine that sort of transient advertising is it's own value, too.

As much as I dislike facebook they have been pretty good stewards of their open source projects and mostly seem to let them stay isolated.

Time for the PSF to consider something inspired by uv as a native solution.

The core-adjacent people have completely failed to produce reasonable packaging tools for decades, why would you want another new tool from them?

Who said anything about it coming from core-adjacent people?

Was Kenneth Reitz "core-adjacent" when Requests was brought under the PSF umbrella?

Is there anyone seriously involved in packaging who is neither working at Astral nor a PyPA member?

Well, if I didn't have a bunch of other ideas for things to work on, and if I felt like anyone cared, there would be me....

I prefer low effort human thought to low effort llm output.

Making home read-only can get there, and I can't find the project that forced using XDG paths. I think it used LD_PRELOAD or somesuch trick.

edit: https://soc.me/standards/defending-home

Strange. Middle-clicking the link opens a HackerNews frontpage, but copypasting into a new tab shows the article. Presumably the server shoos away referer links? To reduce load maybe somehow? Or maybe something's weird in my own configuration idk.

They explicitly check if the referrer is hackernews and do that.

I had the same issue as you. Had to copy and paste the link.

I do the same for years and had no idea that disabled emails are blocked, is that documented anywhere? Will have to switch if so.

When I tested all the p2p messengers I could get my hands on for Android and iOS about two years back, the only one that worked at all without having a router around was Briar. Glad to see it helping people.

I was wondering the same thing. My best guess is that is to guard against operator misuse. Like usb-a only plugging in one way. Anything that is secret will never accidentally print to stdout. String interpolation in bash with `—option $empty` might be safer than `8<$empty`. Have to explore more but yeah, this is a new pattern for me as well.

Another possible factor driving the decision to use numbered file descriptors: the logic to validate that a file exists (or can exist) at a given path, is readable/writable, etc. gets punted to the shell instead of being something the program itself has to worry about.

Those descriptors like 5 could be mapped to anything, including descriptor 1, stdout.

:(

I felt bad making a long thread once I opened Element X and saw it didn't have support for threads.

Someone let me know later that threads are hidden behind a Labs setting, but it only allows the client to reply to threads, but still exposes the entire thread inline for the channel which sucks up all the air in the chat.

this is wrong - the threads support in labs lets you create threads and navigate into them as you expect.

what you are describing is the old threads workaround which predates the proper solution in labs which should exit labs asap.

I am describing what I see on Element X on iOS today. If someone replies to threads, it is not hidden and navigable on this client. Even after switching the labs feature on, the app was showing the thread interspersed with the rest of the conversation.

Uninstalling the app, reinstalling, and making sure the labs option is turned on before navigating to a room with threads, is behaving how I expect.

So maybe, its a bug that the room does not re-render after toggling that setting.

ah right - that sounds very plausible; sorry for the confusion. have filed it as a likely bug at https://github.com/element-hq/element-x-ios/issues/4810 - thanks for the report :)