jedahan

framework 13 pro might fit this. Saying from someone who just migrated from m4 macbook pro 14.

I wish tap trust operated at the author/committer level than identifier level.

Its very personal and situation dependent, but I truly believe that if you work at Amazon or Facebook and do not want to support this, you can.

This is the kind of rationalization I am referring to.

Not sure if you meant to reply here?

Reminder if you work for any of these companies (not unlikely on this site) you are actively enabling this. If your first reaction is doubt, deflection, rationalization or discomfort, there are ways out.

That network is shared with police departments in cities outside Seattle per the article.

Code is a liability - the more there is, the higher potential for bugs and poor performance. I'd recommend treating cheap code like cheap toxic waste, and try to minimize how much is generated.

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.

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

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

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.