In all of this Mercedes had some mechanical problems as well. Russel DNFed twice so far through no fault of his own and scored no points in Monaco because of the arguably faulty pitlane speeding measurement and subsequent penalties that shouldn't have been applied. Antonelli didn't score twice due to mechanical failures.

Hamilton is super consistent in scoring high-to-mid point finishes, but if Mercedes irons out their mechanical problems they are going to win both driver's and constructors championship this year.

I'm not too much into British elections but from what I've gathered he's mostly doing satire and making fun of absurd politics and politicians, whereas Trump was only ever in it for his own gain.

Oder die haben alle voneinander abgeschrieben. Es gibt weder eine Studie mit den Namen noch mit der DOI und auf der Seite des publishers ist auch nichts zu finden.

Das ist ein typischer Fall dafür, dass die Verkehrsführung dem Tempolimit entsprechen muss. 2 spurige, breite, gerade Strasse und Tempo 30? Verschnörkelte Landstrasse durch die Berge mit Tempo 100? Beides schon erlebt, beides Unsinn.

Das sind natürlich Extrembeispiele, aber zeigt wie die Verkehrsführung manchmal nicht den Tempolimits entspricht. Man kann nicht einfach Schilder aufstellen oder die Standards anwenden, sondern muss die Strassen so (um-)bauen, dass die sichere Höchstgeschwindigkeit intuitiv eingehalten wird.

Als Beispiel verkehrsberuhigte Zonen vor Schulen brauchen kein Tempo 30 Schild und Blitzer sondern müssen so gestaltet werden, dass schnell fahren unattraktiv oder gar unmöglich wird. Dann wird auch niemand "Opfer" von Blitzern und es wird viel schwieriger in einer unübersichtlichen Situation versehentlich zu schnell zu fahren.

The battery life seems surprisingly good, which could convince me to get it. Can you confirm if the 54 hours mixed use claim on their website is any accurate?

Writing this from a FP6 right now, last charged Monday morning and still about a third of battery left. This includes a lengthy video call and some regular mixed use. Usually I charge it every 3-4 days.

Als sehr sportlicher Jungendlicher - ich habe damals wahrscheinlich 8 Stunden pro Woche im Durchschnitt in meiner bevorzugten Sportart trainiert und dazu kommt nochmal einiges an Fahrradkilometern pro Woche - fand ich Schulsport immer total nutzlos. Um sich richtig in einer Sportart zu vertiefen oder etwas thematisch neues auszuprobrieren ist keine Zeit, also hat man einfach 90 Minuten irgendwas-Ball gespielt. Das hat meinem persönlichen Trainingsplan mehr geschadet als geholfen und entsprechend schlecht war ich in irgendwas-Ball auch. Den weniger fitten Schülern ging es meiner Erinnerung nicht viel anders, um in irgendwas-Ball mitzuspielen ist eine gewisse Grundfitness vorausgesetzt. Die Einzigen, die das gut fanden, waren die, die schon freizeitlich selbst viel irgendwas-Ball gespielt haben.

Darauf bauen die Lehrer dann eine Leistungsbewertung auf? Ich war fit aber mies in irgendwas-Ball, habe meine 1-2 bekommen, die weniger fitten eine 3-4 obwohl sie genauso mies waren. Von Fairness kann hier keine Rede sein.

Mit 90 Minuten pro Woche bekommt man auch keine Grundfitness aufgebaut. Dafür braucht man täglich etwas Bewegung und eine einigermassen gesunde Ernährung. Da sollte man die Zeit im Schulsport lieber nutzen, um diese Dinge zu fördern oder zu lehren.

Skill issue \s

Warum nicht beides? Das ist ein bisschen gewöhnungsbedürftig, aber man kann zusätzlich zu den Hocktoilleten noch Porzellanthröne für diejenigen, die sich hinsetzen müssen, hinstellen und dann hat man zumindest nichts verloren.

Also diese Szene aus "The Dictator"?

https://www.youtube.com/watch?v=olT8v8yMUEU

Here's a visualization of the birth rates of Japan, Poland and Germany against those of South Korea:
https://georank.org/birth-rate/japan/south-korea
https://georank.org/birth-rate/poland/south-korea
https://georank.org/birth-rate/germany/south-korea

Japan and Poland have been stable, maybe slightly declining, since the early 2000s, and Germany has been stable for 50, all below replacement, whereas South Korea is still going down.

I am no demographic expert, so take this with a grain of salt, but for the moment it doesn't look like the other countries are going to hit the same problems at the same severity anytime soon whereas South Korea is going to get hit by the full force of their demographic issues within a few short decades.

The growth (or in this case decline) is exponential. 1.08 is bad, 0.80 is terrifying. 1.08 is roughly half of the fertility needed for a stable population (about 2.1 children per woman). This means that per generation your population shrinks by half its size. 0.8 is another 25% lower. At an exponential rate these differences add up fast. The first one gives you (roughly) one child per 8 great grandparents. The other one needs 18. So over 3 generations the population shrinks by another factor of more than a half.

The decay products themselves decay through beta decay before arriving at a stable (at human timescales) U234 again. In the chain there is a bit of gamma radiation sprinkled in as well, but overall the decay chain, with the shielding provided by the glass, whatever other bedside obstacle there might have been and the probably small sample size should not have increased the obtained radiation dosage by a significant amount.

I write python code for a living. There is no way to sugarcoat it, the new unittests are slop. There already exists a good writeup of why, which I'm going to quote here:

So, look. One shot rewriting the whole test suite in another language is probably not great to do, but what happened here is so much worse than you are expecting. https://github.com/RsyncProject/rsync/pull/903/
This does not "translate tests into pytest" or a unit testing framework, it writes its own testing framework where tests are whole python scripts that redefine basic test functions in every script. Surely there would be a single way to "run rsync and get the results" - nope, well, there is, but then every test file will randomly redefine its own _run_and_capture function. So like now rsync needs a test suite for its test suite.
If instead of telling an LLM to "rewrite the tests in python" you just searched "python testing" you would find the pytest docs. And then you would find examples. And then you could write fixtures to deduplicate all the prior shell script setup and teardown stuff, and so on. But since it was just "rewrite the tests in python" its now worse than before, and the odds of the rewrite actually being a 100% faithful translation are close to 0.

https://neuromatch.social/@jonny/116666900898570791

Yes right - and after reading about a dozen of the test scripts I can definitely see why using pytest would be useful here to consolidate some of the behavior that was repetitive and ad-hoc in the original testing scripts. Like the tests need to do repetitive things like set up test directories with different names and structures, run and capture results, setup and teardown a server, parameterize over a range of values. Done right, a pytest suite would have made perfect sense and improved both the existing tests by making them more systematic and uniform, but also made it easier to add new tests over time. However that is not what happened, and what did happen is much worse because it did the opposite of almost all those desirable qualities.

https://neuromatch.social/@jonny/116671260017373441

You should read the whole thread, the author goes into more detail, as to why you cannot trust the software any more after the rewrite of the unittests and why you should avoid any new release of rsync since then.