Echo JS 0.11.0

Title of the video is "Ultimate Node.js Cheatsheet for beginners in hindi || 2021 Must watch - part #1", and it just plays music while showing a bunch of examples of nodejs code and stuff like references to global objects.

All stuff which should be in an actual non-video cheatsheet in order to have any meaning. :-|

Good to see you keep growing and exploring those boundaries!
/Ben

That's an interesting title which totally specifies what is being released. It's Strapi (https://strapi.io/).

There very much is - without having dug deeper, this doesn't look like a complete answer, but merely serves as an introduction on how to begin using it.

You should definately unregister your event listeners in componentWillUnmount. If you wanted to pursue this approach I would probably make a higher level component (or mixin) to declaretively and automatically handle the binding and unbinding of events, plus the glue to rxObservables.

Oh my - I skipped that one because I thought it would be yet another 'hey look - promises/generators/<random es6/7 feature>!' article.

Thanks for pointing me back to it.

I'm not involved in the fork, but was aware it might be underway. A lot of the core node.js contributers are involved in the fork, and it seems the fork has been bred out of a frustration with node.js's update cycle, and it's somewhat peculiar versioning scheme.

But I agree - if we start seeing forks appear everywhere, then this will only split the community. On the other hand, if we loose node.js contributors entirely due to frustrations with how joyent is handling it...

</random-thought-stream>

This 'issue' might clear up some of the thoughts behind the fork: https://github.com/iojs/io.js/issues/28

And their first 'official' meeting:
https://www.youtube.com/watch?v=Z1UlIJMS6qs

Care to elaborate? :-)

I love google's material design - but both the React and Angular implementations I've seen of it keep missing out on the accessibility.

Something as simple as tabbing and spacing your way through checkboxes is not doable in these implementations...

Though, besides from that it looks good! :-)

Yeah - it does feel like browserify follows the unix approach (do one thing, but do it well) and leaves the rest to plugins.

But that's not always a good thing - you now have to find plugins for all your more 'advanced' use-cases. And anyone picking up your work might have to grog your chosen plugins as well. But it is simple.

Personally I still haven't fully decided which to use yet - still in the testing phase.

My impression: it does more than vanilla browserify.

It also has the ability to specify async loading, and can pretty easily chunk up shared js files (such as vendor libs) into one file, while generating another specific js file for each entry-page/page.