Why would it be a pain? Hooking onChange or onBlur or onSubmit, depending on the type of input, works like a charm, and covers whatever you need to validate. There's also some great UI component libraries available if you don't feel like writing your own.

F keys gone missing are okay with me, because, as you say, you can configure touchbar to have those. However, I want feedback on ESC key. Its common, its important, I sure as hell dont want to search it when I need it. Seriously, if they made everything as is, but with ESC in its place, it would be perfect.

Why is this not a multiselect poll? All 3 for me.

ItemProviderTransformer would be my practice. Similar with formatters or helpers or what have you.

I use it, and hate the fact that I use it. There are plenty of great publishers that deserve to get their work rewarded. Whitelisting is the only option I guess.

Since you want subjective view instead of facts: I see Ruby jobs all the time, though always by the same handful of companies. I see Python jobs all the time, though its always some minor sets of components/services written in it. I see Javascript jobs all the time. Hell, all those Ruby/Python companies also hire Javascript developers. Bottom line, you can find work in any of those languages easily. Though, from my (very subjective) perspective, Ruby isn't as attractive as it once was.

Lately .map in ES6. arr .map ( callback [, thisArg] )