This has been frustrating me for a while and is part of why I explore other coding agents.
As many advantages as pi has in some areas, there are definitely areas where I believe the hype to be a bit overstated. While the config folder is, ultimately, not relevant for performance, how this was and is continued to handled is a bit frustrating for me.
They have made it abundantly clear it's not going to change however so I'm looking at how other coding agents perform currently.
Oh sorry - basically just a github ticket to an explanation about the .config folder. Pi doesn't respect XDG_BASE_DIR specification, and even if you use the env var it combines cache and config.
The ticket is closed and this will not be changed, period.
From what I understood in the ticket ( I haven't confirmed independently) it's the later. You can set an environment variable to move the .pi directory ( into your XDG Config dir) but it's both the cache and config combined.
What's even more frustrating is that there's a very simple and elegant solution suggested in the thread, to simply check for an existing folder and use the proper convention if not found.
Who cares, geez. Is a single github issue so important that this needs to land on the front page? You can move it and configure your own env to have it wherever you want.
This feels like the sort of decision that well meaning folks that manage utilities can disagree on. It's frustrating every time it happens because it's usually a fairly reasonable perspective to ask for XDG / operating system specific support for folders to be respected. (e.g. macOS's ~/Library stuff).
Posting a github issue like this though feels like an easy brigading target, so please don't do that.
I've been seeing this pattern so frequently of obvious simple things like XDG being ignored. Cynically, I think it's the result of I experienced people suddenly being able to make tools. They never learned all these standards, so if an LLM spews out a junky solution, they're none-the-wiser. Now we have a proliferation of software making mistakes on solved problems, as people are not slowing down to learn how things should be.
16 comments
[ 2.1 ms ] story [ 26.1 ms ] threadAs many advantages as pi has in some areas, there are definitely areas where I believe the hype to be a bit overstated. While the config folder is, ultimately, not relevant for performance, how this was and is continued to handled is a bit frustrating for me.
They have made it abundantly clear it's not going to change however so I'm looking at how other coding agents perform currently.
The ticket is closed and this will not be changed, period.
> even if you use the env var it combines cache and config
You mean both cache and config respect Pi's config env var, or that they get combined somehow independently of the variable?
I assume the former, just wanted to confirm.
Quick Edit: Since github is back up, heres the comment I was referencing: https://github.com/earendil-works/pi/issues/534#issuecomment...
Edit: Known issue: https://news.ycombinator.com/item?id=49330597
[1] https://github.com/earendil-works/pi/
I use pi and couldn’t care less.
Also, if every app would save their carp in my home folder it soon would be impossible to find anything.
Posting a github issue like this though feels like an easy brigading target, so please don't do that.