Notes from DotJS 2019

That was fun. Don’t be tempted by beanbag chairs after lunch, you will pass out. Here are my notes and links to videos.

Talks

• check your project’s babel-react configs to make sure the ‘development’ flag is on

• check if your project works with webpack’s futureEmitAssets option for forwards compatibility and reduced memory usage

• input element’s placeholder attribute is ignored by Google Translate, another reason not to rely on them as labels.

• custom dropdown menus (as substitutes to the select tag) usually have horrible accessibility, don’t make one from scratch.

• a more accurate job title: Javascript Dependerer (do we take NIH too far?)

• tools from Chris’ talk

  • Aka.ms/webhint4code uses webhint (another linting tool)
    • elements4code brings more debugging into VSCode
    • inclusive components goes deep on accessibility
    • [alex-js](https://alexjs.com/ for inclusive writing)

• Screaming Architecture

  Architectures are not (or should not) be about frameworks. Architectures should not be supplied by frameworks. Frameworks are tools to be used, not architectures to be conformed to. If your architecture is based on frameworks, then it cannot be based on your use cases.

  another link

• Regex named capture groups with (?<name>pattern), named back reference capture groups with \k, unicode property escapes with \p can be used for matching emojis, math symbols (from Stefan’s talk)

• Accidentally Quadratic for posts about slow code, probably from Vladmir’s talk

• Hybrid logical clock & CRDT, jlongster on github for data syncing across devices from Jame’s talk

• Nullish coaleasing, optional chaining are in some browsers.

• Node Conf 2009 had a drink mixing robot