8
The Birth & Death of JavaScript (www.destroyallsoftware.com)
submitted 10 months ago by to c/programming@programming.dev
8 comments fedilink hide all child comments
 

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
[–] 8 points 10 months ago (5 children)

-4 votes?

Is someone sockpuppetting?

This was and still is a classic talk, right up there with wat, juice it or lose it, fuck you pay me, the art of code, and pwned by the owner: what happens when you steal a hackers computer

  • permalink
  • fedilink
  • source
  • hideshow 5 child comments
    •
  • [–] 3 points 10 months ago

    Thank goodness it's not just me! When I first saw this post yesterday, there were no comments and it was already quite downvoted. I wached the first 1/4 or so and didn't find anything objectionable; actually it seems quite good. I started checking to see if the guy had recently fiddled kids or spoken out in support of ethnic cleansing or something. The downvotes don't make sense to me either.

  • permalink
  • fedilink
  • source
  • parent
  • [–] [S] 3 points 10 months ago* (1 child)

    I like these as well!

    Erlang: The Movie

    Timezones - Computerphile

    Internationalisation - Computerphile

    I was the sole ui developer on a white-labelled flight search and booking web app that had to support frenchy french, canadian french, mexican spanish, and japanese (rtl), and english. And IE11! Those computerphile ones hit hard, formatting currencies, dates, times all in different time zones and currencies. Fun times lol

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 1 child comment
    •
  • [–] 3 points 10 months ago* (last edited 10 months 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);
  • permalink
  • fedilink
  • source
  • parent