romed

Vast majority of California’s forests are fossils. If you burn them they don’t grow back, you get something else. Climate change is reducing the length of the rainy season, worsening summer droughts, expanding the range of bark beetles, and moving snow lines uphill. Under these conditions our existing forests can survive but not become established.

You discuss this issue as if there is some steady-state solution that can be applied. This is not the case. The climate is in now in transition from one state to another, much warmer and drier state. Controlled burns are difficult or impossible to apply under such a transition, with the number of dead standing trees (hundreds of millions in California) and the unprecedented soil moisture levels and evaporative load.

People are discussing this event as if it were a “pole” servicing some house. The downed line that is suspected here is a high voltage transmission line serving a hydroelectric power station. It’s major infrastructure and there are only a handful of such lines in the state.

Market share.

Apple's cloud is already stored on Google's cloud. How do you figure it will work? Apple and Google cloud will somehow become mutually self-hosting?

Snap doesn't spend it all on what you are all discussing here, though. Even though it's wrapped up in Google Cloud marketing, Snap's main use seems to be of App Engine, a product that is clearly in the lead among comparable products, as opposed to things like GCS and GCE which are clearly behind S3 and AWS, respectively.

Snap also has a huge contract with AWS, for what it's worth. Other large customers like Apple also split their ticket between Amazon and Google.

The entire point of the system of record feature is that nobody is able to manually apply or remove the "sent" label.

First, note that a great many enterprise use cases are total nonsense. But still: people want to be able to put messages into gmail from random other systems and have the "sent" label be applied, so they can treat it as a system of record.

How this feature works is even documented. https://developers.google.com/gmail/api/guides/labels

This is a feature, not a bug, and it's required to get enterprise business.

Simple answer: Japan is up to their necks in money. Anybody can take a few billion off SoftBank.

I can imagine there are very solid reasons related to stalking that result in Uber wanting to make it hard to contact past riders or drivers in either direction.

"Tumble" always needs context.

JHC how much data is in this URL?

https://finance.yahoo.com/chart/FB#eyJpbnRlcnZhbCI6IndlZWsiL...

abseil targets c++11. Its modernity is arguable.

That is not a rumor. Google and Fiat announced the deal. Remember, the entire game for self-driving-car journalists is finding new and creative ways to ignore the fact that Waymo is obviously far ahead of everyone else. They ordered 62000 vans, but Cruise's big advantage is partnership with GM. Uber kills people while Waymo has been shuttling hundreds of people around Arizona for months, but keep writing about how it's a horse race.

https://www.freep.com/story/money/cars/chrysler/2018/05/31/w...

I can't believe you are being downvoted for this. It's absolutely correct and consistent with my point: a system that's abstractly superior but which cannot survive contact with humans is not a good one.

I've interviewed about 100 programmers who just passed their 366th day at Amazon and are looking to get the hell out. Further down the ladder their people are pissing in bottles and collecting food stamps. The only person at Amazon with "a good job" is Bezos himself.

The problem as usual is with the users not the system. If anyone in your building turns the valve on their radiator off (because their space is overheated) then the water will condense and when they open it again the entire system will hammer, forever, until the building engineer drains it. As for the air vents it seems that building supervisors just can’t resist painting them, which renders them inoperable. They should know better.

So in summary steam is wonderful as long as humans don’t get involved.

Many universities and other institutions like hospitals are steam heated because they have the steam anyway from their own combined-cycle power plants. I guess this is a legacy of universities having power before widespread electrification? In any case it’s very efficient. Steam can provide not just heating but also cooling and refrigeration. If you already have the technical staff to run your own power station then maintaining steam distribution should cause you any additional headaches.

The timers are in TCP not HTTP. TCP only ACKs every other packet. If the stream pauses after an odd number of packets, the sender has to just wait for the receiver to perform a delayed ACK, for which there is a timer on both sides. The sender infers that the last packet has been lost if the ACK doesn't arrive after a while. The sender has a thing called the retransmission timeout (RTO) and the receiver's delayed ACK timeout (ATO) sets a lower bound on the RTO. Modern TCP stacks have a thing called the tail loss probe that just sends a retransmit early (before the RTO) if the stream has stopped at an odd boundary. This is a bit of a hack. All of these things affect client-observed latency since obviously the client can't proceed until it gets the last packet. On mobile this is pretty important because mobile networks have massive packet loss.

Anyway, that's mobile. In the datacenter all of these timers are way too high, by several orders of magnitude. 1ms is an outrageously long RTO in a datacenter fabric but 200ms is the minimum RTO allowed by the TCP RFCs.

Yeah I’ve noticed a preference among the library authors for kicad-compatible releases. That’s fine with me. I consider it analogous to the situation between clang and GCC. All the compiler people are working on clang these days. But GCC is still the better compiler, through the sheer mass of accumulated contributions. Someday the new thing will surpass the old thing.

TCP has major issues in low-latency environments. It has too many timers and they are too coarse for 50us RTTs and 100gbps bandwidth. QUIC as a transport for gRPC can solve a lot of this. What we know for sure today is that Linux distributions, out of the box, are garbage for TCP in datacenters. You can tune some of it away, if you happen to know where the knobs are, but some things like microsecond packet time stamps you have to patch. Switching to a UDP transport means you don’t have to argue with Linux kernel maintainers in order to make progress.

People don’t really appreciate what a miracle the quick-turn electronics industry is. You can upload a Gerber file and get boards back in 24 hours. 2 layers, 4 layers, 6 layers whatever. Tiny little holes all over the board. Boards two feet square. If I order a huge box of stuff from Digi-key right now I’ll have it on my desk at 8am tomorrow. Or I can drop-ship it to the PCB place and get stuffed boards, inspected and reworked, in a couple days. It’s incredible, and all this has been up and running for at least 20 years.

KiCAD is not bad but I definitely file under the category of software for people who like screwing around with software. If you’re making boards in your kitchen then the free edition of Eagle will be more than satisfactory, and it comes with decades worth of user-contributed libraries and scripts.

San Francisco recently held a city council hearing on eliminating parking minimums city-wide. Houston has no parking requirements in its central business district. Mandatory parking is looking pretty dumb at this stage of the climate emergency.

That's one data point, but how does that relate to whether the law should force people to build parking garages in their homes?

"Open tracing" is a bit too opinionated by be universally useful. For example opentracing makes sampling decisions at the end of the span, not the beginning. Because of this you always pay the cost of span annotations even though the vast majority of spans are discarded. I think it's interesting that opentracing descends from the author of Dapper, and opencensus is from Google itself, and yet they've diverged on this and other details. Google of course just uses Dapper.

If you've got a kid in 4th grade, all national parks are free all year long.

That's just your pet definition of transaction. That is not universally accepted.

If nothing else this would be a fun and easy way to develop a driver from scratch for unfamiliar hardware, even if you intended to port the whole thing back to C in the end, after it was all figured out.

Privacy derangement syndrome is big now. People even question license plates.