Same. I've personally never had issues with any auth packages, granted I've never used auth0. Personally, they all seem quite similar, especially in the react world.
Anything that can help me utilize oauth standards is fine to me.
IDK, they sound like they overflow the "maximum code" counter and land up straight in the literate programming land. I wonder how far you could go writing your whole program as doctests spliced between commentary.
The odds of all services rm -rf / at the same time are pretty small to be honest. The point is to have your work in multiple places, such that you're not reliant on a single service.
I've started my nerves journey w/ my (older) raspberry pi 3.
It's my first time working on anything IoT, but I have to say how easy it was to start. Currently have a few sensors attached (is this the proper term?), and I was amazed at how easily you can update the firmware w/ mix upload or just burning it.
If you want to create your own design systems / UI components and want to have a simple place to show that without any actual apps running ( or as some have mentioned, without any data - related logic ), Storybook makes this easy and clean. You can build it right off from your actual application.
The company I work for uses it for frontend devs (who are mostly freelance) to understand the feel of the UI designs and how the components should be built/used.
I'm less worried about how large corps will use my info in the long run vs how myself should develop and learn over time. 'Productivity vs learning and in my own way' was the way I was looking at it. I suppose they aren't mutually exclusive though!
Anything that can help me utilize oauth standards is fine to me.