They just described servant leadership and called it something else. It's not about parenting or treating people like children.
Readit Newsusernamed7 commented on Transparent leadership beats servant leadership entropicthoughts.com/tran... · Posted by u/ibobev
usernamed7 commented on Building optimistic UI in Rails (and learn custom elements) railsdesigner.com/custom-... · Posted by u/amalinovic
FWIW you don't even need to define custom elements to use them: https://html3000.dev/
usernamed7 commented on Goodbye, Price Tags. Hello, Dynamic Pricing nytimes.com/2025/11/28/op... · Posted by u/apparent
I expect price tags will become QR-code based, and you'll need their app to see the price. This will let them tailor prices to each person for minimal costs.
I don't think I am a dick, I guess that went without saying.
I'll take critique from other maintainers who have done as much or more open source work for similar returns over similar time periods. Funnily enough, I'm friends with many, and they are supportive the vast majority of the time instead of critical. Maybe that's because they can relate and you cannot.
> Maybe that's because they can relate and you cannot.
Now you're deflecting. I passed no judgement i made an observation of your statement and you took it personally.
There's a misunderstanding here what the issue tracker is for in Homebrew. In some projects, it's for free-for-all discussion. That's great if those projects want to use it that way.
In this issue's case, you have someone in leadership (p-linnane) communicating that work needs to be done, a maintainer (carlocab) communicating what needs to be done to make this change. xtqqczze's attempt to get us to move backwards on an already made decision doesn't help anyone. We have a discussions forum (and, well, the rest of the internet) for discussion of the pros and cons of decisions made. There's no point maintaining the illusion that we're soliciting feedback or discussion on the issues tracker when we are not.
As to me being a dick: I've been maintaining Homebrew for 16 years. It's used by millions of people. My full-time job has never been doing so and I've never been paid a market rate for my work on it (not that I expect or perhaps even deserve so). My primary concern with Homebrew is keeping the project actually running. This primarily requires the time, energy and work of maintainers doing so in their free time. It also requires contributors who submit pull requests.
Go read through some merged pull requests some time and you will see moderately to very positive responses from me. That's because that's the work that keeps the project alive. It has almost died several times in the past and I've kept it going. You may think it hyperbolic but drive-by negativity by non-code-contributor users is the biggest existential risk to projects like Homebrew.
> As to me being a dick: I've been maintaining Homebrew for 16 years. It's used by millions of people. My full-time job has never been doing so and I've never been paid a market rate for my work on it (not that I expect or perhaps even deserve so). My primary concern with Homebrew is keeping the project actually running. This primarily requires the time, energy and work of maintainers doing so in their free time. It also requires contributors who submit pull requests.
your explanation did nothing to speak to being a dick, did not attempt to apologize, only tried to justify the poor behavior.
Take a look at their codebase (posthog is open source) and then tell me again that collaboration sucks, because i feel like the lack of collab is why their codebase is in such terrible condition.
usernamed7 commented on The Costs and Choices of Kiki's Delivery Service econlib.org/the-costs-and... · Posted by u/gaws
i enjoyed this and found it insightful into thinking about costs.
usernamed7 commented on Friendship Begins at Home 3quarksdaily.com/3quarksd... · Posted by u/herbertl
i prefer self-acceptance.
once i learn to accept (grateful receipt of) myself (who i am, what i’ve done, what’s been done to me, what i do today) then it’s easier to accept (grateful receipt of) other people (who they are etc).
compassion is possibly apt too
> Deep awareness of the suffering of another accompanied by the wish to relieve it
ditto on self-acceptance being much easier to grasp and champion than self-love
GID's are great - i think the issue is with how they leveraged rubyLLM for something they should inherently not be using LLMs for.
> Remember that GIDs were made for facilitating ActiveJob serialization - they are a system-level facility, not a product-level facility.
I think this is somewhat obvious given the signature like gid://awesome-app/Post/32; there is no scoping to the user or account so it should be treated like a global lookup. If you need scoping to a user/account you can build that.
Honestly I think this is a matter of the author using poor design decisions and over leveraging LLMs. But this is not the fault of Rails, it is working as expected.
Be careful with LLMs!