I would probably structure this so differently that it's hard to even say
where the changes should be. I don't know the Electron API, so the
following is almost certainly wrong, but it should demonstrate the basic
ideas:
```
const promisify = require('some-promisify-function');
const
@michael, integration-level javascript rarely deals with blocking-code. its
mostly tedious-work debugging and “fixing” endless piles of async-io timeout
issues, without the help of a stack-trace :`( and the term “fixing” is
oftentimes euphemism for “rewriting the carefully architected backend
We got another round of insurmountably good feedback, so I revised the
presentation again and am back to writing spec text.
I will get the revised spectext out before finishing the revision of the
accompanying proposal doc, which is primarily background and explanation.
On Tue, Mar 13, 2018 at
I totally agree that Map (and Set) should have `.map`, `.filter` and a few
more (`.slice`, ..) methods, similarly to immutableJS. Since Maps and Sets
are ordered, it would make sense
example polyfill:
```js
class SortableMap {
constructor(data) {
this.m = new Map(Array.isArray(data) ? data :
4 matches
Mail list logo
