Yeah well the problem is that after a moderately prosperous person buys a car and a house out in the suburb, the act of having spent half a million dollars makes them believe that they are entitled to drive their car into the city and enjoy the commerce and culture that the city fosters, plus free parking and toll-free roads and subsidized gas. None of those are great! In my town this manifests as people who live just over the county line in unincorporated places who nevertheless feel entitled to participate in city deliberations over road design and parking policies.
Have you ... looked for evidence? I guess I always felt that it was self-evident that horizontal development costs way more in terms of roads, pipes, and wires, and at the same time raises almost nothing in terms of revenues. Residential-only development patterns never pay their own way. https://resources.environment.yale.edu/kotchen/pubs/COCS.pdf
I've looked a few times, and it quickly (at least to me) appeared to depend on what you bucket and where you can torture the data and make it confess.
Single buildings can cost as much as my entire "city" - one World Trade Center alone cost $4 billion.
An example of how you can bucket things is do you look at property tax, income tax (and if you do, is it where the "nexus of generation" is done, where the worker lives, where he works, where she's headquartered, etc). Around here basically none of what we would call "support" is paid for by property tax except schools (95% or so) and sewer (which is billed as a property "tax" though it's actually per connection/size).
In my town schools aren’t 95% of property taxes but they are the majority. Add emergency services, water (though that’s a separate bill), same for electricity. Less familiar with road and bridge maintenance. Assume some comes from the state and feds but at least some is local.
It's the part that flows through the feds that lets you get whatever answer you want - is a local bridge being 80% federal and state-funded the cities supporting the town? Or is that less than the income tax taken from the local town?
I agree and you’d have to do a lot of study and the answer is still probably it depends. Presumably nuking some distressed Midwest cities isn’t the answer, and a lot of these cities are somewhat spread out. But it’s hard to argue with they’re not bringing in tax revenue because in aggregate they’re pretty poor. Some luxury high rises to replace some of the many single-family homes is not going to help Detroit absent a big influx of jobs.
That's exactly the point. On big vertical building covers 1 acre of land but it has 80 acres of interior space. There's one honking water pipe in the basement that will never need to be replaced, instead of mile after mile of water pipes with leaky fittings every 50 feet.
Yeah, I agree. And if the surface is complex the Z features tend to obscure the complexity. I make maps like these for the cities of Berkeley and Oakland, but I use a color scale. And I usually aggregate at a larger granule than parcels. For e.g. https://observablehq.com/@jwb/2024-25-berkeley-property-tax-...
Even the most visible academic skeptic of Waymo (Phil Koopman) had to throw in the towel and admit that they've cleared every conceivable statistical hurdle to conclusively demonstrating that they are better than humans on injuries and airbag deployments. They have moved the goalposts to aesthetic arguments, for example: if it's so safe why does it sometimes do weird stuff? But to principled systems thinkers they have already shown what needed to be shown. It's safer.
Waymo's software has crossed multiple generations of sensors and vehicles over almost two decades. It does not seem to be tightly coupled to a particular device.
Not tightly coupled in obvious ways, but as I understand it they aren’t putting it on pickup trucks, convertibles, or anything toeing a boat etc. Their vehicles don’t have aftermarket suspension systems dramatically changing handling characteristics, or turned one into a stretched limo etc.
Which means the software can safely assume the vehicle will behave within a relatively narrow operating range.
I suppose owners will be motivated to have the thing do the driving (and so seek defeat devices and such), but at least the software can have "do nothing" as a safety mode if it manages to detect that the vehicle is not configured as expected.
And maybe the software can be designed to be coupled to a vehicle dynamics model that can be updated.
I don't think the vehicle performance really matters in the typical case. They're using like 20% of what the vehicle "can" do. They're probably hedging against the long tail of variance on the road somehow. Kinda like how private people can tow whatever the f they want with their pickups but in a work setting you need to keep it fairly stupid proof.
The new (as of now than a year ago) Waymo cars still had human safety drivers last I saw one (a month or two ago). I also don't see them taking customers. So they do seem to slow roll hardware rollouts.
I was just reading the QUIC multipath RFC. Didn't it come out literally yesterday? I guess it's common to have the implementation foreshadowing the RFC but it's jarring to see them back to back like this.
Many QUIC features get implemented while in draft stage as people iterate on the RFC's design (e.g., ACK Frequency[0] is currently on draft version 14 and I implemented support for it three years ago in quinn).
It’s common enough for groups to not consider the spec done until there is a decent bit of implementation experience (both because actual implementers tend to find interesting bugs in specs, and because many things are hard to measure without any implementation).
It’s pretty common for IETF drafts to be substantially complete well before they are finalized as RFCs. For example, supporting ML-KEM in TLS is still a draft, but there are already multiple large scale deployments of it since the technical aspects were nailed down a while ago
Even if they could I don't think they would. It is not in their interest. Their target selection does make sense from their point of view and it has been a restrained and capability constrained tit for tat.
For now all they seem to want is to have a financially viable future as an independent country, not as anybody's vassal, not as a country for other superpowers to play games for geopolitical reasons. Essentially to control their own destiny.
That was scuttled in 1953. Their civilian aircraft was shot down without apology. Saddam Hussein was foisted against them. They pulled through 8 years of wars that saw attacks with chemical weapons to which they lost several tens of thousands lives.
If they do not like the people who have messed with them, I cannot say that their feelings are unjustified.
1) It is not clear that the people of Iran actually want to blow up refineries in general right now, but living in an autocracy they don't have much of a choice.
2) Because there is a pretty big ocean between them and most American civilians/infrastructure (this also enabled past colonial powers to wage war very pretty cost effectively and at their convenience). I'd like to argue that the prospect of retribution on home soil is important to stem aggressive wars, but at least for medieval Europe this apparently did not work that well either.
They could stage a "Operation Spiderweb" inspired attack [0], but this seems highly unlikely with the current powerful surveillance state of the USA. I once read a wild theory that some Mexican cartels might be able to, since they have access to military hardware too nowadays.
Their post gives the impression that clearly AMD's branch prediction is better, because this one number is bigger. "Once more I am disappointed by Intel"
While it could very well be true that the AMD branch predictor is straight-up better, the data they provided is insufficient for that conclusion.
You may want to look up who Daniel Lemire is and the work he's done. What he's basically saying is "in the totality of things I've examined where Intel has come up short, this is another data point that is in line with their performance across the board". It's not "this one benchmark proves Intel sucks hurr hurr" - it's saying it's yet another data point supporting the perception that Intel is struggling against the competition.
reply