alexkoeh

Congrats on the launch! We looked into barcode scanning with webassembly about 2 years ago, and the open source libraries weren't great. Really glad to see that webassembly can work well for this.

Not OP but glad you mentioned this. We're starting to look at internal tooling libraries and this looks really interesting.

This is art

This is awesome. As our userbase grows I've been wondering how to best address this problem.

When we have a migration that requires more than 500 batch writes, we first got around that by building an array of batches with 500 writes per entry, then committing all of it at the end. Then we discovered the bulkWriter API in the node.js library which gets around the 500 batch limit. It looks like `createBatchMigrator` only supports up to 500 writes due to the firestore batch limit. Is that correct?

Is it possible for Cmd+P to work when you don't have the Debugger tab in focus? That one of the few things I miss from Chrome dev tools.

Performance-wise it's been running great for me. The hard work you've put into this definitely shows.

Redux the library is not "state management for react". It's more of a concept that gives you a predictable structure around how state changes over time.

I think what you're thinking of is specifically the `react-redux` library which gave a nice abstraction to the old & clunky React context API. The new context API was released with React 16.3 (which came out March of this year).

Reading about the architecture of that chip (3 core, PowerPC) I am amazed at how smooth GTA V could run on it.

I've heard more and more about prettier, but I can't figure out how it's much different from eslint. What are the advantages?

Along with that, generators (redux-saga) are amazingly simple to test.

Our team had the same thoughts on react-router. I'd suggest checking out https://github.com/kriasoft/universal-router. It uses the HTML5 History Library (https://github.com/ReactTraining/history) for navigation.