A lot of REST APIs are just as hard to grok as GraphQL is as a whole. Companies often lack schemas and documentation, which GraphQL helps with out of the box.
It is not always obvious (e.g. strep throat is similar, but one or the other sicknesses may or may not need medicine) and doing things on a hunch is not how scientific fields should do things when there are simple tests.
Testing also provides safety for doctors against medical malpractice lawsuits.
I think some Google engineers published a free Meap book on service relatability and uptime guarantees. Seemingly counterintuitive, scheduling downtime, without other teams’ prior knowledge, encourages teams to handle outages properly and reduce single points of failure, among other things.
While you wouldn't want to leave "console.log" in your code in production, you can use them in function components just like a classes' render methods.
A better example (from the video "React Today and Tomorrow and 90% Cleaner React With Hooks" from October[1]) is something along the lines of updating document.title = `${some} Page` or possibly calling an API.
React has also been using classes for a long time (although the trend is to move away from them for performance and simplicity reasons). There is also a huge upward trend of people using TypeScript with React. Personally, after using TypeScript & Angular at work, I've preferred switching to TypeScript when using React in personal projects.
My main gripe with Angular (vs. React) has been the lack of first class support for patterns (higher order components) that have been a boon for React. It does look like Angular will have more 1st class support with Ivy[1], however, higher order components are so simple with React (and even better with TS/React).
I use Chrome on iOS because I find Mobile Safari’s UI to be total poop.
There was some funky scrolling on this article I noticed on my phone which is not present on most websites/websites viewed through Safari backed mobile browsers.
That’s a good point. It was much harder to find interesting stuff to read back in the day. I had my Google Reader with a bunch of blogs, but that ended up being pretty noisy and they took it away. You had to do the searching yourself and be your own data curator, or have a network of other friends pitching in content to check out (eg. forums, Maybe digg?)
It’s locked in a somewhat growing, walled garden, yes, but Medium is now basically the Google Reader for a lot of people. Those people don’t care about logins if they can get a good read every now and then. And, when Medium goes to crap, some other platform will pop up with no ads (for a while :) ) and lure us all over there.
“Someone who isn’t me”, a term used when discussing something (usually illegal) the poster did or has experience with, but is using this term to hide that fact.
There was a class action lawsuit against them (LinkedIn Lost it, iirc) for what they did. I believe they would try to connect you with any of your email contacts if you logged in with OAuth.
Correct. I mistakenly said author, and was referring dalbasal’s comment.
My point was that people (on both sides of this issue) do mistake fact checking with agenda when it comes to religion because of the polarizing nature of the topic.