Echo JS 0.11.0

<~>

tracker1 comments

tracker1 2927 days ago. link 2 points
For me the most common use cases for cloning are for logging, or a sanity check before crossing a wire (often for API responses and/or errors).  So true clones aren't needed, same for prototype chains.  What you do want to avoid is to have circular references plucked, and/or pull up error message/stack properties out of the prototype instance.

I created an npm module (safe-clone-deep), and helped with another (fclone).  I mostly just use fclone these days.
tracker1 2927 days ago. link 13 points
Happy to help.  This site has become a part of my daily routine for a few years now.  Thanks for all your hard work on this.  I totally understood why you had taken it down, and even more happy you've decided to bring it back up.
tracker1 2927 days ago. link 2 points
Really hope this gets flushed out and injected into an electron app.
tracker1 2939 days ago. link 1 point
Lost me here, "Angular tend to be much better than React Native because of the higher level of  code security and hacks resistance"
tracker1 2939 days ago. link 6 points
In the end, there is a cost to type checking.  The extent of that cost comes in time and effort to make sure all your interfaces are typed to get the benefit, in some cases this can be a lot of effort.  The risk from bugs saved by type checking isn't always offset of that effort.  In some cases it is a wash.  You do also gain some in refactoring efforts.

It's definitely a mixed bag.  There's also the fact that TS doesn't keep up with pending JS changes.  For long time if you wanted async functions, you needed TS + Babel, which is often painful to configure well, and then try to get webpack's benefits on top.

Personally, I wish that TS was a babel preset, like flow is.  In fact, I really wish that flow would update to use the typescript definitions, which would be a better configuration pairing imho.
tracker1 2948 days ago. link 1 point
Shame about the https change killing all the jsbin embeds.
tracker1 2948 days ago. link 1 point
The article title is somewhat misleading... "ECMAScript Proposals That Didn't Make It In 2017" would be more accurate... realistically, most of these will likely make it by end of 2018 for whenever the ES2019 cutoff happens.
tracker1 2956 days ago. link 1 point
Cool article... I'm progressively irritated by what AngularJS and Angular 2+ have in the box.  I don't get why Angular2+ have half of what it does considering you're in the npm ecosystem, just use modules... such as http, just use fetch.
tracker1 2963 days ago. link 0 point
React is like regular Lego, mindstorm kits are optional... Angular is like a weird Duplo version of mindstorm, and may require a Dremel to get some parts to work with it.
[more]