Mais bien sûr ! Consider visiting France some day, it's not just the restaurants, supermarkets carry genuinely interesting ingredients. https://www.intermarche.com/produit/cervelle-de-porc/2889214...

its in the US too... just only in more, uh, earthy places.

> there are likely too many students to maintain a high standard of education anyway.

Right on point. I find particularly striking how little is said about whether the best students achieve the best grades. Authors are even candid that different LLMs asses differently, but seem to conclude that LLMs converging after a few rounds of cross reviews indicate they are plausible so who cares. The apparences are safe.

> Go also has a built-in "event loop"-type thing, but decidedly does not have a coloring problem.

context is kind of a function color in go, and it's also a function argument.

Which country if I may ask? I have lived in France Switzerland and Ireland and haven't seen something like this, even though governments provide the tax filing software.

I wonder if the explanation actually had to do with these people who used to do the job 15 years ago influencing the process to ensure they remain relevant. Kind of like in the US actually.

Praised for its functionality and freedom, yet notorious for its weak moderation and ties with Russia, Telegram is increasingly used for malicious campaigns. From anti-vaccination and flat-Earth conspiracies to disinformation and illicit activity, its freewheeling growth challenges the EU’s information space and digital governance frameworks. Drawing on EU-wide data and Ukraine’s experience, this article explores how Telegram has become a main conduit of disinformation in Europe’s information space and the need for oversight of its activities.

Can you please share a few sessions ? I want to get a better sense of what people have achieved with generic LLMs that is novel. (Emphasis on "generic", I think I can more readily imagine how specialized models for protein folding can lead to innovation)

It means that the language and runtime both agree not to look at your dead-end state, so no-one can say it's their fault ;)

For example I can define a notsemaphore actor that calls a callback once an internal count reaches 0, and then I can forget to decrement it and so it will never reach 0. But technically this didn't involve synchronization so there isn't a stack trace to tell me why is my program stuck and somehow this is better.

As someone that has spent the last week debugging a possible deadlock in pure async message passing code, I'm not amused :).

It would be technically deadlock free because you'd have a state that is unable to progress forward but it wouldn't technically involve a synchronisation primitive. In my view a real deadlock would actually be easier to debug but I'm just a caveman.

3. The use case is dynamic schemas and access is through the reflection API. Thus PGO has to be done at runtime...

I am talking with it in French, the UI is even localized. Dark theme is missing though.