Internationalis(z)ing Code – Computerphile



Audible free book:
Catering for a global audience is difficult, Tom takes us through a ‘timezones’ style explanation of the things you need to keep in mind when internationalising your code.
This video features Tom Scott – more from him at: &

The Problem with Time & Timezones:

Emoji & the Levitating Businessman:
Heartbleed, Running the Code:
Floating Point:
Public Key Cryptography:

This video was filmed and edited by Sean Riley.

Computer Science at the University of Nottingham:

Computerphile is a sister project to Brady Haran’s Numberphile. See the full list of Brady’s video projects at:

source

46 Comments

  1. "If that surprises you, you need to get out more"
    No Tom, people need to stop believing in fairy tale ideologies and demanding people to believe in it too.

  2. I'm surprised that right-to-left languages got so little attention, I think it's one of the biggest problems on the list. Apps always deal with this horribly, and I'm not sure there is a single non-horrible solution

  3. As much of a giant pain as this all sounds, I can't imagine most solo programmers are going to try to make their website/application available in a ton of different languages. The type of software likely to have a bunch of language options is like to have been produced by a big company with a huge team of engineers and translators, so no one person would be having to deal with all of this complexity.

  4. Accommodating names was fine. Anything beyond that should not have been tolerated. A single standard is needed for things that operate globally. Precisely tracking time, measuring weights and distances, conducting global business should be (and are) done using UTC, the metric system and the English language respectively. Tolerating everything leads to huge inefficiency and a lot of problems. Imagine if rather than having a single gauge for railroads across the United States, every county in every state in the entire country had its own standard, where their section of railroad had its own unique gauge, its own unique thickness and height for each piece of track, its own materials, its own standard for load tolerance, its own way of joining sections of track. It would be a complete mess. Nothing would work well on such different tracks and there would be a lot of accidents and deaths. In fact, there was huge variation in track gauges in the United States in the past. Standard gauge was adopted across virtually the entire country by 1886 and the benefits of that have been huge. There were some losers too in that case, namely those who had spent their money buying trains that couldn't run on standard-gauge track but the winners (everyone else) gained far more than the losers like that lost.

  5. That's why you either not do it in English or just let your translations not match perfectly the grammar of that country. Who gives a s***t. English has already been standardised quite well in the world. The whole language thing for each country should be eradicated sooner or later

  6. I am Turkish and I love Turkish language so much. We don’t have genders, we don’t have plural systems, we don’t have umlauts, our letters don’t change depending on some bizarre rules. All thanks to Kemal Atatürk.

Leave a Reply

Your email address will not be published. Required fields are marked *

You might like

© 2026 Cantinho do Vídeo - WordPress Video Theme by WPEnjoy