- From: Filip via GitHub <noreply@w3.org>
- Date: Sun, 24 Aug 2025 14:55:32 +0000
- To: public-hydra-logs@w3.org
@lanthaler This kind of approach is exactly why Hydra risks never breaking out of its niche. When energy is wasted on ego-driven, self-centric arguments over trivial details, it doesn’t look like an open standard, it looks like a closed show. Insisting on control over things that don’t actually move the spec forward is not stewardship, it’s vanity. And that vanity sends the worst possible message to potential adopters: that Hydra is more about protecting egos than solving problems. Standards only thrive when they lower barriers, encourage broad use, and make outsiders feel welcome. Every time Hydra leans into self-importance over practicality, it loses another chance to be taken seriously. If the goal is adoption, then ego needs to take a back seat. Otherwise Hydra will remain what it increasingly looks like from the outside: a small, closed show arguing with itself. -- GitHub Notification of comment by filip26 Please view or discuss this issue at https://github.com/HydraCG/Specifications/issues/181#issuecomment-3218168111 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Sunday, 24 August 2025 14:55:33 UTC