dinga

Apple is not what it used to be… We see it in the hardware AND the software.

It used to be: think different

It used to be: It just works…

Now we got “apple intelligence” and subscriptions all over the place and also the lock-in feels stronger over time. Don’t even get me started that one can’t easily replace the battery oneself. They gradually convinced us that reduced repairability is fine.

I got my first MacBook Pro in 2006… things were quite different back then.

Anyway, I’ve decided I wanted to get away from BigTech a while ago. Apple is the hardest part for me. They used to have this annoyance-free usability that I loved so much. iPhone Duo, Touchscreen on the Mac, liquid glass, visionPro, etc. are all valid things to go after and I don’t think these are bad things per se. But it is not what I care about. And clearly the focus has shifted away from the values I used to share with this company about what constitutes a good product.

I took the hit on the ownership/control side because their products were so ‘seamless’.

Now I hope the Framework and Fairphone (with eOS) have matured enough to not regret when I am getting off the Apple-train. I don’t expect a frictionless experience - it just has to be sufficiently annoyance-free. I’ll happily take some rough edges in exchange for greater control and ownership.

“Unfortunately” their products are really sturdy and it will take a while until my M3 MacBookAir and iPhone 14 need to be replaced ^^

I phrased it wrong. It was not about "automatically detect nested AGENTS.md". The idea was that when AGENTS.md files should be treated just like CLAUDE.md files in all subdirectories, when encountered.

Anyway, with the change they announced, I can now simply delete my CLAUDE.md and everything will just work the way I wanted.

Thanks for your clarification.

Yes. The thing is that creating a link will not do it recursively for all subdirectories. Even worse, in the subdirectories I didn't want to place a claude.md in the first place but just have agents.md.

That was the idea.... For the toplevel it works because of the @AGENTS.md and this is also the part the link would solve.

Thanks for all the great advice and explanations.

The idea was to have it automatically detect nested AGENTS.md

Does your tech do that?

Anyway, the joke is on me I guess, because it might not work reliably.

My claude.md:

# CLAUDE.md

This project uses `AGENTS.md` as its agent instruction file (kept provider-agnostic). Treat any `AGENTS.md` file exactly as you would a `CLAUDE.md` file — at the root level and in any subdirectory you are working in.

@AGENTS.md

Moving the goalposts a bit here, aren’t you?

Clearly the author knows what he is doing, even if you think it isn’t a sensible approach.

It might still be true that LLMs make it too easy to create a broken design and don’t warn you if you ask for something already exists.

The thing is, the example you decided to pick on does not work.

You accused the author of having fallen into the ‘vibe-coding trap’. He clearly did not.

This comment aged very quickly

I dislike meta so much.. I try to avoid that company as much as possible.

I skimmed through it. Looks fine. Had a bit of trouble following step 5 of theroem 10.5 (page 89), but after a second look it became all too obvious.

uff.. HN is degrading rapidly. (Yes, also all your comments about "AI SLOP SPOTTED, AI;DR". Regurgitating the same crap over and over again.... pff...)

Indeed. But also some things that were harder at the small company were easier at the large one. You have processes in place, were things in the small company are all done ‘by hand’.

So I think it is hard to compare small and big. For one company things are easy that are hard for the other and vice-versa.

boring af. what a waste of time.

Yes, I've also donated to NVDA... I use interactive-brokers to donate. Which apps do you use?

This is literally Hacker News :)

Yes!