Honestly, at this point I'm in favor of just changing the name. "JavaScript" sucks anyways. The spec already uses "ECMAScript.” We could even name it WebScript to match WebAssembly. Hell, call it UntypedScript for all I care. It's not even consumer-facing. WWF had to change to WWE. People can keep calling it JS for years (like Bonjour) as they slowly get used to it, and eventually it'll just become a weird piece of trivia about TheArtistFormerlyKnownAsPrinceScript.

https://deno.com/blog/deno-v-oracle4

Apologies to people who follow me for JavaScript content: At the moment, I’m focusing on TypeScript, but that will change again (I have many ideas for JS posts).

I’m tagging my TS posts with # TypeScript so that they are easy to mute.

The new iPhones are “celebrating color in an unparalleled way”.

But they do so very quietly, hidden inside phone cases. 😀

I’m now avoiding the names `foo`, `bar`, etc. in example source code (I used them a lot before “JS for impatient programmers”). Why? It’s easy to lose track of what’s what. Compare:

// Before
const foo = {bar: 'baz'};
foo.bar = 'qux';

// After
const obj = {prop: 1};
obj.prop = 2;

OMG i just learned something mindblowing with SF Symbols. You can create a custom symbol and combine it with other symbols and badges 🤯🤯🤯🤯🤯

#apple #sfsymbols #design