I think "guy" is quite neutral, and also "dude", and *also* "man" in neutral contexts (i.e., not opposed to "woman"), but still this isn't about JavaScript.
How long until Node can actually and effectively replace a Java backend, though? And all of its business logic?
Talking about a complete JavaScript full stack, even in the business area.
[spam]
But I'd like to note:
> Compatible with the most important browsers available in the market: IE 5.5+, Firefox 1.0+, Mozilla 1.3+, Netscape 7+, Chrome.
Netscape is really the selling point for me. Yeah.
It's an odd situation here.
While React - the library for which Jest was conceived - is basically just a virtual DOM library and so it's very basic, lately the community is shifting from the highly customizable and pluggable standard of tools (like Gulp, PostCSS or Mocha's ecosystem) to more battery-included solutions (like webpack and Jest) that relieve developers the burden of choosing, setting up and maintaining a boatload of plugins.
At least that's what I feel about the web dev community right now.
Yes, but on a more practical side, it makes little difference: you copy that reference to work with the object it points to.
If you take PHP. instead, as long as they're arrays (for those who don't know the evil of PHP, they're the equivalent of *both* JavaScript's Array and Object instances), it makes *deep* copies of them, and you have to use the & operator to get refrences instead. (Class objects are always passed as in JavaScript instead - did I mention that PHP is evil?)