Saying gRPC hides the internals is a joke. You’ll get internals all right, when you’re blasting debug logging trying to figure out what the f is going on causing 1/10 requests to fail and fine tuning 10-20 different poorly named and timeout / retry settings.
Hours lost fighting with maven plugins. Hours lost debugging weird deadline exceeded. Hours lost with LBs that don’t like the esoteric http2. Firewall pain meaning we had to use Standard api anyway. Crappy docs. Hours lost trying to get error messages that don’t suck into observability.
I wish I’d never heard of it.
I like a lot of things about it and used it extensively instead of the inferior REST alternative, but I recommend to be aware of the limitations/nuisances. Not all issues will be simply solved looking at stackoverflow.
Did they improve the initial steps to get up and running too?
(I remember it took hours to clone all the subprojects and most of the times something failed along the way, even worse than downloading the Android sources)
Explores the consequences of consciousness being just a pattern. Would it continue if the pattern is paused? Seems yes, since we survive being unconscious. So we move in space and time, but still consciousness feels continuous.
What if you pause it, destroy it, recreate it somewhere else. Would it not continue then as well (the classic teleporter question). But it doesn't stop here.
What if you destroy it, but it just happens to continue somewhere else? Then it should continue there as well. So if you think that teleportation would not mean death, then you kind of have to accept that if anywhere in the universe at any time the same pattern exists when you die, then you can't really die because you'll just continue on from there instead.
Not sure I accept it, but it's certainly mind-bending to think about!
Let me know what you guys think.
Note: God bless the Oscilloscope, essential for these projects.