interlocutor

https://github.com/wisercoder/uibuilder/blob/master/SimpleDe...

EDIT: Regarding the polyfill, now you are beginning to write your own little jQuery clone.

jQuery has many convenience features such as chaining, for example: item.addClass('selected').siblings().removeClass('selected'); and you don't have to check for nulls after each selection.

Many functions such as closest() and remove() have no equivalents in IE11, and other things such as replaceWith() and before() are not available even in Edge.

For simple sites it is easy enough to remove jQuery, but for more complex javascript applications, especially apps that have a lot of interactivity, removing jQuery will result in more code, or you will end up writing a lot of utility functions thereby creating your own little clone of jQuery.

Vanguard's user agreement says this:

Data security is, of course, a top priority. To mitigate computer virus attacks and other acts of cyberterrorism, We have implemented controls monitored by a dedicated team of information security specialists. We also maintain a network of redundant systems, off-site data storage, and off-site tape vaults to ensure that all source data are recoverable in a disaster.

Case in point: ETRADE. Just received an update to the customer agreement. The definition of “Force Majeure Event” (unforeseeable circumstances) was updated to include cybersecurity incidents. Also this: ETRADE ... makes no representation or warranty of any kind ... with respect to security.

https://docs.google.com/spreadsheets/d/1Ryu_-mVYxSdJbW8lmf1z...

https://mspoweruser.com/no-microsoft-is-not-rewriting-office...

Why so? Could you add some detail to this comment?

Yes, there is. See https://github.com/wisercoder/uibuilder

You can do better than template literals. You can use TSX, which gives you compile-time verification for tags and attributes, in addition to JavaScript expressions.

See: https://github.com/wisercoder/uibuilder

With TSX (which is JSX written using TypeScript, you get things like syntax coloring and indentation for tags, because HTML and JavaScript are both first-class citizens in TSX.

So employers can't ask job applicants, but they can still ask Equifax, right? Your current employer may be sharing your salary with Equifax. (There is no law preventing employers from doing so.) Equifax offers various services using the salary info shared by your employer. For more info see: https://www.theworknumber.com/

Compare that to .tsx templates (Typescript's version of JSX). All html as well embedded expressions are checked at compile time, and typos are caught at compile time.

Hiring managers that have this attitude are not the next Steve Jobs, that's for sure.

Steve Jobs specifically looked for the "multiplier factor" when hiring: In choosing key members of his team, he looks for the multiplier factor of excellence. Truly outstanding designers, engineers and managers, he says, are not just 10 percent, 20 percent or 30 percent better than merely very good ones, but 10 times better. Their contributions, he adds, are the raw material of “aha” products, which make users rethink their notions of, say, a music player or cellphone.

Source: http://www.nytimes.com/2010/01/31/weekinreview/31lohr.html

Here's one definition I found: http://www.urbandictionary.com/author.php?author=ChrisTTT

A computer programmer with such strong skills and so much specific experience that they are the equivalent of a rock star in the domain of software. Many people play guitar pretty well, but only a few become rock stars. These programmers can develop more software than 5 - 10 newly hired regular programmers because they know what needs to be done and how to do it. They also might set the architecture of the product that dozens will build upon.

What's wrong with that?

What percentage of business applications would benefit from this? My guess is, very few. Typical business applications fetch data from the backend and display it, let the user update the data and immediately send the updated data to the backend. There is no need for something to track "when, why and how your state was updated and what part of the application triggered the state update". I am not saying nobody needs that kind of capability. I am saying that few business applications do, and yet there is this notion that React and Redux go together and if you're going to use React it would be strange to not use Redux. Practically everyone who uses React also uses ReactRouter and Redux.

The end-result of this is that React, which by itself is a simple, elegant and useful technology, has been turned into an over-complicated mess by the community of developers, by gluing it with over-complicated add-on technologies.