hnov

Well the people who smoke fent off of a piece of foil aren't going to disappear so you have to put them somewhere. If you were to put them somewhere in Pac Heights where the residents actively work against public transit that'd displease them, so they go where the community is less civically engaged and less powerful, like next to public transit. In effect there's a feedback loop where the area next to BART is only going to get grimier and Pac Heights are going to get NIMBYer.

I think that really depends on what social circles you run in.

Isn't a doubly linked list basically incompatible with Rust's idea of memory ownership?

Ironically, the closure also made Market St more unpleasant (an already unpleasant experience before) to walk after dark.

For what protocol would this be advantageous over plain connection pooling?

This is true, on average having an edge will be faster, but it is not a panacea for latency, especially if you don't move non-trivial QPS from every region.

TLDR, adding an "edge" in front of your application incurs a connection setup cost which can be 2-3x RTT and is especially noticeable when you don't have a large QPS and are in a region like APAC where geographically close networks often have high latencies between each other. Both Argo and OriginShield seem to pool more aggressively, often going cross-datacenter to avoid hitting origin which sometimes saves this setup cost by coalescing onto warm connections, but only sometimes (notice how spiky their Argo graphs are, the p90 request is probably no faster than before).

While that lasts, you can't be charging a flat $200 in a world where the other players are charging 5-10¢/GB of egress.

It's more complicated than that though, you're interrupting a rape, in the victim's house, the perpetrator is their neighbor and they have a gun (so do you) so bloodshed is imminent if you get involved, you're the victim's significant other, but you don't care that much about them, you've been beefing with the perpetrator over who gets to store their car on the victim's lawn. The rape should stop and the perpetrator punished, but it's still not clear who gets to store their car on the victim's lawn (what you care about). You really want the victim to off their violent neighbor so you slip them an icepick and slip out the door.

This is how most high performance networked software is written, it’s mostly fine, when you’re running on the event loop, nothing else is.

Right, my camera even goes as far as offering in-body HDR, it's just not as good as what I get in my iPhone, especially when the scene has moving elements, the camera isn't on a tripod, etc. Phones can paper over a lot of things with "AI" which means that you can get a serviceable shot without trying, but it doesn't really correspond to reality and sometimes (especially with the moving elements case) has artifacting.

Phones outperform cameras in suboptimally lit shots. They also distort reality, hard. Good enough for IG but pretty different results otherwise.

I imagine they love the sqlite codebase but are not ecstatic about having to maintain a fork and would like to have sqlite upstream their changes such that they don't have to import patches in perpetuity. This is a valid frustration that most commonly happens with OSS that's built by a corporation and thrown over the wall. I think in this case the dig at the end of the README is a way to be like "look at those religious cult members, closed off from accepting contributions" which is a cheap shot but all's fair in politics. A lot of companies build on top Linux, PG and others and are able to reach consensus with the community.