The linked post on Take Take Take is interesting. Magnus Carlsen created a chess.com competitor and eventually sold it to chess.com and became a sponsor. While working as a sponsor he then created a new chess.com competitor.
I'm a Lichess patron and happy to see them get support, but I do feel a bit bad for chess.com in this case. Magnus is such a big figure in chess that organizations like FIDE and chess.com feel they have no choice but to accommodate his whims, but that doesn't come with any guarantees. I hope Lichess does not find themselves in a poor position if Magnus decides to "alter the deal".
All large systems are inherently weak when one individual has an outsized influence on their outcomes. The solution is not to hope Magnus is altruistic, but to not allow Magnus (or any individual) to drive meaningful outcomes directly or through their combined influence/followings.
The only thing I love about chess.com is the ability to create custom variants, edit them, and unleash them into the wild. Been loving minihouse lately, such a cool variant.
Would love to see Lichess add bughouse, as its cousin Pychess recently debuted it and it seems to work fine. Chess.com has bughouse.
I love Lichess more than anything, and I hope this brings a lot of donation to them that they can use independently, and that the Lichess brand does not get subsumed by Take Take Take and their corporate money.
Above all, with everything that's happening in the software engineering world rn, I look at Chess as a place were we've seen it play out in the past decades. And Lichess is a big part of that.
I hope this deal helps two things:
(1) Bring more people to Chess,
(2) Actually, help Lichess find out a way to reward those working in it as much as they deserve.
Lichess is written in Scala and is hosted on dedicated OVH for a very significantly small amount of money (I think just a few thousand dollars per month) and hosts so many millions of players and games.
It's an understatement how well optimized they are right down to the optimization techniques that they use and the infra providers that they use. The same thing even in something like AWS could cause significantly more amount of money.
It also shows that you don't need AWS/GCP/Azure for basically just about everything, to be honest.
Lichess is a beacon of hope and congrats to the lichess team for this cooperation with TTT.
> It also shows that you don't need AWS/GCP/Azure for basically just about everything, to be honest.
That's where they won, people think AWS/GCP/Azure has to be the default while in reality, the number of platforms that actually need to be able to scale up/down fast are probably below 1% of all platforms out there. Most platforms would save money and run better with proper dedicated hardware rather than going for clouds by default.
Flashback to a moment in my life where a team pushed (successfully) for building a distributed architecture for an app that we didn't even knew if it had product market fit yet. Fast forward 3 years to today and the app is no longer online, but while it had 5 users they were using really reliable infrastructure, I guess that's cool.
Depending on the development cost of being in the cloud, it was probably the right choice. Optimizing for cost per user when you don't have product market fit is probably the worse early optimization.
Lichess has been absolutely fantastic platform. AS a chess enthusiast as an engineer of a chess website me and some others are building (shameless plug, https://chess67.com), they are the only platform I have worked with where so much is so easily accessible in terms of their APIs.
Their Oauth requires to special app registration nor any oauth secrets - only platform I have seen that does that.
I do wonder how this opens up ability for people to integrate Lichess’ player pool to their own apps.
Huge respect to Lichess. Open source, no ads, super clean interface and super functional website. Chess.com is a pain to use compared to it.
All their finances are also public: https://lichess.org/costs
The linked post on Take Take Take is interesting. Magnus Carlsen created a chess.com competitor and eventually sold it to chess.com and became a sponsor. While working as a sponsor he then created a new chess.com competitor.
I'm a Lichess patron and happy to see them get support, but I do feel a bit bad for chess.com in this case. Magnus is such a big figure in chess that organizations like FIDE and chess.com feel they have no choice but to accommodate his whims, but that doesn't come with any guarantees. I hope Lichess does not find themselves in a poor position if Magnus decides to "alter the deal".
Business is business. Non-competes expire. Don't waste your feelings on chess.com.
All large systems are inherently weak when one individual has an outsized influence on their outcomes. The solution is not to hope Magnus is altruistic, but to not allow Magnus (or any individual) to drive meaningful outcomes directly or through their combined influence/followings.
Well for the chess world, open source world (BDFL), etc probably okay. For real world governments...
Love Lichess.
The only thing I love about chess.com is the ability to create custom variants, edit them, and unleash them into the wild. Been loving minihouse lately, such a cool variant.
Would love to see Lichess add bughouse, as its cousin Pychess recently debuted it and it seems to work fine. Chess.com has bughouse.
I love Lichess more than anything, and I hope this brings a lot of donation to them that they can use independently, and that the Lichess brand does not get subsumed by Take Take Take and their corporate money.
Lichess, you guys rock.
Above all, with everything that's happening in the software engineering world rn, I look at Chess as a place were we've seen it play out in the past decades. And Lichess is a big part of that.
I hope this deal helps two things: (1) Bring more people to Chess, (2) Actually, help Lichess find out a way to reward those working in it as much as they deserve.
Keep on the amazing work,
Lichess is incredibly well optimized [0] (and an amazing public service). I'm sure that this is very cost effective for TTT, so a win-win.
[0] https://lichess.org/@/revoof/blog/optimizing-the-tablebase-s...
Lichess is written in Scala and is hosted on dedicated OVH for a very significantly small amount of money (I think just a few thousand dollars per month) and hosts so many millions of players and games.
It's an understatement how well optimized they are right down to the optimization techniques that they use and the infra providers that they use. The same thing even in something like AWS could cause significantly more amount of money.
It also shows that you don't need AWS/GCP/Azure for basically just about everything, to be honest.
Lichess is a beacon of hope and congrats to the lichess team for this cooperation with TTT.
> It also shows that you don't need AWS/GCP/Azure for basically just about everything, to be honest.
That's where they won, people think AWS/GCP/Azure has to be the default while in reality, the number of platforms that actually need to be able to scale up/down fast are probably below 1% of all platforms out there. Most platforms would save money and run better with proper dedicated hardware rather than going for clouds by default.
Flashback to a moment in my life where a team pushed (successfully) for building a distributed architecture for an app that we didn't even knew if it had product market fit yet. Fast forward 3 years to today and the app is no longer online, but while it had 5 users they were using really reliable infrastructure, I guess that's cool.
Depending on the development cost of being in the cloud, it was probably the right choice. Optimizing for cost per user when you don't have product market fit is probably the worse early optimization.
This is huge, congrats to the lichess team.
Lichess has been absolutely fantastic platform. AS a chess enthusiast as an engineer of a chess website me and some others are building (shameless plug, https://chess67.com), they are the only platform I have worked with where so much is so easily accessible in terms of their APIs.
Their Oauth requires to special app registration nor any oauth secrets - only platform I have seen that does that.
I do wonder how this opens up ability for people to integrate Lichess’ player pool to their own apps.
Big fan of Lichess here. Such a great and underrated service.
The free open source model does have its competitive advantages!
As it happens "Take Take Take Sign Cooperation Agreement" is also OpenAI's modus operandi when it comes to the publishing industry.