When I looked at HL7 a few years back, it was standardized on in the most technical sense and was basically a big bag of hurt. Epic made a big chunk of their money just charging people to build interfaces over various PACS (and other) systems. Has that changed recently?
Based on discussions with my wife and her friends, that's a feature, not a bug. You can post beach pictures for example, and be relatively comfortable knowing that people can't (casually) zoom in.
On Epic's side at least, they are actually overloaded with engineers/applicants now, to the point that they removed their referral incentives because they have more people applying than they can deal with. They're perfectly happy if they lose a few percent of applicants if they avoid some false positive hires.
I really enjoyed my time there actually. There's a decent burnout rate for some teams and roles (especially for ones that travel a lot), but there are some groups there that do interesting work. I was one of their Security team leads for a year or so right before I left and had a lot of fun with it.
In the US, I know 0 users of WhatsApp (excluding work friends from other countries). It doesn't have nearly the market penetration of even something like GroupMe as far as I can tell.
Ran into this with Southwest's wifi this week. HSTS preloading makes it worse too. No dice with Google, Facebook, my website, etc. Just lots of error pages until I figured out what was going wrong.
From a position of total legal ignorance, I don't see a meaningful distinction. In both scenarios, you're recording an account of someone else's performance with enough fidelity for someone to know what's happening in the game. In the linked case, the issue seemed to be the the recorded content had no copyright, so I don't get why that's relevant? Very interested in a more detailed answer though :)
To be real, any time you visit any site you're running 3rd party code you didn't invite. NPM modules, random scripts from CDNs or stored off in a /libs directory, hardly any sites are built entirely on code hosted or written by the party running that site. Ads get a bad rap, but if you're running JS on the modern web it's not even the biggest culprit.
I really don't think that most JS programmers write code without declaring variables. Anyone using strict mode, ES6, or ESLint/JSLint/JSHint is already forced to declare variables appropriately.
Personally, I think the benefits of let are worth killing off var. I have honestly never seen an example where hoisting has been more clear than the alternative (declaring variables before they're used).
True, worded that poorly. The resolutions are always executed asynchronously, versus a callback approach where the code receiving the callback can inappropriately and unexpectedly choose to execute the callback synchronously.
Promises and callbacks have fundamentally different behavior. Promises are much more reliable (only executed a single time, always executed asynchronously vs possibly synchronously, etc.) and also have slightly different execution behavior in the event loop. People emphasize the syntax differences, but that's not the most useful thing about Promises imo. You Don't Know JS's async book has an excellent in-depth writeup on it.
Probably should be on v45 rather than the upper v4*s if you're not doing upgrades, since it's the extended support release and will receive security fixes. Although opting to not take updates because Firefox is taking a harder security stance going forward seems a bit self-destructive...