this post was submitted on 06 Jan 2026
10 points (66.7% liked)

Programming

24386 readers
344 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Rules

  • Follow the programming.dev instance rules
  • Keep content related to programming in some way
  • If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities !webdev@programming.dev



founded 2 years ago
MODERATORS
 

This science fiction / comedy / completely serious talk traces the history of JavaScript, and programming in general, from 1995 until 2035. It's not pro- or anti-JavaScript; the language's flaws are discussed frankly, but its ultimate impact on the industry is tremendously positive.

you are viewing a single comment's thread
view the rest of the comments
[–] spartanatreyu@programming.dev 3 points 5 days ago* (last edited 5 days ago)

Yeah, I'm the lead on a bunch of websites that all have to be localised.

There's a lot of weird footguns to watch out for, and a lot of retraining devs when they're used to only working on a single language/locale.

Two biggest head scratchers I've had to deal with are computers treating "fr-FR" different from "fr-fr" (due to file system case-sensitivity differences between developers), and having to undo the coded assumption that languages and locales follow an [a-z]{2}-[a-z]{2} pattern (e.g. "en-gb") once we stumbled upon Latino Americano: "es-419".


EDIT: My left ear really loves the Erlang talk.

This fixes it:

const audioContext = new AudioContext();
const audioElement = audioContext.createMediaElementSource(document.querySelector("video"));
audioContext.destination.channelCount = 1;
audioElement.connect(audioContext.destination);