They are museums run by companies about their own histories and industries. The TDK one was quite unexpected: it's basically a museum about very thin plastic.
For talks which will obviously be popular, go to the talk before it even if it's not as interesting. It's not common to have two super-popular talks in a row in the same room.
In Europe if an airline does that they have to pay you a penalty of a few hundred euro.
But KLM (Dutch flag carrier) found a way around that: if a flight is overloaded by weight they will keep all the passengers on board but leave their luggage behind. There is no direct penalty for late luggage, so many customers will get nothing except perhaps a little free shopping if they feel like filing forms to reimburse for having to buy clothes at their destination. But that's cheaper than the penalty for not taking the passenger on time, so KLM "optimized" it.
If that were true it would also apply to C and C++. I have used Valgrind with Python + Boost C++ hybrid programs and it worked fine after spending an hour making a suppressions file.
If you care about network bandwidth you can compress before sending, as virtually all web applications do. Then you don't need to worry much about the space efficiency of the application format.
That problem became known a decade ago, so it's somewhat surprising to see such a similar bug now.
This new one is worse because the drive cannot be used after reaching the magic number of hours. In the Crucial M4 case the firmware could be updated even after the bug struck.
Go typically relies on garbage collection, which is a no-no. Same with Java. This can be worked around, but you may find that programming a GC language with the GC unavailable is not better than C++ (and it may rule out the use of most third-party libraries).
Rust at a high level could be suitable, when well-tested libraries exist for it.
The example of "GB Technical Services, Unit W7a, Warwick House, 18 Forge Lane, Minworth Industrial Park, Minworth, Sutton Coldfield, B76 1AH, United Kingdom" could still reasonably be written within five lines this way:
GB Technical Services
Unit W7a, Warwick House, 18 Forge Lane
Minworth Industrial Park, Minworth
Sutton Coldfield, B76 1AH, United Kingdom
I don't think British people would actually write it as eight lines. Does anyone have a better example of an address that does not reasonably/conventionally fit on five freeform lines?
US addresses exhibit neither increasing nor decreasing specificity. Apartment numbers are usually written in the middle, like "30 Tristan Way, Apt. 107, Gwyneth VA 27384". This never seemed strange to me until I saw it being done more sensibly elsewhere.
Singapore is another good one: its postcode scheme changed twice in less than a century, and being a city-state, there is nothing useful to put in a "city" field (mail is often sent to "Singapore Singapore", or even "Singapore Singapore Singapore").
The US used to have five-digit postcodes, now has nine-digit ones, but laypeople mostly ignore the extra four digits. Singapore used to have two-digit codes, then upgrade to four, then to six. Maybe French postcodes will grow another digit or two someday.
https://www.tdk.com/museum/en/
https://www.khi.co.jp/kawasakiworld/english/
They are museums run by companies about their own histories and industries. The TDK one was quite unexpected: it's basically a museum about very thin plastic.