@WillCJohns@FabianoCaruana Lichess isn’t much better in this regard: Single point of failure for gameplay, significant lag for non-Europeans, mobile app frequently times you out after you’ve made your move, rampant cheating that is only acted upon if you fill out a form with detailed information, etc.
@JamesWard Depends on how limited the declarative language is. (The limitations may be caused more by Mill’s architecture than the declarative language used.) The moment you need to escape to the macro-based Scala DSL, everything (including the tooling story) gets a lot more complicated.
@JamesWard Ah, that must be new. The Scala DSL is definitely hindering adoption outside the Scala ecosystem, but the YAML looks like coding Scala in YAML (`object test: extends: […]`) and may be very limiting.
@durarbayli Most of Lichess’ competitors suck at software development. That’s why they can’t build anything better despite (some of them) having far greater resources. For example, Chessable has been around for a decade and has never had a working engine. That’s both a tech and mgmt failure.
@JamesWard@VladimirSitnikv You might also want a way to detect that adding a dependency changed the version of an existing (transitive) dependency. Diffing lock files is one such way. Another is (being forced) to resolve version conflicts explicitly.
@Roktimchess@Dixit__Nikhil Modern (Apple Silicon) Macs no longer support dual boot. I ran ChessBase in a Parallels/VMWare virtual machine for years, but it was a performance/stability nightmare. Eventually gave in and bought a Windows gaming laptop just for chess(base). Never looked back.
@natesolon I started to question his sanity towards the end of his career, when he repeatedly took irrational risks and kept insisting in post-game interviews that he had been winning left and right until his opponent escaped by a miracle. Even Ding couldn’t stop laughing.