Echo JS 0.11.0

<~>

tracker1 comments

tracker1 81 days ago. link 0 point
I really don't like the "redux" name used in software that is so very different from redux, it doesn't even resemble the original anymore.  Call it something else already, and stop trying to piggyback on the success of another open source software.  Even if you are using redux underneath, this is emphatically *not* redux.

For what it's worth @angular-redux/store bugs me so much less than this.
tracker1 89 days ago. link 2 points
Decent primer on ES6 class syntax.  

1. Should use `TypeError` for the error message for an abstract class.

2. Missing class field declarations[0] (stage-3, but eminent).

    class Foo {
      bar = 'instance';
      baz = () => console.log(`I'm context bound to ${this.bar} yo!`);
    }

    var f = new Foo();
    f.baz();

Aside: Been working with InDesign's ExtendScript the past few weeks, it's been extremely painful.  Won't even shim to ES5 completely/properly, cheating just to get most of ES5, and ES6 modules with Webpack.

[0] https://github.com/tc39/proposal-class-fields
tracker1 89 days ago. link 1 point
Can't believe NodeAZ (Tempe/Phoenix, AZ, USA) isn't included...  :-/
tracker1 94 days ago. link 1 point
Unless you're going to test in many different browsers, I'd probably be more inclined to use Puppeteer or Chromeless and call it a day.
tracker1 98 days ago. link 1 point
The only thing I'm slightly disappointed in is that they didn't take the extra half a step to run the JSX version with React@16 proper.  It would have been an interesting contrast, and maybe surprising.  I would suspect that SSR + React's hydrate client-side might be the fastest to interactive of all of them.
tracker1 99 days ago. link 2 points
While interesting, it would be nice to see actual code.  Also, without more information on the specific code for both sides, and the testbed in place it's hard to really judge.

In the end, the numbers between the two weren't significant enough to inform a clear decision for most use cases.  Also, the whole point of microservices is to be able to scale out workloads.  Use what's best for a given task/microservice.  Duh.
tracker1 99 days ago. link 1 point
Yet another biased comparison between two fairly different frameworks.

In the end, look at both, and pick one based on your style.  IMHO, you'll be able to structure and organized larger projects with the React community paradigms be it Redux, other state management, or other flux-like options.  There are more alternatives to that side than anything.  It's the view portion, but I find redux + react + thunks + material-ui goes a *LONG* way to everything I need, and no box to keep me out.

I don't think that vue will scale as well, I think it's probably sufficient for most small-medium applications, and particularly in the case of smaller apps could be at an advantage in terms of complexity.

In any case, I'm also totally biased.  I'm tired of these X over Y.  It'd be nice to see something akin to an updated TodoMVC.
tracker1 99 days ago. link 1 point
Now following 3 more people on twitter (was already following the other 6)
tracker1 99 days ago. link 1 point
yet another boilerplate for webpack, no idea what it has to do with gulp, other than the motivation for creation was switching away from gulp.

Personally, I switched out of gulp, mostly relying on npm scripts and may create custom node scripts as needed (run from npm scripts), with shelljs and/or gulp modules/streams as needed.
tracker1 105 days ago. link 1 point
This looks like 1/5 of what an article with such a title should be.  There's a suggestion on how to create then rename a file, an editor (Sublime) and how to disable JS in chrome and IE.

1) as much as I really like Sublime Text 3, Atom and Visual Studio Code are might be other editors to advise people getting started to use.

2) Edge is the current MS browser, and should probably be the focus.

3) No coverage on actually getting a .js file after all that work to do anything.  If you're really going to take this from *that* basic of a level, you should probably include how to run the JS, and maybe even basic DOM interaction on init, as well as links to more resources.
[more]