And turns out the patterns and metaphor in this book can be co opted. Without belief in the supernatural, or submission to human authority structures. Though still receiving and giving the same benefits.
Love isn't owned by a king, it's already built in, inherent to all of us.
I suspect the e-scooters left around town (Lime, Bird, etc) are massive Bluetooth / LoRa dragnets. You pay them to increase coverage or visibility to social hot spots.
There is a startup (in Stuttgart i believe?) that adds camera ms to these scooters.. this is 100% illegal (and I think the ccc is filing lawsuits?). Some of the earlier Tier model scooters even had a dedicated space for a camera in their head tubes.
The net/http library is the caller in this case,
so that would be consistent with the rule that callers
should start goroutines.
Request handlers are a bit of a special case too, in that
they are a framework for dispatching tasks to be worked on;
what is main() for a command line program is the request
handler for a webserver. It seems fair that there is some
concurrency coordination happening at the top level.
Yeah, but it doesn't spin up a thousand for every request. And it doesn't require you to start them. It starts them under the covers as part of the API.
The article says almost exactly the opposite, and I agree.
Your API should present all of the things it does as synchronous functions/methods. If callers want to run them asynchronously, they can easily provide their own goroutine to do so, including whatever lifecycle management makes sense for them.
The concrete example was
// Do this
func (t *type) Run(ctx context.Context) { ... }
// Not this
func (t *type) Start() { ... }
func (t *type) Cancel() { ... }
This is generally good advice which stops a whole class of extremely common and very tricky to debug orchestration bugs outright.
Funny thing: in the last couple years I've seen way more back buttons broken because of backend idiossincrasias than anything else.
It is super common to see "Don't use your back button" messages after placing orders on e-commerce websites.
On the other hand, most frontend developers writing SPAs just use react-router or something like that (instead of reinventing the wheel) and it just works.
Yet there was a post about how specifically to do that on dev.to because their users couldn't tell their modal was a modal, and the solution they came up with was to hijack the back button.
Phone applications and their data are so abstracted these days, it would be difficult for even an IT expert to differentiate between cloud and local data if search takes place using the device itself (which I assume is what happens). If they connect the phone via USB and browse the contents with a workstation, that might be a different story.
Some apps won't let you access any of your content without authenticating with their servers. So even if it's local content, not having an internet connection would deny access. I can envision CBP saying they need to crack your phone to get to the local stuff.
I was thinking the same thing - for purposes of making a record of the evidence and to ensure some forensic integrity (as well as only obtaining local data) a USB connection is the best approach.
FWIW, my laptop and phone were searched going into Canada and there was no special technology used - the officer just made me unlock them and hand them back to him.
Apple should add many QA steps filtering out the vast majority of bad parts. First there would be incoming QA on any received shipments. And any well run assembly line contains many check steps to make sure the unit has good constituent parts. This way you don't burn good parts farther down the line on a unit that was never going to pass. Then there is out going inspection and burn in testing.
All that testing increases overall quality and value.
In theory that's possible true but in practice on an iPhone I highly doubt a DIY can do "the exact same thing". For one there are important ports we can't access, like JTAG testing the SOC. And there is a whole other factory OS which we have no idea what it does and why.
Bottom line: We're all in a prison, and shit sandwiches are for dinner. I'll take the one with 90% less shit until (hopefully someday) we're all released from the prison that is American democracy.
Agree 100%. I think that the city of New York has no business putting limitations on how a property (that you own) can be used and leased. If you have a community/association that's making those rules, fine... that's fair. It's fair because you agree to their terms prior to purchasing the property. If you rent a property and the lease explicitly disallows subletting, fine. That's fair too. Rules and laws should be granular, specific to their locality, rather than vast sweeping blankets.
I'm also in favor of zoning for residential and business, that makes sense. But there's a big difference between someone operating a high foot-traffic business out of their home, and seeing an occasional stranger walk into a residence every other day or so.
If there are no specific rules that a localized community has agreed on, then Airbnb should be fair game. Why should the municipal government make the rules?
Love isn't owned by a king, it's already built in, inherent to all of us.
reply