> My original idea was going to involve a dependency on one of the bad words lists available on npm, but then I saw the API censors said words and thought, "Oh, that's easy."
You only need to per-visit when it's an insecure localhost endpoint or something similar IIRC. (or if you have an extension which clears that setting every page load)
My original idea was going to involve a dependency on one of the bad words lists available on npm, but then I saw the API censors said words and thought, "Oh, that's easy."
I talked about native mobile applications as well.
> Also, your glorious React didn't exist three years ago. Why should I expect it to be still developed three years from now? It doesn't sound like a very transferrable skill.
Facebook is dogfooding React in a way not seen in other libraries in use on the web. Sure, Google uses Angular here and there, but nowhere near to the extent that Facebook uses React -- both on the web and native mobile.
> Why not learn functional programming language for functional programming?
That's not really the point I was trying to make. JavaScript is already widely adopted on millions of devices. I can deploy functional JavaScript anywhere.
> And one has to go way, way out of his way to use this paradigm for real in JavaScript.
I mentioned libraries that encourage this paradigm. Including lodash-fp which makes a point of making everything in lodash auto-curried, iteratee-first, and data-last.
