Echo JS 0.11.0

<~>

tracker1 comments

tracker1 958 days ago. link 1 point
Interesting... I starred it for later review.  Definitely looks useful, and will probably take a review/audit in the near future.
tracker1 966 days ago. link 2 points
I'm guessing GPT, or otherwise replicating an existing tutorial or repository that is using this.
tracker1 966 days ago. link 1 point
If using service workers, make sure to setup to self-update... this can get kind of borked if you don't.
tracker1 982 days ago. link 1 point
Not sure if this is cloned/duplicate content, but the sample code formatting is completely borked, whitespace is missing. Beyond this, the API itself isn't really detailed well and there is missing context for supported browsers [1]. Which does indeed seem to be well supported.

Links to the MozDev API docs might help as well. [2][3]

    1. https://caniuse.com/payment-request
    2. https://developer.mozilla.org/en-US/docs/Web/API/PaymentRequest
    3. https://developer.mozilla.org/en-US/docs/Web/API/PaymentResponse
tracker1 985 days ago. link 1 point
Interesting... though unsure about potential pitfalls or costs in the future.  I tend to be extra leery if I don't see clear pricing, including anything related to distribution costs/fees from something that isn't open source.

Not against commercial efforts at all, and this definitely seems cool, just need more on licensing costs and plans for monetization before I would look deeper.
tracker1 987 days ago. link 1 point
I tend to call it delay...

    const delay = (ms) => new Promise(r => setTimeout(r, ms));
    ...
    await delay(1000); // wait a second
tracker1 987 days ago. link 1 point
Looks to be using a proxy with bound hooks for use as a state store.  Interesting and kinda cool.
tracker1 993 days ago. link 3 points
Just saw this on HN, and figured I'd share here.  Definitely interesting, with a pretty clean take.  Similar to other frameworks, not sure how well a more unified state (like redux) might work with it.
[more]