clodboy @wallhackio@cat.family

@Lady @vaporeon_ oh that's based as hell, deno wins again

@coriander the coolest goblin

@mia pretty sure that we live on a flat disk and some giant star called the "capri sun" or something like that, i dont remember, is rotated in circles and it projects a cone of light on subsets of the earth at any given time. im pretty sure god is responsible for keeping that star moving all the time.

but who knows, im not a scientist

@amy something something "soju of love"

@vaporeon_ thats what my couch it for

@aescling @amy pretty sure they dont

@aescling @amy the catwins strike again

@aescling @amy do milotics nya

@amy here, allow me to make that problem even worse

@aescling @vaporeon_ have PATIENCE you creature whose name i forgot

@vaporeon_ regarding ES5 and ES6:

The language had a small spec update in 1998 (ES2) and then a more significant update in 1999 (ES3). ES3 is when the language really caught on.

ES4 was then developed for many years but due to political differences, poor management, and concerns of growing complexity in the proposals, it was tossed and the committee started over. They were not able to come to a consensus on a new update to the language until 2009, at which point they decided to call the spec ES5 instead of ES4 for some reason.

ES6 was then developed in 2015 and was the most impactful update the language specification. It introduced an entire new syntax for declaring functions, new syntax for declaring variables, promises (a built-in abstraction for concurrency/asynchronous programming), template strings, generator functions, weak references, and so much more. It completely changed the language. (Mostly) for the better.

@vaporeon_ sun microsystems trademarked JavaScript in the 90s because of course they did, so when JavaScript was standardized (I believed in 1997?) the committee was not sure if they had the rights to publish a document with that term.

they were going to call it LiveScript (or was it ActionScript? i forgot which) but Netscape had also trademarked that name and as such the committee wasn't sure if they could use that name either.

the group which standardized JavaScript was, at the time, part of the European Computer Manufacturer's Association, or ECMA for short, and since they ran out of time before both Sun and Netscape could get back to them regarding the preferred names, the committee decided to settle with the name ECMAScript. Nobody liked the name but it was chosen and now it stuck.

@Lady how interesting. i, myself, am over a decade old. perhaps this was meant to be

@vaporeon_ are you familiar with the term ecmascript?

if you can understand this toot then there is no hope left for you.

fuck typescript im gonna rawdog some pure untranspiled es6. as a treat

it is a shame that the javascript ecosystem is so fucked because the language itself delights me

an onion is carmelized when heated. a properly carmelized onion takes many hours to create.

so, too is my brain. i see now, that my mind is not being burnt, but instead carmelized into its final, delicious form

@vaporeon_ i will ask you for help. if the need arises.