I mean, they make me feel bad too, no question about it... But that's exactly why they're necessary.

There are two different things mentioned here, which I feel I need to clarify:

First, what you said about merging / creating a PR with broken tests. Absolutely you shouldn't do that, because you should only merge once the feature is finished. If a test doesn't work, then either it's testing for the wrong aspect and should be rewritten, or the functionality doesn't work 100% yet, so the feature isn't ready to get merged. Even if you're waiting for some other feature to get ready, because you need to integrate it or something, you're still waiting, so the feature isn't ready.

At the same time, the OP's point about tests being supposed to fail at first isn't too far off the mark either, because that's precisely how TDD works. If you're applying that philosophy (which I personally condone), then that's exactly what you do: Write the test first, checking for expected behaviour (which is taken from the specification), which will obviously fail, and only then write the code implementing that behaviour.

But, even then, that failing test should be contained to e.g. the feature branch you're working on, never going in a PR while it's still failing.

Once that feature has been merged, then yes, the test should never fail again, because that indicates a new change having sabotaged some area of that feature. Even if the new feature is considered "essential" or "high priority" while the old feature is not, ignoring the failure is one of the easiest ways to build up technical debt, so you should damn well fix that now.

Isn't the copyright specifically for the recordings/streams the league produces? I don't actually know if it's illegal to offer a stream using your own camera. Almost certainly against stadium rules, but as you said, they shouldn't be able to claim copyright in that case.

I've never used Mercurial, but a simple one based on the explanations and my experience with Git:

Locating the branch a commit originated from. If a git branch has been merged into (or rebased on) main or another branch, there's no way to tell which commit came from which branch. But sometimes I'd really like that information to figure out what prompted a certain change. Without it, I need to use external tools like a ticketing system and hope the other developers added in the necessary information.

Ah, nun, das Büro habe ich nie gesehen 😅

Als ob ich das nach all den Jahren noch wüsste, vor allem war ich selbst nicht mal dabei, weiß das nur vom Hörensagen.

Ein Mitschüler hatte mal in einer Klassenarbeit einen Tischgrill angeschmissen... Soviel zu "Sicherheit"

"History is written by the victors." - what I immediately thought of.

Pseudo-Shrink: "Just reimagine yourself! Be what you need to be! Rebrand yourself as a bishop, then you'll be happy :-)"

Ich kann an der Stelle zumindest teilweise relaten:

Ich war in einer Verteilerliste drin, die einem die Möglichkeit gibt, eine tägliche Zusammenfassung statt lauter einzelner Mails zu erhalten. Aber mein Mail-Client hat dann wohl die Mail für zu lang befunden und nur einen Teil davon angezeigt und den Rest abgeschnitten (vielleicht als Spam-Schutz oder so, keine Ahnung). Man hatte aber auch einen sehr offensichtlichen Button, um sich die komplette Mail anzeigen zu lassen. Vielleicht hat ihr Mail-Client ja etwas ähnliches gemacht und dort war der Button dann nicht so offensichtlich?

Heh,

how about forcing LaLiga to show evidence about damages? Because surely everyone who pirated their content would have paid if free streams weren't available, right guys???

If you want the magic explained, here's a start: https://en.wikipedia.org/wiki/Lempel%E2%80%93Ziv%E2%80%93Welch

Thanks for the suggestion, but I already don't use Google for actual navigation, just for rough estimations. I'm quite happy with OsmDroid.

Mine's a bit closer to your proportions, although I'm not sure if Google can accurately predict the effects climbing a steep hill up and down will have on cycling and walking. The weird thing is the public transport. It must not know about all available lines, because that should be more like 90 minutes.

Hardly a surprise, since Windows 10 didn't need new hardware to run. You could install it on anything.

Cookies required for the website to work (like that one) are totally fine and, in fact, they don't even have to ask you about them - if they're not used for tracking. So no, asking each time is definitely avoidable.

Because you don't need to have significant experience or rent a VPS in order to do that, and I can respect that. We don't need to force FOSS developers to become proficient in everything.

What needs to happen is some kind of tool (ideally FOSS) that lets you spin up an actual forum with the same difficulty to set it up as Discord.

Possible formula: Tax for n-th house = n-th Fibonacci number + 5 * max(0, n - 2). So low numbers like three get penalized by that linear part, and high numbers grow exponentially due to the Fibonacci number.

That may be true for smaller cities, but in bigger cities it becomes impossible, because there just isn't enough space to house all the people near areas of interest. Cars don't factor in there at all. Give me a subway for the major areas, and perhaps a tram or bus system so you don't need that many subway stations in the residential areas, and you can have car-free city centers.

I don't really like including pedestrians in there. Like sure, you can fit a bunch of people in a small area, but another point you shouldn't ignore is the throughput over time, and pedestrians are by their nature rather slow. Obviously if you're looking at shopping in a street lined by shops left and right, then that street becomes tailor-made for pedestrian traffic (and nothing else except perhaps bicycles). But public transport is much better suited for travelling any further distances, and that should be the main focus when deciding to ditch cars.