Echo JS 0.11.0

<~>

tracker1 comments

tracker1 2055 days ago. link 2 points
IMHO, this is emphatically *NOT* the most scalable app architecture... imo, feature oriented structures work far better. A given feature may have child features, may have action creators, reducers, components, data access requests, etc, etc.  

Nested, mirrored trees organized by type is much harder to work with in practice as your related items are spread across several directories reducing the usefulness of having a directory tree for your files to begin with.

As to the mention of Axios... just wrap fetch for your needs directly.
tracker1 2057 days ago. link 1 point
If you're going to call out generators, should add async and async generators.
[comment deleted]
tracker1 2062 days ago. link 3 points
*REALLY FUCKING SLEAZY*

This was a re-upload of content originally from 2 years ago in JSConf EU 2018.  I changed the link to the original content.

About half of erisanakorede's posts have been removed as posted, Hence the Youtube discussion a couple days ago.  Next spammy/scammy thing the person posts, deleting the user (which unfortunately removes useful posts, but unsure how much are even original content after this).
tracker1 2062 days ago. link 1 point
I really like parcel, in many ways for the same reasons I like jest.  Trying to wire it all up yourself is *so* much effort, that I'm willing to spend a couple seconds on initial builds to account for it.

Similarly, Jest does such a good job at wiring up coverage, which is really a pain with say mocha.

I't a bit more pragmatic, and I still have to do some leg work.  I'll probably start using v2 in the next few months.  I tried an early beta and had some issues with it.
tracker1 2062 days ago. link 1 point
Missing generator functions... async generators are really cool as well, combined with for-await.
tracker1 2062 days ago. link 1 point
Interresting, though for something like this, that's embedding in another application instead of being the application, I'd probably reach for preact or hyper as another JSX transform option, which will be much lighter.  You can even swap in prod vs dev builds for testing.  React adds a lot of tooling and niceties that come with a ton of overhead.

You're looking at probably a 80k deliverable for the example out of the box, vs under 5k using hyper+jsx or preact.

I like React.  This just is a case where using something smaller/lighter but being very similar in practice would be better.

1. https://github.com/lukejacksonn/hyperapp-wiki/blob/master/docs/jsx.md
2. https://github.com/preactjs/preact
3. https://github.com/kenoxa/svelte-jsx
tracker1 2062 days ago. link 1 point
Interesting. Would definitely reach for Vue when extending mostly static content for more dynamic components at this point, where I might have used jQuery a decade ago.  I still prefer React + Redux + Material-UI for apps though.
tracker1 2063 days ago. link 1 point
Seems like the general sentiment is to keep them.  I often don't feel like sitting through the videos, so will probably just remove only if there's multiple downvotes or "this is spam" type comments on them.

Thanks for the feedback.
[more]