I’ve found Wallaby (https://wallabyjs.com/) to be a great addition to my tool chain over the last year.

It is an automated test runner for JS / TS code with a great integration with ides. It has made writing tests and refactoring so much more productive.

At a previous employer we had a high up executive from Facebook come out to give a presentation.

One of my main take away was that one of FBs big goals was to build a 'knowledge economy'. It struck me as a bit of an odd objective at the time, but I think I am now starting to understand what this means (and it's a little scary).

I am not convinced that parameter type inference is a reason to use flow. I have seen examples where flow fails to report errors because it can't infer the parameter types. I would rather consistency over inference that sometimes works sometimes fails silently.

For example:

  function fn(a) {
    const {b} = a; 
  
    console.log(b.c);
  }
  fn({});

This compiles without errors - but would fail at runtime. https://flow.org/try/#0PQKgBAAgZgNg9gdzCYAoVUCuA7AxgFwEs5swp...

Yep, reported to Flow issue tracker.

This library is great! My team uses it extensively to generate types for both our server and client from our Api definitions (in RAML).

There is a typescript example on their page:

https://github.com/zeit/next.js/tree/master/examples/with-ty...

Indeed, however it managed to crash my browser after clicking that button a couple of times.

To be fair a reasonable amount of people find Oculus rift makes them nauseous in any application.

But 99% of times it's motion sickness. You only get it if the camera moves, which is not the case here.

Its a little scary how big that list is.

My concern is that this is a great source of websites with poor security for potential hackers to exploit.

That's why we should use different passwords on each website

Thankfully password managers and software like iCloud makes this extremely easy. There's no excuse to not do it!