u/roelschroeven

Error handling is both really annoying and an absolute necessity. All these special cases that you have to account for, but that distract from the main flow of your code, but without it your software explodes on first contact with the real world.

On one hand, yes, the text goes on and one without any real substance. On the other hand texts in musea etc. about art works and artists feel to me exactly the same.

You can, but it's a side effect of how classes work in Python. You can always call object.method(arguments) as method(object, arguments), but that doesn't mean it's the intended way to do things. separator.join(iterable) is how it's taught, is how it's documented, it's how it's meant to be used.

I think the question is why is it designed that way, as opposed to join(separator, iterator) or join(iterator, separator) or iterator.join(separator).

Israëlische propaganda in een poging om zich vrij te pleiten. Klopt niets van.

Clean-room is not a defense against patent lawsuits at all, it's a get-out of copyright infringement.

Pro Palestina als in voor mensen en tegen genocide.

If we ignore air resistance and other non-ideal stuff like that, the time for a round-trip through such a straight tunnel happens to be exactly the same as the period of an orbit at the height of the tunnel entrance. Such an orbit is of course impossible because you'd run into terrain and atmosphere and such, but still it's interesting that both calculations come to the same answer.

The Foundation is the one that doesn't really do anything useful, isn't it? Isn't the Corporation the one that actually pays the developers to develop Firefox, and hence the one that needs money?

You're right that tools like CMake are what you should use these days.

Just for completeness though, I want to mention that makefiles are more than just shell scripts. Crucially, they allow specifying dependencies, they check what is changed and what is not, and use that to only rebuild stuff that needs rebuilding. Doesn't matter much for small projects, but very important for large ones.

That being said, Ninja does that too but better, and CMake + Ninja is preferable over makefiles.

7th stage of TdF 2017 apparently, with a difference of 0.0003 seconds (0.3 milliseconds) between Marcel Kittel and Edvald Boasson Hagen (https://www.telegraph.co.uk/cycling/2017/07/07/tour-de-france-2017-stage-seven-live-race-updates-chris-froome/).

Anyone can import the image in some drawing software and draw a vertical line. That gives something like this: https://imgur.com/3Vzozad If you zoom in, there is a small but clear time difference between Evenepoel and Ciccone.

Did they really say that?? I didn't hear that, but then again I often kinda zone out because of all their bs.

Why don't we simply stop after the "Users grow to live it" step? Wouldn't avoid a lot of grieving, a lot of useless work, and free up developer time to work on what really matters?

These days any criticism, however well founded, gets labeled as hate. With that definition it's easy to get a lot of haters.

But I am convinced that many of those people express those criticisms precisely because they like Firefox, and because they want it got even better.

That was Nys who said that.

Switzerland should be neutral

But MVDP got two yellow cards for incorrect position on the bike and got disqualified.

Wout gives himself a chance of 8%. Weirdly specific, but other than that sounds realistic.

You're wrong, it does apply when one rider is caught up by another.

From the official UCI regulations: https://assets.ctfassets.net/761l7gh5x5an/6FEzFHeA2oKMBGb5sdIvQ7/9da669a83c210f198edf4783dcb49113/2-ROA-20260901-E.pdf, p. 57 (this is in the section on individual time trials):

2.4.017 If one rider is caught up by another, he may neither lead nor follow in the slipstream of the rider who caught up.

2.4.018 A rider, upon catching up with another shall leave a lateral gap of at least 2 metres between himself and the other rider. After 1 km, the rider caught up shall ride at least 25 m away from the other.

2.4.019 If necessary, the commissaire shall force the riders to leave the 2 metre lateral gap and the distance of 25 metres respectively, without prejudice to the penalties provided for in the scale of penalties (article 2.12.007).

2.4.020 Riders may not help one another.

I have never seen the UCI taking action against drafting in ITTs. Typical UCI: make rules but don't enforce it. Riders start ignoring the rule. At some point some unlucky rider will be the victim of UCI's arbitrary rules.

Same with sock length. I don't know why that rule exists, but it does exist and is almost never enforced. Look at the socks and this ITT: a large percentage have socks clearly longer than midcalf.

"Important race update: GC times will be taken with 9.8 kilometres remaining. There will be no bonus seconds at the finish, while the points classification remains unchanged."

Yes, I'm pretty sure you're right. The time for GC is taken at some point before the finish line, but it only counts if you actually cross the finish line. And of course the finishing order is still determined by the actual order the riders cross the finish line.

Maybe the last lap is considered more dangerous because of the chaos of the sprint teams trying to position themselves?