> So what language to you propose we use to rewrite all video and audio software? Javascript, Lua, Brainfuck, what? It's not proposing a particular language; o

> So what language to you propose we use to rewrite all video and audio software? Javascript, Lua, Brainfuck, what? It's not proposing a particular language; only a property was proposed: memory-safety. This was defined loosely: > Garbage collection was invented in 1959, for Lisp, the first memory-safe language. It provides the foundation for memory safety and it is used in most memory-safe programming languages today. (It is also possible to have memory-safe languages without garbage collection, e.g., Cyclone or Rust.) We could compare this with other properties of programming languages which have been tried in the past, but are now considered bad ideas or a last resort: - DWIM (Do What I Mean): if a name (function, variable, etc.) doesn't exist, use one with a similar spelling - Ignore errors by default: eg. Bash without "set -e", visual basic's "On Error Resume Next", etc. - GOTO: still useful on occasion, but no longer the "go to" control structure in most code (pun intended) - Dynamic scope by default - NULL: Perhaps controversial, but also infamous. Can be tamed with nullable types, or eliminated with option types. - "Loose typing", ie. the casting rules in PHP, JS, etc. which break symmetry and transitivity of "==" - Automatic semicolon insertion: Either require semicolons or don't; trying to guess leads to problems - Name-based typing: eg. in FORTRAN any variable name beginning with I, J, K, L, M or N are implicitly ints, anything else is implicitly float I would certainly consider memory unsafe languages in the same category. There's no need, now that we have garbage collection and linear types.