<Comment deleted by user>
Respectfully, I disagree with the blog's viewpoint that adding more features to Lichess isn't necessary. More features can greatly improve gameplay, engagement, and user experience. While there might be maintenance challenges, the benefits of enhancing the platform outweigh them. There are several features that can cater to players of all skill levels and add depth to the platform. Embracing innovation and adapting to user needs will lead to a more enjoyable time on Lichess.
Seems like you misunderstood the blog's viewpoint. "adding more features to Lichess isn't necessary" is not it.
The point is announced in the title: "We don't want all the features". The post explains why not every feature is desirable.
At no point does it suggest that no feature is desirable.
Between everything and nothing, there's infinite room for nuance. Where we need to decide what to add, and what not to add. The post explains how we decide that.
The point is announced in the title: "We don't want all the features". The post explains why not every feature is desirable.
At no point does it suggest that no feature is desirable.
Between everything and nothing, there's infinite room for nuance. Where we need to decide what to add, and what not to add. The post explains how we decide that.
@thibault Can I suggest a new variant on November 2025?
I’m Reche, btw.
I’m Reche, btw.
Great philosophy. Simplicity is the way to go. Too often I see dev teams whose only apparent output is unnecessary features that invariably stay unused and have to be removed. I don’t always agree with Thibault but this is article is spot on.
Our goal is not to do everything that everyone can think of.
Should be rephrased to It isn't our goal to do everything everyone can think of. :)
Should be rephrased to It isn't our goal to do everything everyone can think of. :)
Hi @thibault ,
1- "All" could be in caps to emphasis your meaning
2- Regarding this, one thing that botters me is the multiple (close to 800) open Issues on github. I understand it is hard to keep track of all of them, however as someone who wants to help, I'd like to know :
How can someone who develops know if fixing/developing a feature is needed/wanted or not ? Should we ask you for each of them ? Are the only issues that are safe to take (read: won't be developped/realized in vain) the one marked "bug" and "Good first issue" [you mention "Good first issue" in /help/contribute, but not much more...]? Should one always ask on Discord when they are not marked as such ? or via PM@Discord (You're busy I get that and I don't want to be bothering you) ?
I also feel that the decision may depends on the code/modification needed to accept the resolution of an issue; but in some cases it seems it could have been marked as "Won't do/fix" before.
Perhaps a system where all new issues get tagged something may somehow be constructive. (E.g. a "To-confirm" tag ; asking people to confirm with devs and/or you before starting it; Some get no tag, and then realized without being merged)
Thank you !
1- "All" could be in caps to emphasis your meaning
2- Regarding this, one thing that botters me is the multiple (close to 800) open Issues on github. I understand it is hard to keep track of all of them, however as someone who wants to help, I'd like to know :
How can someone who develops know if fixing/developing a feature is needed/wanted or not ? Should we ask you for each of them ? Are the only issues that are safe to take (read: won't be developped/realized in vain) the one marked "bug" and "Good first issue" [you mention "Good first issue" in /help/contribute, but not much more...]? Should one always ask on Discord when they are not marked as such ? or via PM@Discord (You're busy I get that and I don't want to be bothering you) ?
I also feel that the decision may depends on the code/modification needed to accept the resolution of an issue; but in some cases it seems it could have been marked as "Won't do/fix" before.
Perhaps a system where all new issues get tagged something may somehow be constructive. (E.g. a "To-confirm" tag ; asking people to confirm with devs and/or you before starting it; Some get no tag, and then realized without being merged)
Thank you !
Does this mean we’re not implementing the space elevator
..maybe you should add "except in game analysis where we are looking to keep adding until it practically curses out your stupidity to you"
Exactly
Adding so many features destroyed Chess.com already
Adding so many features destroyed Chess.com already