Echo JS 0.11.0

<~>

tracker1 comments

tracker1 1519 days ago. link 2 points
Arrays will get borked with this implementation.  See the fclone source for something more complete.
tracker1 1519 days ago. link 1 point
Worth noting that "classical" inheritance in JS is mostly syntax sugar over prototype based inheritance with all it's performance implications.
tracker1 1519 days ago. link 2 points
Math.random isn't a good random number generator, especially for smaller number variations.

Use window.crypto or import 'crypto' for node.
tracker1 1523 days ago. link 1 point
While this is a cool abstraction, I do think that React is here to stay for a very long time, and that JSX based component library options are also likely to stay around for a very long time.

While the DOM is relatively stable now, this wasn't always the case, and with the expansion of WASM libraries and tooling that will come in the next few years, it could get interesting. An abstraction like in TFA might be better served with a WASM targeted application management layer/framework.
tracker1 1523 days ago. link 2 points
It's a bit opinionated.  No test setup anywhere in sight.  Redux Saga chosen over say thunks.  As mentioned no Saga examples.  Organized by type, not feature.

Really doesn't add much over create-react-app imo.
tracker1 1523 days ago. link 1 point
Both of these components don't seem to have anything actually wired for click events, feels like half the example is missing and not in a way that makes things really understandable.
tracker1 1526 days ago. link 2 points
Would be nice if you used github pages to host an active version of this.
tracker1 1536 days ago. link 0 point
Why the hell did you just turn around and post this again literally 2 days after you already posted it?
tracker1 1538 days ago. link 0 point
TBH, it's just massive information overload to the point where it really loses value.  There's some inline bits as well as external links.
tracker1 1543 days ago. link 2 points
Yeah, diagnostics would be really beneficial... possibly something that can generate a bundle from the polyfills that get added.  Of course, would need to run across several browsers and aggregate the results.

Only including what you actually need, vs say the babel-env fills, that include everything missing for your target, even if you aren't using it.

Blocking requests can be seriously nasty in practice though... I had to use them for SCORM implementations at one point.  And if you have a spotty connection as a user (think mobile) it can/will get particularly bad.
[more]