You do raise a good point re: tradeoffs in a healthy society. Mill anticipated this objection and addressed it directly. He didn't advocate for free speech without consequences but developed a harm principle specifically to establish what limits are acceptable. Acceptable limits on thought and speech should be based on demonstrable harm, rather than alleged offence, discomfort, or the current popular opinion or cultural disapproval.

He recognises the need to set some limits, yet also the dangers of who gets to set them. Historically, those with power to restrict speech have restricted truth as falsehood. The bar for restrictions should be very high, not because free speech should be absolute, but because the dangers of overzealous restrictions far outweigh the cost of permitting speech we might personally find objectionable. Even completely false opinions might have their value as they force defenders of truth to better articulate their position or reasoning, and prevents beliefs from becoming prejudiced, or platitudes.

I thought I'd share since it's relevant and there may be some younger readers here that might not have come across his work. I really recommend reading it, even if it's an LLM summary as an introduction (as seems to be the trend nowadays)

Edited to fix a few typos (typing from mobile)

1. https://www.econlib.org/library/Mill/mlLbty.html#book-reader

And whilst nobody wants to risk being starved to submission, it's also equally important to promote more profitable sectors, and tax accordingly, so that we can support our more strategic sectors. I wouldn't say we're doing a good job at that for what its worth.

I just looked up the latest trade and investments factsheet[1] and there are some interesting deets. If you're wondering about direct investment in the US as well as imports:

- Total UK imports from United States amounted to £111.5 billion in the four quarters to the end of Q3 2024 (a decrease of 5.1% or £5.9 billion in current prices, compared to the four quarters to the end of Q3 2023).

- In 2023, the outward stock of foreign direct investment (FDI) from the UK in United States was £494.1 billion accounting for 26.7% of the total UK outward FDI stock.

In addition to direct investment I would also count portfolio investment since we're sort of involved at an individual level through our workplace pensions (and/or personal), savings, stocks and shares ISAs, and so on. A preliminary report[2] foreign holdings of US securities as of June 2024 puts the UK as the top holder at over 3 trillion USD.

1. https://assets.publishing.service.gov.uk/media/67b6f8efbd116...

2. https://home.treasury.gov/news/press-releases/sb0037

This is a really cool tool -- I often read latin texts with the original on one page and the translation on the other, just because I think it's interesting to see how they wrote/spoke at the time, but for the most part certain words or declinations throw me off guard. Inline literal translations really help there.

That being said, I noticed whilst reading some of the texts that the inline literal translations are still in latin, e.g. in "Part IV. I Some Barbarous Customs", most of the translated text is just latin. I guess OpenAI won't take all our jobs just yet!

I do have one suggestion for improvement though. Many of these texts have translations that are already in the public domain (older translations). It would be helpful to display the original Latin and a fluent English translation side by side, whilst still being able to toggle the literal translation on or off. This setup would make it easier to compare the original text with a fluent English translation, similar to the format used in some bilingual books.

The main point he's trying to make is not just about the logs you wrote but about logs coming from other systems or services, e.g. monitoring kernel logs in your OS. As he rightly points out, one of the reasons is that logs are not an API.

> One reason this happens is that almost no one considers log messages to be an API, and so they feel free to change log messages at whim.

If I were starting a project today in Python, I would definitely try setting up my tooling and processes to enforce type checking to at least some extent. Fortunately, we have a lot of guardrails that recover from the typical exceptions that occur in those cases, but as I experienced first hand, it's very easy to introduce new bugs when relying only on my intuition for those difficult-to-spot cases. Tooling definitely helps there.

My previous role had me writing TypeScript and Rust so there's always the temptation, or bias, to advocate for strict typing everywhere, but I'm conscious that it's neither practical nor feasible in large codebases with hundreds of contributors (most of whom may be more accustomed to dynamically typed languages).

edit: fixed postcode->city typo.

And on the topic of onions: it has a three page section on caramelising onions, which will take you anywhere from half an hour to over an hour, depending on the quantity. That book doesn't lie.

I also have cookbooks that have been gifted to me that belong in the trash. You can tell from just looking at the ratios, times, and method description that the dish isn't going to turn out as expected. Worst of all, my partner is the type that can only cook from a recipe book and this has brought on many arguments over a simple suggestion to deviate from the recipe.

> The freedom to distribute copies of your modified versions to others (freedom 3). By doing this you can give the whole community a chance to benefit from your changes. Access to the source code is a precondition for this.

Emphasis in "give the whole community a chance to benefit from your changes".

1. https://www.gnu.org/philosophy/free-sw.en.html#four-freedoms