benediktwerner

The word used in the original comment was "revolutionized" and in reference to "the market", not "innovative" and not in reference to product functionality.

Wasn't it more about inconsistencies in JS though? For stuff which didn't need JS at all, there also shouldn't be much need for JQuery.

I don't see what that does. The AI hardly cares about it's reputation and I also can't really blame the AI when my boss or a customer asks me why something failed, so what does committing under its name do?

I'm ultimately still responsible for the code. And unlike AI, library authors but their and their libraries reputation on the line.

Interesting, as a German (which also has a similar system), I am the complete opposite, I find it super irritating when people address me by my last name. And the worst part is having to figure out how to address others, especially people you've known for a while but aren't really close to, e.g. say long-time neighbors I rarely meet.

Luckily, in the IT industry, it's common to just use first names with everybody.

As far as I understand, they would primarily be in the same peer group as all other people with their Korean age.

The way the conversion is done here, different sudokus produce different graphs. Besides the regular sudoku graph structure, there are nine additional nodes, each corresponding to one number. They are all connected to each other to ensure they must be different and each one is connected to each cell where the corresponding number is present as a clue from the start. This way, the graph doesn't need any pre-coloring to still encode the sudoku including the given clues.

I mean, you might still be right but I'd rather suspect that they didn't consider somebody running SQLite over S3 with 100ms latency ...

Presumably, it is faster on a saner filesystem.

You can also install rustup via your package manager and then use it as usual to manage your Rust installations. Though I guess in most cases, a single moderately recent Rust installation works just fine. But it's useful if you want/need to use Rust nightly for example.

Why would that make the setup harder? If they provide a statically-linked executable, you can just download and run it, without even the need to install jq or anything else. It's not like they'd provide Go code and ask you to compile it yourself. Go isn't Python.

Try giving a random human 30 chess moves and ask them to make a non-terrible legal move. Average humans even quite often try to make illegal moves when clearly seeing the board before them. There are even plenty of cases where people reported a bug because the chess application didn't let them do an illegal move they thought was legal.

And the sudden comparison to something that's safety critical is extremely dumb. Nobody said we should tie the LLM to a nuclear bomb that explodes if it makes a single mistake in chess.

The point is that it plays at a level far far above making random legal moves or even average humans. To say that that doesn't mean anything because it's not perfect is simply insane.

1750 elo is extremely far from beginner chess. The random mover bot on Lichess has like 700 rating.

And the article does show various graphs of the badly playing models which will hardly play worse than random but are clearly far below the good models.

From what I remember, one of the main reason also was to avoid bloating the JS on the game page. That page is kept especially slim to maximize performance and load times for low-powered devices.

Redid runs on the main server, where lila runs, as indicated in the diagram you linked. And moves are buffered in lila. Redis is only used for pub-sub.

This is a joke that's actually built into Python. The __future__ module is where you can import/enable features that will become the default in future versions. The point it makes by giving "SyntaxError: Not a chance" is that Python will never add braces.

And IMO for good reason. It makes the code so much cleaner and it's not like it particularly takes effort to indent your code correctly, especially since any moderately competent editor will basically do it for you. Tbh I actually find it much less effort than typing braces.

That still doesn't mean you spend zero on average. I assume pretty much all your clothes are less than ten years old. To have a 3.5€/year average, all the clothes you own would need to have costed at most 35€ total, which is clearly unrealistic.

Though 35€/year maybe is achievable, especially if you get/wear shirts, hoodies, maybe even shoes from conferences or company events.

You probably at least still need a decent pair of shoes, one set of nice clothes, a jacket, pants, and underwear. 350€ to get that stuff for ten years still sounds very tight but maybe possible.

You can judge the quality of a contribution by looking at the code. Who wrote it is completely irrelevant. The trust in the Linux kernel never came from knowing the names of all the people that contributed to it.

https://github.com/lakinwecker/irwin has more recent commits and I think is what actually runs on Lichess, or at least close to it. Not sure much fundamentally changed though. This isn't "the whole of Lichess' anticheat". It's a tool doing one specific thing which it mostly has been doing that way since it was created. There are a bunch of other parts to cheat detection, some of which are much more recent developments. For example kaladin, which has also been linked in the other thread about Lichess. But there's a fair bit more. Understandably though, Lichess doesn't really talk much about all of them, even though pretty much all of it is open source if you know where to look and how to use it.

This isn't the repository which runs on Lichess. The actual one does have much newer commits. Though not sure much fundamentally changed. Ultimately, I guess it does what it's supposed to do (catch obvious cheaters to save human time). But this is only one part of a lot of anti-cheating measures, including a lot more automated ones (some, like kaladin, which actually is a recent development, were also linked in the other thread about Lichess) but also a huge amount of human work. Most of the people here or in the other thread don't really know anything about cheating, how to properly detect it, and the difficulty of it.

Though ofc you're certainly right that this isn't a recent development at all and at the same time it's certainly also not perfect yet. And I doubt it ever will be. I don't think cheating in online chess is something that can ever really be solved completely.

There is only one server. Or well, there are lots of servers that make up Lichess but they mostly do different stuff. There is only one main server which handles all the core stuff including games.

Also, restarts usually aren't daily. They generally are around once a week. Though sometimes when a new feature is seeing rapid iterations or an important enough bug is found, restarts can happen a few days in a row.