Echo JS 0.11.0

<~>
tracker1 2132 days ago. link 1 point ▲ ▼
No code sample for actually using the suggested (behind a flag) feature, but one for a higher overhead approach?

Frankly, I'm getting sick of the constant low value posts from logrocket.

Replies

gimenete 2132 days ago. link 2 points ▲ ▼
Hi, I'm the author of the article. I've added an exmaple about the worker_threads module to the article.

My idea on the article was to focus more on the "why" we need this new module, more than the "how" we can use it, because the docs already have examples and at the same time is experimental, so it is subject to change and the example in the future could not work. But you are right, an example was needed.

I hope you enjoy it. Thanks for the feedback.
tracker1 2132 days ago. link 1 point ▲ ▼
Sorry for the excessively gruff response (wrote more in my response to your coworker).
efunction 2132 days ago. link 2 points ▲ ▼
Hey, Michael. I'm Brian. I edit Logrocket's blog. 

While I'm not psyched to hear that you think our stuff is "low value", I do think your point about showing the suggested feature is more than fair. It's feedback we've received elsewhere too - I've asked the author to update the article.

I'm completely open to hearing about ways to improve. You can either talk to me here or via email (brian@logrocket).
tracker1 2132 days ago. link 1 point ▲ ▼
I apologize for the comment, I just happen to notice a lot of entries, and looking back at your blog, most articles are much more flushed out.  I try to read pretty much all articles on EchoJS, and most of the top 100 on hackernews every day and don't always keep all the sites correct in my mind.

I also tend to be much more critical of blog sites/entries that have relatively large portions of marketing blurbs attached; such as a lot of the Auth0 blogs that where at least half seemed like thin examples of using their service.  I'm also very critical when there's an opportunity to dive deeper into a more complex topic such as not only why we need workers, but also how we use workers.  Understanding that it's a work in progress feature.  The specific article in addition to an example for the new feature would have been to cover the browser version and how they compare and possibly an abstraction for using the same worker code for both.

Contrast this with the recent CSS Houdini article which was much more flushed out and included a simple example of how to use the new APIs.  Only critique there might have been to embed a working example (with a note of which browser(s) are supported).