-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathindex.xml
1654 lines (1620 loc) · 265 KB
/
index.xml
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948
949
950
951
952
953
954
955
956
957
958
959
960
961
962
963
964
965
966
967
968
969
970
971
972
973
974
975
976
977
978
979
980
981
982
983
984
985
986
987
988
989
990
991
992
993
994
995
996
997
998
999
1000
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
<title>Ashton Kemerling</title>
<link>http://ashtonkemerling.com/</link>
<description>Recent content on Ashton Kemerling</description>
<generator>Hugo -- gohugo.io</generator>
<language>en-us</language>
<lastBuildDate>Sun, 23 Jul 2023 00:00:00 +0000</lastBuildDate>
<atom:link href="http://ashtonkemerling.com/index.xml" rel="self" type="application/rss+xml" />
<item>
<title>So, you don't like a web platform proposal, a response</title>
<link>http://ashtonkemerling.com/posts/so-you-dont-like-a-proposal-response/</link>
<pubDate>Sun, 23 Jul 2023 00:00:00 +0000</pubDate>
<guid>http://ashtonkemerling.com/posts/so-you-dont-like-a-proposal-response/</guid>
<description><h1 id="introduction">Introduction</h1>
<p>I regret to inform you that I am once again, mad on the internet.</p>
<p>There is a new Chromium proposal that&rsquo;s officially designed to cut out click fraud on the web by allowing the server to automatically inspect and validate the hardware, OS, and browser state of the client. Given Chrome&rsquo;s market dominance, it&rsquo;s expected that this feature would rapidly become an industry norm if released.</p>
<p>The community freaked out. A lot of people had concerns about how this capability might be eventually abused to restrict competitive browsers and tools used to block ads. To the authors' credit they did include a section about risks, but the technical details were too light to be persuasive in my opinion<sup id="fnref:1"><a href="#fn:1" class="footnote-ref" role="doc-noteref">1</a></sup>. Eventually Yoav, a high level Chromium contributor, stepped in to do crisis comms and it did not go well. As of this writing the repo is locked, always a sign things have gone from bad to worse<sup id="fnref:2"><a href="#fn:2" class="footnote-ref" role="doc-noteref">2</a></sup>.</p>
<p>Yoav decided to provide some public <a href="https://blog.yoav.ws/posts/web_platform_change_you_do_not_like/"target="_blank" rel="noopener noreferrer">feedback</a>
, and frankly it had me seeing a bit red. I think that this blog post was both counter productive to Yoav&rsquo;s goals, and presumes that the problem lies entirely with the way that the community interacts with Chromium project leaders, and does not even broach the possibility that the Chromium devs and the proposal authors might have opportunities to improve.</p>
<p>While I obviously have my complaints about the proposal itself, I want to focus on what a failure in community communication and crisis management this blog post was. If Yoav wanted cooler heads to prevail and to guide the discussion back towards what he sees as productive, this was not the blog post to write.</p>
<p>A bit more broader, this post seems to demonstrate a high handed attitude towards community feedback, which is worrying. I would implore Yoav and his peers to rethink how they interact with the community during these moments of crises, and reflect on whether or not the attitude he expresses how he wants to be seen by the community writ large.</p>
<h1 id="the-post">The Post</h1>
<h2 id="yoavs-introduction">Yoav&rsquo;s Introduction</h2>
<blockquote>
<p>You wake up one morning, scrolling the feeds while sipping your coffee, when all of the sudden you land on a post related to a web platform proposal that you really don&rsquo;t like. Worse, one that you believe would have significant negative consequences on the web if shipped?</p>
</blockquote>
<blockquote>
<p>At the same time, there are some pitfalls you may want to avoid when engaging in those discussions.</p>
</blockquote>
<p>If I may offer some rhetorical critique, the paternalistic tone here does not work. Yoav is not a neutral party in this discussion, he&rsquo;s chairing this proposal to guide it through public criticism and the review process. Taking a high handed approach explaining what tone they should use to persuade you to stop doing the thing that you’re doing is not convincing.</p>
<h2 id="its-just-a-proposal-we-swear">It’s just a proposal we swear</h2>
<blockquote>
<p>Often a proposal is just that - someone trying to solve a problem by proposing technical means to address it. Having a proposal sent out to public forums doesn&rsquo;t necessarily imply that the sender&rsquo;s employer is determined on pushing that proposal as is.</p>
</blockquote>
<p>Technically speaking, he&rsquo;s right. Creating a proposal does not at all imply that one&rsquo;s employer is intending to ram things through. But it&rsquo;s also not inconsistent with it either, so a wise person would be well suited to look at other evidence before jumping to conclusions.</p>
<p>But wait, why are we talking about employers at all here? Isn&rsquo;t Chromium open source? Who wrote this proposal anyways?</p>
<ul>
<li>Ben Wiser (Google)</li>
<li>Borbala Benko (Google)</li>
<li>Philipp Pfeiffenberger (Google)</li>
<li>Sergey Kataev (Google)</li>
</ul>
<p>So four Google employees wrote a proposal, a fifth employee is chairing<sup id="fnref:3"><a href="#fn:3" class="footnote-ref" role="doc-noteref">3</a></sup> it, and they intend to add it to Google&rsquo;s majority market share browser and the community is concerned about the interoperability and privacy implications of this proposal, including concerns that the authors have not responded to<sup id="fnref:4"><a href="#fn:4" class="footnote-ref" role="doc-noteref">4</a></sup>. This obviously isn&rsquo;t proof of conspiracy or malicious intent, but it&rsquo;s not hard to see why someone might think so. I don&rsquo;t think that dismissing people&rsquo;s concerns about it being driven by Google out of hand is going to convince anyone.</p>
<p>Saying something to the effect &ldquo;we weren&rsquo;t ordered by Google managers to do this&rdquo; is also to miss the point quite a bit. We have quite a bit of real world experience of how organizations can encourage employees to do unethical or outright illegal<sup id="fnref:5"><a href="#fn:5" class="footnote-ref" role="doc-noteref">5</a></sup> things without giving them explicit orders. Humans are social creatures, peer pressure and prevailing norms are much more effective on us than we&rsquo;d often like to admit. Constant pressure to improve company metrics and a culture that devalues the concerns of those outside of the company is quite a powerful combination.</p>
<blockquote>
<p>It also doesn&rsquo;t mean that the proposal is &ldquo;done&rdquo; and the proposal authors won&rsquo;t appreciate constructive suggestions for improvement. Different proposals may be in <a href="https://blog.chromium.org/2019/11/intent-to-explain-demystifying-blink.html#:~:text=Step%201%20%2D%20Initial%20research"target="_blank" rel="noopener noreferrer">different stages</a>
of their development, and early stage proposals are often extremely malleable.</p>
</blockquote>
<p>They aren’t actually malleable though, at least not in a substantive way. I asked Yoav by what process the proposal might not be modified, but abandoned entirely. The answer was “Presenting unmitigated risks that outweigh the benefits of the anti-abuse use cases, and that go beyond the status-quo of device fingerprinting could be one way of convincing e.g. the <a href="https://blog.chromium.org/2019/11/intent-to-explain-demystifying-blink.html#:~:text=What%E2%80%99s%20an%20%E2%80%9CAPI%20owner%E2%80%9D%3F"target="_blank" rel="noopener noreferrer">Blink API owners</a>
not to approve this proposal when it reaches an Intent to Ship stage”.</p>
<p>Again, you can swear up and down all you want that the proposal isn&rsquo;t final, but this sentence and the block quote are mutually incompatible in practice. Only if you provide &ldquo;unmitigated risks&rdquo; that outweigh the &ldquo;benefits&rdquo; of the use case<sup id="fnref:6"><a href="#fn:6" class="footnote-ref" role="doc-noteref">6</a></sup> after the code has been implemented, tested, shipped behind a feature flag, and beta tested by public users, only then do you get a chance that it might get rejected. The proposal might not be &ldquo;done&rdquo; in the most technical sense, but if you or the community thinks the proposal is fundamentally bad it&rsquo;s damn near a fait accompli.</p>
<p>Oh, and the final step is it&rsquo;s enabled if 3 of the 10 Blink API Owners approve. Seven work for Google, including Yoav. If I was going to design a process designed to look open normally while also tipping the scales so that controversial proposals from Google usually make it through, it would look exactly like this.</p>
<p>And the community <strong>knows</strong> this. People aren&rsquo;t dumb, especially since the process documents are public. Providing assurances that the community finds non-credible is a very bad strategy for calming things down.</p>
<h2 id="on-occam-and-his-razor-company">On Occam and his razor company</h2>
<blockquote>
<p>When thinking about a new proposal, it&rsquo;s often safe to assume that <a href="https://en.wikipedia.org/wiki/Occam%27s_razor"target="_blank" rel="noopener noreferrer">Occam&rsquo;s razor</a>
is applicable and the reason it is being proposed is that the team proposing it is trying to tackle the use cases the proposal handles. While the full set of organizational motivations behind supporting certain use cases may not always public<sup id="fnref:7"><a href="#fn:7" class="footnote-ref" role="doc-noteref">7</a></sup> (e.g. a new device type not yet announced, legal obligations, etc), the use cases themselves should give a clear enough picture of what is being solved.</p>
</blockquote>
<p>That&rsquo;s not how Occam&rsquo;s razor works<sup id="fnref:8"><a href="#fn:8" class="footnote-ref" role="doc-noteref">8</a></sup>. To be charitable I believe that Yoav was trying to reference the more general &ldquo;benefit of the doubt&rdquo;, where when something is unclear you assume good intent until proven otherwise.</p>
<p>And in every day life offering individuals<sup id="fnref:9"><a href="#fn:9" class="footnote-ref" role="doc-noteref">9</a></sup> the benefit of the doubt is certainly good advice. Most people mean well-ish most of the time, so assuming good intent is a good habit.</p>
<p>But the &ldquo;benefit of the doubt&rdquo; does not require that we ignore past experiences. If some hypothetical individual repeatedly lied to you, you would stop offering them the benefit of the doubt. That&rsquo;s just how human relationships work; you can invoke the benefit of the doubt as a good principle all you want, nothing will require (or make) anyone trust someone they see as fundamentally untrustworthy.</p>
<p>And as I&rsquo;ve written on this blog before, Google has spent a huge amount of its credibility with the public and the technical community itself. Obviously a lot of this centers around Google&rsquo;s troubled history with user privacy which is highly relevant in this context, but a lot of it comes down to Google just not being seen as keeping its word. Not only is this becoming a bit of a drag for some Google products<sup id="fnref:10"><a href="#fn:10" class="footnote-ref" role="doc-noteref">10</a></sup>, but it&rsquo;s relevant here. There are aspects<sup id="fnref:11"><a href="#fn:11" class="footnote-ref" role="doc-noteref">11</a></sup> of this proposal that depend on quite literally on trusting Google<sup id="fnref:12"><a href="#fn:12" class="footnote-ref" role="doc-noteref">12</a></sup> to do things like certify rival browsers <strong>and never ever stop doing that</strong>, with no mechanism in place to enforce continued good behavior.</p>
<p>I can certainly see how the authors might be able to convince themselves that they&rsquo;ll never ever break this, but from the outside this is equivalent to asking end users to trust that Google will never change its mind in a way that might bring anti-competitive benefits to Google itself. This <em>might</em> work with a company that has more user trust around this area, but it won&rsquo;t work with Google.</p>
<p>As a matter of practical public communication, there is nothing that Yoav (or any of the proposal writers) can do to instantly fix Google&rsquo;s trust issue. Trust is built slowly and destroyed quickly, and very few individuals in Google have enough power to meaningfully change this, and even those individuals will need to work for a very long time to repair the damage that is done. But for the time being, Yoav and his colleagues can do a couple of different things to make this go smoother.</p>
<ol>
<li>Do not appeal to the benefit of the doubt, or simply assert that no secret agenda exists. Those who don&rsquo;t trust Google will not believe you, those who are neutral will find it suspicious.</li>
<li>Tread gently around community concerns about interoperability, openness, and privacy. There&rsquo;s not much you can do to fix the credibility issue, but you can certainly make it worse by acting high handed or dismissive of community concerns.</li>
<li>Pre-prepare for push back on privacy and interoperability concerns
<ol>
<li>Very, very carefully locking out abuse potential in the mechanisms of the proposal. No &ldquo;we won&rsquo;t turn off holdback ever&rdquo; or &ldquo;we promise to always attest competitor browsers.</li>
<li>Work with people outside Google, ideally ones that don&rsquo;t depend on selling ads so that proposals don&rsquo;t look like they come from Google and Google alone.</li>
</ol>
</li>
</ol>
<h1 id="legal-stuff">Legal Stuff</h1>
<blockquote>
<p>The fastest way to get someone working for a large corporation to disengage from a discussion is by using legal or quasi-legal language. Such language will prevent them from replying to your claims without talking to their corporate legal counsel, which will probably mean they will <em>not</em> reply to your claims. If you want to have a productive exchange with the folks making the proposal, it&rsquo;s best to not pretend you&rsquo;re a lawyer. (and if you are one, may be best to pretend you&rsquo;re not)</p>
</blockquote>
<p>Two takeaways from this paragraph.</p>
<p>First, this is kind of giving the ball game away about this being a Google initiative, not one coincidentally written by Google employees. If Google employees working on an open source project are worried creating legal risk for Google the company and therefore said employees will not engage with discussions on the topic of legality<sup id="fnref:13"><a href="#fn:13" class="footnote-ref" role="doc-noteref">13</a></sup>, then perhaps the community is completely correct in viewing this as Google trying to force this through for their own benefit at the cost of everyone else.</p>
<p>Second, as a matter of tone policing &ldquo;don&rsquo;t point out that what we&rsquo;re doing might be a crime&rdquo; is unpersuasive. You are not obligated to take anyone&rsquo;s specific interpretation of the law as true, of course, but whether or not it violates the law in relevant jurisdictions is extremely relevant and on topic. You should either just drop the pretense of this not being a Google initiative and involve Google lawyers<sup id="fnref:14"><a href="#fn:14" class="footnote-ref" role="doc-noteref">14</a></sup>, or you should build a stronger firewall between Google the company and Chromium the project so that individual proposals cannot pose a legal risk to Google the company.</p>
<p>Personally, I&rsquo;d be privately thankful for the warning, being deposed sounds unpleasant, and have legal come up with a canned &ldquo;thanks for the feedback, I&rsquo;m running this past legal&rdquo; response. That or not work on proposals that create legal risk. Either or.</p>
<h1 id="lalalalala-im-not-listening">Lalalalala I’m not listening</h1>
<blockquote>
<p>In cases where controversial browser proposals (or lack of adoption for features folks want, which is a related, but different, subject), it&rsquo;s not uncommon to see issues with dozens or even hundreds of comments from presumably well-intentioned folks, trying to influence the team working on the feature to change their minds.</p>
</blockquote>
<blockquote>
<p>In the many years I&rsquo;ve been working on the web platform, I&rsquo;ve yet to see this work. Not even once.</p>
</blockquote>
<p>I&rsquo;m trying not to be snarky, but I am struggling how to interpret this as anything other than &ldquo;we do not listen to community feedback&rdquo;. Saying that you do not change your mind in the face of feedback as an individual is generally seen as a serious character flaw no matter how it&rsquo;s presented. If you&rsquo;ve never seen people in this project ever change their mind about a proposal’s goal is a sign that something is catastrophically wrong with the process and the culture of the project.</p>
<p>I&rsquo;m not saying that Chromium proposal writers need to change their mind every single time there&rsquo;s large push back, but it literally never working is a sign that something is very, very wrong.</p>
<blockquote>
<p>On the receiving end, this creates a deluge of emails that&rsquo;s very hard to sort out.</p>
</blockquote>
<p>I can understand that this is frustrating but it seems like incredibly small potatoes when you&rsquo;re discussing features that impact this many people. A lot of people are worried about their privacy, their freedoms, and maybe their careers. Complaining about how this fills your inbox comes across as more than a tiny bit tone deaf.</p>
<p>Let me say this as snark-free as I can<sup id="fnref:15"><a href="#fn:15" class="footnote-ref" role="doc-noteref">15</a></sup>; sometimes the consequence for power is more work. Nobody is forcing you to take such a prominent position at Google or Chromium or even on any given proposal. You volunteered for this, and you could easily stop doing it. Hell, you could probably keep your job at Google, with all the perks and compensation that includes. It&rsquo;s on you as someone with power and authority to learn how to deal with the pressure and noise of these moments, not on the rest of us to think about your inbox first.</p>
<blockquote>
<p>While some of those may be full of technical insights, it&rsquo;s very hard to find them in that pile and distinguish them from the other forms of commentary.</p>
</blockquote>
<p>I guess only technical insights matter?</p>
<blockquote>
<p>So while it may feel good to join a good old-fashioned internet pile-up, it&rsquo;s very unlikely to lead to the outcomes you actually want.</p>
</blockquote>
<p>Personally I think I’d take the large scale opprobrium of my peers as a sign I’m on the wrong path. This isn’t an internet pile on by random yahoos, but the expressed opinion of fellow engineers and IT professionals. Dismissing their outrage as a mere “internet pile on” is insulting.</p>
<p>Also, in the strongest of terms possible, <strong>do not denigrate your angered peers and community as merely &ldquo;trolls&rdquo;<sup id="fnref:16"><a href="#fn:16" class="footnote-ref" role="doc-noteref">16</a></sup> or as participating in a pile on</strong>. It&rsquo;s offensive, it never calms people down, and it can make you look worse in the process. Even related to your own goals, such comments are extremely likely to make the noise of feedback louder, and not quieter. I promise you that you can find ways to reference controversy and spirited<sup id="fnref:17"><a href="#fn:17" class="footnote-ref" role="doc-noteref">17</a></sup> discussion on certain issues without dismissing everyone as doing something fundamentally invalid.</p>
<h1 id="use-cases">Use Cases</h1>
<blockquote>
<p>In some cases, you may consider the use cases themselves to be ones you think shouldn&rsquo;t be supported on the web. If that&rsquo;s the case, if I&rsquo;m being honest, you&rsquo;re up for an uphill battle.</p>
</blockquote>
<p>If discussing whether or not the use case is soft off limits, then this is not an open process. Discussion about whether the problem needs to be solved at all should always be on the table<sup id="fnref:18"><a href="#fn:18" class="footnote-ref" role="doc-noteref">18</a></sup>. No honest comparison of benefits and costs can be honestly done if certain discussions about the proposed use case are framed as invalid or low utility.</p>
<p>Presuming that the use case is valid and discouraging any discussion on the matter is a pretty nifty way to get unpopular proposals through the process. And people on the Github absolutely noticed this as well.</p>
<blockquote>
<p>If the proposal contains risks in terms of <a href="https://docs.Google.com/document/d/1RC-pBBvsazYfCNNUSkPqAVpSpNJ96U8trhNkfV0v9fk/edit"target="_blank" rel="noopener noreferrer">compatibility</a>
, <a href="https://docs.Google.com/document/d/1romO1kHzpcwTwPsCzrkNWlh0bBXBwHfUsCt98-CNzkY/edit#heading=h.mxgkfxtgzxqs"target="_blank" rel="noopener noreferrer">interoperability</a>
, or any other risks to the open and safe nature of the web platform, that&rsquo;s something worthwhile pointing out.</p>
</blockquote>
<p>The proposal we’re discussing is a fundamental risk to the open and safe nature of the internet, as well as having extremely obvious compatibility risks. Many people pointed that out quite eloquently, and the authors didn’t respond and then locked the repo<sup id="fnref:19"><a href="#fn:19" class="footnote-ref" role="doc-noteref">19</a></sup>. While I&rsquo;m sure that Yoav didn&rsquo;t intend it this way, it does feel a bit gas-lighty to suggest that people provide the feedback that they did provide, that thus far has been ignored, all to a forum that has since been locked.</p>
<p>I mean, it’s good advice in general. But it tastes more than a bit bitter given the context. A single sentence along the lines of &ldquo;some people did provide high quality feedback about compatibility and interoperability risks, the proposal authors are getting to it I promise&rdquo; would have done wonders for this section.</p>
<blockquote>
<p>This should come without saying, but.. people are less likely to understand and internalize your constructive feedback when it&rsquo;s littered with distracting and unprofessional language.</p>
</blockquote>
<p>I certainly agree that some level of professionalism makes sense, as does banning people who behave way outside the acceptable bounds<sup id="fnref:20"><a href="#fn:20" class="footnote-ref" role="doc-noteref">20</a></sup><sup id="fnref:21"><a href="#fn:21" class="footnote-ref" role="doc-noteref">21</a></sup>. But in this discussion somehow &ldquo;professional conduct&rdquo; has somehow morphed into &ldquo;you cannot discuss if you feel mislead&rdquo;.</p>
<p>To be blunt, no definition of civility or professional conduct has ever required that someone accept what they believe to be misleading statements or harmful proposals without honest comment. It might impose limits on evidence and the way they bring up the issue, but there is no requirement to self censor.</p>
<p>“Everyone pushing this works for the same organization that has incentives misaligned against the end user, and has a history of both lying about privacy and abusing its control over chrome to erode privacy and bolster their profits. I do not believe promises that this feature will not be abused, and I think someone might be lying to us” is not unprofessional. You might not <em>like</em> it, but that’s a different matter altogether.</p>
<h1 id="conclusion">Conclusion</h1>
<blockquote>
<p>Obviously, the above doesn&rsquo;t guarantee that the next point of feedback you provide on a proposal would be accepted and integrated. But at the same time, I think these guidelines can increase your chances of being heard and impacting the outcome of the discussions you&rsquo;re involved in. And after all, that&rsquo;s the point of getting involved, right?</p>
</blockquote>
<p>As I said at the beginning, the entire framing of this article is that the community is Doing Engagement Wrong, and at no point does Yoav engage with the possibility that maybe people are angry because they feel not heard. Aside from the technical merits of the proposal itself, I think that this is an counter productive way to respond to controversy and a destructive way to run a community. I encourage Yoav and his peers to find a way to listen to the community as readily as he&rsquo;s willing to talk at the community.</p>
<section class="footnotes" role="doc-endnotes">
<hr>
<ol>
<li id="fn:1" role="doc-endnote">
<p>I might do a followup on this later, but I have my manager hat on right now. So it&rsquo;s time to think about people and process.&#160;<a href="#fnref:1" class="footnote-backref" role="doc-backlink">&#x21a9;&#xfe0e;</a></p>
</li>
<li id="fn:2" role="doc-endnote">
<p>&ldquo;For the weekend&rdquo;. I have never, ever seen locking a repository in this situation go well. Pruning non-constructive, abusive, or repetitive comments in these situations is a very fine art. Outright locking discussion, even temporarily, tends to piss people off and rarely results in cooler heads prevailing.&#160;<a href="#fnref:2" class="footnote-backref" role="doc-backlink">&#x21a9;&#xfe0e;</a></p>
</li>
<li id="fn:3" role="doc-endnote">
<p>Yoav isn&rsquo;t an author for this proposal, but he&rsquo;s &ldquo;chairing&rdquo; it. Which means he&rsquo;s basically helping it through the process and doing public comms. This is almost certainly a necessary role for a controversial proposal, but the chair has a decent amount of influence so his employer matters even though he&rsquo;s not an author. As we’ll see in a bit, he also is one of the final gate keepers for these types of changes. His opinion matters a lot.&#160;<a href="#fnref:3" class="footnote-backref" role="doc-backlink">&#x21a9;&#xfe0e;</a></p>
</li>
<li id="fn:4" role="doc-endnote">
<p>I’ll get into it in another post but this proposal is very thin on details, and does not provide convincing controls to potential sources of abuse. There is a good reason people are suspicious of this already heading into the prototype stage.&#160;<a href="#fnref:4" class="footnote-backref" role="doc-backlink">&#x21a9;&#xfe0e;</a></p>
</li>
<li id="fn:5" role="doc-endnote">
<p>This is basically how Wells Fargo got its employees to <a href="https://en.wikipedia.org/wiki/Wells_Fargo_cross-selling_scandal"target="_blank" rel="noopener noreferrer">defraud customers</a>
without executives having to tell people to go do fraud. This kind of stuff happens all the time.&#160;<a href="#fnref:5" class="footnote-backref" role="doc-backlink">&#x21a9;&#xfe0e;</a></p>
</li>
<li id="fn:6" role="doc-endnote">
<p>And we&rsquo;ll soon see, arguing about the use case is explicitly called out as pointless.&#160;<a href="#fnref:6" class="footnote-backref" role="doc-backlink">&#x21a9;&#xfe0e;</a></p>
</li>
<li id="fn:7" role="doc-endnote">
<p>This sentence makes me feel like I&rsquo;m taking <a href="https://www.youtube.com/watch?v=ilcRS5eUpwk"target="_blank" rel="noopener noreferrer">crazy pills</a>
. Doesn&rsquo;t this directly contradict an appeal to Occam&rsquo;s razor? Why even include this?&#160;<a href="#fnref:7" class="footnote-backref" role="doc-backlink">&#x21a9;&#xfe0e;</a></p>
</li>
<li id="fn:8" role="doc-endnote">
<p>Occam is often invoked as a counter argument to conspiracy. This only really works for baroque, complicated ones. &ldquo;We actually built rockets and went to the moon&rdquo; is simpler than &ldquo;NASA has run a decades long conspiracy with thousands of people in order to fake the moon langing and humble the Soviets a tiny bit in 1969&rdquo;. Sometimes hidden motives are simple though; &ldquo;the ad company is modifying their browser to make it easier to sell ads&rdquo; is a rather simple hypothetical scenario.&#160;<a href="#fnref:8" class="footnote-backref" role="doc-backlink">&#x21a9;&#xfe0e;</a></p>
</li>
<li id="fn:9" role="doc-endnote">
<p>I say individuals here deliberately. Over the years I&rsquo;ve come to the conclusion that it&rsquo;s much easier for large organizations to lie because responsibility and knowledge is diffused enough that nobody is truly responsible for an organizational lie. Therefore an organization is much more likely to be duplicitous than an individual is, at least in my experience.&#160;<a href="#fnref:9" class="footnote-backref" role="doc-backlink">&#x21a9;&#xfe0e;</a></p>
</li>
<li id="fn:10" role="doc-endnote">
<p>This is probably a large amount of what killed Stadia, as a lack of user trust around Google&rsquo;s commitment to the project became both a drag on adoption, and eventually a self fulfilling prophecy.&#160;<a href="#fnref:10" class="footnote-backref" role="doc-backlink">&#x21a9;&#xfe0e;</a></p>
</li>
<li id="fn:11" role="doc-endnote">
<p>Again, there are more details than this. I will get into that in another post.&#160;<a href="#fnref:11" class="footnote-backref" role="doc-backlink">&#x21a9;&#xfe0e;</a></p>
</li>
<li id="fn:12" role="doc-endnote">
<p><em>Technically</em> Google will not be the only one that can attest to a browser&rsquo;s validity. But of course they&rsquo;re going to be the default for a lot of websites, including their own properties. If Google stops attesting for a given browser, then enough of the web becomes off-limits to that browser to render it unusable.&#160;<a href="#fnref:12" class="footnote-backref" role="doc-backlink">&#x21a9;&#xfe0e;</a></p>
</li>
<li id="fn:13" role="doc-endnote">
<p>In an era where GDPR is a thing, avoiding discussing legality at all seems completely unfeasible. This stuff is going to come up at some point, even in open source projects.&#160;<a href="#fnref:13" class="footnote-backref" role="doc-backlink">&#x21a9;&#xfe0e;</a></p>
</li>
<li id="fn:14" role="doc-endnote">
<p>You should&rsquo;ve run this by legal already, actually. Even if you have no legal liability personally, being involved in major litigation is a bad experience.&#160;<a href="#fnref:14" class="footnote-backref" role="doc-backlink">&#x21a9;&#xfe0e;</a></p>
</li>
<li id="fn:15" role="doc-endnote">
<p>This paragraph went through a lot of rewrites.&#160;<a href="#fnref:15" class="footnote-backref" role="doc-backlink">&#x21a9;&#xfe0e;</a></p>
</li>
<li id="fn:16" role="doc-endnote">
<p>Even the trolls, which there certainly will be. Prune trollish stuff away with a careful hand, of course, but even implying that the discussion is full of trolls is dangerous territory.&#160;<a href="#fnref:16" class="footnote-backref" role="doc-backlink">&#x21a9;&#xfe0e;</a></p>
</li>
<li id="fn:17" role="doc-endnote">
<p>See? I did it just now!&#160;<a href="#fnref:17" class="footnote-backref" role="doc-backlink">&#x21a9;&#xfe0e;</a></p>
</li>
<li id="fn:18" role="doc-endnote">
<p>That quote from Jurassic Park became a meme for a reason.&#160;<a href="#fnref:18" class="footnote-backref" role="doc-backlink">&#x21a9;&#xfe0e;</a></p>
</li>
<li id="fn:19" role="doc-endnote">
<p>In all fairness, he wrote this before the repo was locked, and he was not the one who locked it. But he could acknowledge that some people did provide said feedback, just to be polite and fair.&#160;<a href="#fnref:19" class="footnote-backref" role="doc-backlink">&#x21a9;&#xfe0e;</a></p>
</li>
<li id="fn:20" role="doc-endnote">
<p>Again, a <em>very</em> light hand is required here. Go too far and it tends to turn the temperature of the discussion up, not down. Not many people like trolls, even ones they agree with temporarily, but feeling like legitimate discussion is being shut down is a sure fire way to get lots more people seeing red.&#160;<a href="#fnref:20" class="footnote-backref" role="doc-backlink">&#x21a9;&#xfe0e;</a></p>
</li>
<li id="fn:21" role="doc-endnote">
<p>Also, be even handed in moderation. As I write this some abusive comments <strong>supporting</strong> the proposal remain up. People have very fine tuned hypocrisy sensors in general, if they think you’re moderating dissent more than consent they will get angrier.&#160;<a href="#fnref:21" class="footnote-backref" role="doc-backlink">&#x21a9;&#xfe0e;</a></p>
</li>
</ol>
</section>
</description>
</item>
<item>
<title>Telemetry and Trust</title>
<link>http://ashtonkemerling.com/posts/go-telemetry/</link>
<pubDate>Sat, 25 Feb 2023 00:00:00 +0000</pubDate>
<guid>http://ashtonkemerling.com/posts/go-telemetry/</guid>
<description><p>I recently read an <a href="https://twi.github.io/blog/making-go-telemetry-opt-in-is-a-mistake.html"target="_blank" rel="noopener noreferrer">article</a>
about Go opt in tracking being a mistake. The author was very earnest about the pros of compiler tool chain telemetry, how it was very common among Google and Go&rsquo;s competitors, and how opt in tracking would skew the data set. Their general argument was that anonymized telemetry is extremely useful for compiler writers, and that shifting Go to opt in rather than opt out doesn&rsquo;t help user safety and reduces the ability of the Go team to correctly steer their important project</p>
<p>Reading the article I was struck by a feeling of &ldquo;I&rsquo;m confused
why you&rsquo;re confused&rdquo;<sup id="fnref:1"><a href="#fn:1" class="footnote-ref" role="doc-noteref">1</a></sup>. The author made a ton of great points, but to me they missed the main problem completely. The issue never was telemetry, the issue was Google<sup id="fnref:2"><a href="#fn:2" class="footnote-ref" role="doc-noteref">2</a></sup>. Very few people trust Google anymore<sup id="fnref:3"><a href="#fn:3" class="footnote-ref" role="doc-noteref">3</a></sup>, and therefore the problem was that the telemetry suggestion came from Google. Focusing on the pros and potential safety rails of an open telemetry system is not wrong per se, it&rsquo;s just completely orthogonal to what got everyone worked up in the first place.</p>
<p>Google as an organization has spent its credibility, both among the larger public and among engineers. It spent its credibility <a href="https://www.forbes.com/sites/zakdoffman/2021/03/20/stop-using-google-chrome-on-apple-iphone-12-pro-max-ipad-and-macbook-pro/?sh=2786a7444d08"target="_blank" rel="noopener noreferrer">misleading consumers</a>
about the privacy implications of its actions, it spent its credibility by carelessly <a href="https://killedbygoogle.com/"target="_blank" rel="noopener noreferrer">killing off</a>
services people loved, and it spent its credibility by <a href="https://steve-yegge.medium.com/dear-google-cloud-your-deprecation-policy-is-killing-you-ee7525dc05dc"target="_blank" rel="noopener noreferrer">regularly breaking</a>
non-Google developers stuff. And like many large organizations it has made the catastrophic mistake of assuming that its size, money, and market penetration means that its credibility does not matter. And now they&rsquo;re discovering exactly how wrong that assumption is.</p>
<p>In this specific case, google is discovering that low credibility makes anything involving public consent really hard. Easy things become difficult, possible things become almost impossible, and prophecies become <a href="https://techcrunch.com/2022/10/01/stadia-died-because-no-one-trusts-google/"target="_blank" rel="noopener noreferrer">self fulfilling</a>
. Even when the Go team goes way out of their way to demonstrate good intentions, people don&rsquo;t believe them. And of course they don&rsquo;t! It&rsquo;s not like we&rsquo;ve all seen Google sneak in privacy defeating &ldquo;features&rdquo; under the guise of performance or safety before. Why shouldn&rsquo;t people assume that this data collection proposal won&rsquo;t be abused?</p>
<p>No amount of promises, analysis, or poorly advised <a href="https://research.swtch.com/telemetry-opt-in"target="_blank" rel="noopener noreferrer">accusations of trolling</a>
<sup id="fnref:4"><a href="#fn:4" class="footnote-ref" role="doc-noteref">4</a></sup> is going to overcome an issue of people not trusting you. In fact it probably makes the problem worse, not better. The only solution for low credibility is to take the long, incremental, and unpleasant steps required to repair that credibility. Opt in telemetry is probably a good step in this direction, or it would have been if they&rsquo;d not been dragged kicking and screaming to it.</p>
<section class="footnotes" role="doc-endnotes">
<hr>
<ol>
<li id="fn:1" role="doc-endnote">
<p>I&rsquo;m not actually certain if OP is confused. But this is the short hand phrase I say when some extrenal problem is immediately obvious to me, and I&rsquo;m confused why someone else doesn&rsquo;t focus on same thing I do.&#160;<a href="#fnref:1" class="footnote-backref" role="doc-backlink">&#x21a9;&#xfe0e;</a></p>
</li>
<li id="fn:2" role="doc-endnote">
<p>I believe that the official line is that Google doesn&rsquo;t own Go, it just happens to employ everyone who is on the core team. I find this unpersuasive.&#160;<a href="#fnref:2" class="footnote-backref" role="doc-backlink">&#x21a9;&#xfe0e;</a></p>
</li>
<li id="fn:3" role="doc-endnote">
<p>A few years ago I would&rsquo;ve joked that the only people who trust Google work at Google. But after the layoffs and weird desk sharing mandates, I don&rsquo;t think many people at Google trust Google either.&#160;<a href="#fnref:3" class="footnote-backref" role="doc-backlink">&#x21a9;&#xfe0e;</a></p>
</li>
<li id="fn:4" role="doc-endnote">
<p>Seriously, don&rsquo;t call concerned end users trolls. It will never work out for you.&#160;<a href="#fnref:4" class="footnote-backref" role="doc-backlink">&#x21a9;&#xfe0e;</a></p>
</li>
</ol>
</section>
</description>
</item>
<item>
<title>Lets Talk About Trains</title>
<link>http://ashtonkemerling.com/posts/lets-talk-about-trains/</link>
<pubDate>Mon, 17 Oct 2022 00:00:00 +0000</pubDate>
<guid>http://ashtonkemerling.com/posts/lets-talk-about-trains/</guid>
<description><p>Last week<sup id="fnref:1"><a href="#fn:1" class="footnote-ref" role="doc-noteref">1</a></sup> Casey had a <a href="https://caseyhandmer.wordpress.com/2022/10/11/why-high-speed-rail-hasnt-caught-on/"target="_blank" rel="noopener noreferrer">blog about</a>
High Speed Rail (HSR), and it triggered my worst impulse: my need to argue on the Internet. Casey suggested that I write my own post rather than just being cranky in his comments, and while my initial instinct was to continue to be cranky, I must admit that he was right and I should be more contstructive.</p>
<p>The starting point for all of this discussion is the continued boondoggle of trying to create a HSR between San Francisco and Los Angeles. Just to get this out of the way up front, there is no way in hell I would ever consider defending how this project is being implemented. I think HSR has a lot of opportunity in America, but the CA project is spending way too much<sup id="fnref:2"><a href="#fn:2" class="footnote-ref" role="doc-noteref">2</a></sup> for way too little compared to our peers. America needs to have a real serious &ldquo;come to jesus&rdquo; moment about why it&rsquo;s so damned expensive to build important public goods. But how to fix that is beyond my capability.</p>
<p>At a very high level, Casey is making two broad statements about HSR. First, he&rsquo;s making an argument about the capabilities of HSR in terms of efficiency, cost, maintenance, throughput, and other factual claims about HSR. Second he is comparing HSR against its alternatives, namely roads and airports, in argument that the alternatives are superior places to spend limited social resources. Obviously the first set of arguments is used to bolster the second set of arguments. There are some colorable arguments in this piece, but there are also a lot of serious factual errors that undermine the overall point. I think once you replace all the factual errors, the net sum of evidence points to the exact opposite of what Casey argues.</p>
<p>The clearest and least verbose<sup id="fnref:3"><a href="#fn:3" class="footnote-ref" role="doc-noteref">3</a></sup> way to approach this is to group Casey&rsquo;s arguments into similar sections, so that I can provide counter arguments once rather than repeatedly. Therefore the pull quotes will not be in order from his post. Where reasonable, I will link to specific sources, with some exceptions for wikipedia when the source is obvious and I can&rsquo;t be bothered. I pulled a lot of the numbers for European HSR from the 2009 paper <a href="https://www.researchgate.net/publication/326159879_Economic_Analysis_of_High_Speed_Rail_in_Europe"target="_blank" rel="noopener noreferrer">Economic Analysis of High Speed Rail in Europe</a>
, and I will reference it repeatedly.</p>
<p>And finally, a few notes on methodology. I&rsquo;m going to do my level best to avoid letting Covid goose the numbers. Covid crushed transit numbers and budgets across the board and required direct federal bailouts for all kinds of industries. There was no way for any of these companies to avoid a bailout during a once in a century pandemic, so it&rsquo;s not fair to judge them by extraordinary circumstances. Where possible I will either use 2019 numbers, or 2021 if they&rsquo;ve rebounded to pre-pandemic levels. I will similarly be using 2020 inflation<sup id="fnref:4"><a href="#fn:4" class="footnote-ref" role="doc-noteref">4</a></sup> numbers, because the inflation in 2021 and 2022 was caused to a large degree by supply chain constraints. Exactly what percent is debatable, but I don&rsquo;t think that they tell us much about how construction costs might change.</p>
<h1 id="high-level-misconceptions">High Level Misconceptions</h1>
<h2 id="why-high-speed-rail-hasnt-caught-on">&ldquo;Why high speed rail hasn’t caught on&rdquo;</h2>
<p>The first and most obvious issue is the article&rsquo;s title. I normally give blog authors a lot of leeway for clickbait titles, because I am not at all above reproach in this area. That being said the rest of the article is relatively consistent with the headline, so lets be charitable and assume that the title is indicating that HSR adoption remains minimal due to fundamental issues with HSR.</p>
<p>This &hellip; doesn&rsquo;t seem very true? The list of <em>famous</em> HSR lines is small, most people probably can only name the &ldquo;Japanese bullet train&rdquo; or maybe TGV if they&rsquo;re a francophile, but there&rsquo;s a pretty decent list of HSR lines in operation that are unknown to foreigners. Until this article put a bee in my metaphorical bonnet, I had never heard of things like the Honam HSR Line, the HSR Madrid–Barcelona, the Banqiao–Zuoying line, or the Ankara–Konya high-speed railway to pick some random examples. And why should I? The goal of any train line ought to move people, not impress random jerks like me. The fact that a lot of these are obscure to non-locals seems like a mildly positive thing, I want HSR to be unremarkable and effective, not world famous. Boring infrastructure is reliable infrastructure.</p>
<p>Also, the list of countries with HSR is bigger than Casey implies. The size of this list creates problems for Casey&rsquo;s main argument that he does not acknowledge. If the list of countries was small and similar in nature, we could potentially find mitigating circumstances to explain why HSR works in country X and not anywhere else, but that&rsquo;s not the case. One might be inclined to say &ldquo;China has HSR because a communist country can ignore profit and make money losing public goods<sup id="fnref:5"><a href="#fn:5" class="footnote-ref" role="doc-noteref">5</a></sup>&rdquo;, but this seems to lack explanatory power for Germany and the UK. One might argue that rich countries like Germany and the UK can afford luxury goods because they are rich post-industrial powers, but then again Vietnam and Kazakhstan are planning HSR, and Japan built a lot of HSR when it was emphatically not rich and post-industrial. Perhaps the flat terrain of France and the temperate climate of Spain is why, but then again you have Japan right there, all full of mountains and seismically active as can be.</p>
<p>Ultimately one is left struggling to explain why so many countries are doing what Casey argues they ought not be doing. All I see left is the argument that a dozen countries with wildly dissimilar economics, cultural histories, and geographic challenges are all being irrational in exactly the same way, which seems to run afoul of Occam&rsquo;s Razor.</p>
<h2 id="what-is-hsr">What Is HSR?</h2>
<p>First off, what do even mean by &ldquo;High Speed Rail&rdquo;? Obviously speed seems to be part of it, so we&rsquo;ll need to decide how fast a train has to be going in order to be considered &ldquo;high speed&rdquo;. Casey seems to draw the line at 300kph here:</p>
<blockquote>
<p>Despite decades of development, only a handful of routes in Europe operate at anything like airplane-competitive speeds, which for all but the shortest routes, require &gt; 300 km/h or &gt; 185 mph.</p>
</blockquote>
<p>and here</p>
<blockquote>
<p>In general, the number of &gt;300 km/h HSR networks on Earth can be counted on one hand,</p>
</blockquote>
<p>While 300kph is certainly &ldquo;high speed&rdquo; this is actually a pretty idiosyncratic definition of HSR. The EU defines HSR (&ldquo;Category I&rdquo;<sup id="fnref:6"><a href="#fn:6" class="footnote-ref" role="doc-noteref">6</a></sup>) as rails that can hit at least 250kph on purpose built lines and 200kph on upgraded pre-existing lines. Demiridis &amp; Pyrgidis define HSR as having a maximum speed of exceeding 200kph and averaging over 150kph for the corridor that is being evaluated<sup id="fnref:7"><a href="#fn:7" class="footnote-ref" role="doc-noteref">7</a></sup>. These numbers are selected because these are the points where the rail precision requirements, air resistance, and pressure issues in tunnels begin to increase rapidly. Above 200kph track side signaling is no longer workable, and Positive Train Control or something equivalent becomes mandatory. Personally I think that setting the bar at 300kph and declaring HSR a failure because this is a small set of rails does not seem terribly charitable<sup id="fnref:8"><a href="#fn:8" class="footnote-ref" role="doc-noteref">8</a></sup>.</p>
<p>But lost in all this is the following question: why does defining HSR even matter to us? Personally I think that arguing about whether or not trains over 300kph are good or bad is putting the cart before the horse so to speak. In my opinion the goal should be to move the maximum number of people comfortably via rail for all of the reasons that even Casey acknowledges. Trains capable of exceeding 300kph and running on dedicated track is one of many tools available for achieving that goal. There will be times and places where dedicated track exceeding 300kph will be necessary for service to be competitive with alternatives. There will also be times and places where that speed is unnecessary or impossible. &ldquo;The list of places that are a good fit for 300kph or faster rail service is small and mostly built out&rdquo; seems like it might be stronger, but that&rsquo;s not the argument Casey is making.</p>
<h2 id="hsr-networks-and-convenience">HSR Networks and Convenience</h2>
<p>Right off the gate, Casey says a number things that I think are misleading about the design of a rail transport network and how end users might interact with it.</p>
<blockquote>
<p>Despite decades of development, only a handful of routes in Europe operate at anything like airplane-competitive speeds, which for all but the shortest routes, require &gt; 300 km/h or &gt; 185 mph.</p>
</blockquote>
<blockquote>
<p>The oft-stated goal time of 2 hours and 40 minutes [between Los Angeles and San Francisco] is both unachievably rapid with finite money and current technology, and also too slow to compete with aircraft</p>
</blockquote>
<blockquote>
<p>HSR is not a compelling option for generic high speed intercity transport.</p>
</blockquote>
<p>First of all, this drastically misstates end users revealed transit preferences. HSR does not need to match airline speeds in order to be competitive with airlines, because end consumers do not actually care about travel speed. Consumers care about <em>door to door</em> travel time, frequency, comfort, and cost. While airplanes do cruise at a much higher speed than HSR, they also spend a lot of time not at cruising speed. All the time spent getting to the airport<sup id="fnref:9"><a href="#fn:9" class="footnote-ref" role="doc-noteref">9</a></sup>, through security, finding the gate, boarding, taxiing, climbing to cruising altitude/speed, landing, getting baggage, and travelling from the airport count<sup id="fnref:10"><a href="#fn:10" class="footnote-ref" role="doc-noteref">10</a></sup>. Plus you have to include the indignities and discomfort of being shoved into a small seat and breathing <a href="https://www.camfil.com/en-us/insights/commercial-and-public-buildings/airplane-iaq"target="_blank" rel="noopener noreferrer">bad air</a>
. The overall outcome is that while not everyone in Europe takes HSR, the general <a href="https://www.travelstatsman.com/08082016/high-speed-rail-train-plane/"target="_blank" rel="noopener noreferrer">revealed preferences</a>
is that users take the train for shorter trips, with the break even point between HSR and flights for a given route at about 4.5 hours of train time.</p>
<p>Secondarily, the fact that HSR is a &ldquo;tiny and static&rdquo; portion of total rail network build outs does not reflect a fundamental flaw in HSR if it were true (but it&rsquo;s not true&hellip;). HSR is not necessarily a good fit for every single country and city, it&rsquo;s a tool that has to be evaluated in context. Lots of cities are too small or too close to justify HSR, and lots of countries have not been able to afford it. The list of cities that are a good demograhic fit for HSR in countries that can afford it has been a relatively stable set until recently, so it&rsquo;s not that surprising that the networks haven&rsquo;t grown.</p>
<p>Consider France. The TGV has 2800km worth of track directly connecting a pretty small number of cities directly. This might seem like a failure as an American, until you consider the demographics of France. France has a very different population distribution than America, with a huge percentage of the population living in or close to Paris. The Paris metropolitan area of Paris contains 14.6m of France&rsquo;s 67.9 million people, or over a fifth of the countries population. So the TGV obviously connects all the cities you&rsquo;ve heard of like Lyon, Nice, Marsailles, and Bordeaux, but also a bunch of tiny little towns that nobody outside the region has heard of. The TGV directly connects Avignon (pop 90,305), Arras (pop 40,830), Hazebrouck (pop 21,408) and Vendenheim (pop 5,971) to pick a few random ones. SNCF can and still is adding lines to improve the network, but they&rsquo;re well into diminishing returns when it comes to what population of France they&rsquo;re serving. In fact a lot of their planned lines actually leave France for Italy and Spain.</p>
<p>And finally, HSR is clearly not a compelling option for &ldquo;generic&rdquo; intercity transport, but that is an arbitrarily high bar to set. Very, very few people are recommending that we get rid of all airplanes for HSR. Instead people like me are instead arguing that HSR is a good fit for certain large population centers within certain distances of each other. There is no world in which people take HSR from LA to NYC, or LA to Montana. Instead the question is whether we should invest the money to create better or new HSR between major population centers in California and the Eastern seaboard.</p>
<h2 id="adoption">Adoption</h2>
<blockquote>
<p>In general, the number of &gt;300 km/h HSR networks on Earth can be counted on one hand, and the total track length is a minuscule and mostly static fraction of global rail network length, which itself is shrinking at a reasonably rapid pace.</p>
</blockquote>
<p>I mean, this is literally false. The number of HSR networks with routes faster than 300kph is six, which is more fingers than I have on either of my hands. This list includes China, France, Japan, Morocco (!!), South Korea, and Spain. If we widen our list to include routes that are exactly 300kph, this list expands to 14 including Germany, Italy, the UK, Turkey, Saudi Arabia, Taiwan, Belgium, and the Netherlands. Meeting the EU&rsquo;s definition brings in South Korea, Germany, Italy, Russia, Uzbekistan, Austria, and Switzerland for a total of 21. America just falls off this list with a top speed of 240kph<sup id="fnref:11"><a href="#fn:11" class="footnote-ref" role="doc-noteref">11</a></sup></p>
<p>The size of the network is also growing. China alone has added 40,000km of HSR to its network, so I would not call the track length &ldquo;mostly static&rdquo;. Morocco is also new, having added 323 km in the past four years. Networks under construction (not just in planning) expands the list to Canada, USA, India, Thailand, and Indonesia. This list excludes countries that already have HSR and are expanding their network, such as Japan&rsquo;s under construction 286km 505kph<sup id="fnref:12"><a href="#fn:12" class="footnote-ref" role="doc-noteref">12</a></sup> Chūō Shinkansen line. So not only is the network bigger than &ldquo;one hand&rdquo;, but it is emphatically growing.</p>
<p>And this is to be expected! A lot of countries have not historically had the economy, the technical base, and the urbanization to make it worth it. While my general position is that HSR is not expensive compared to the large, rich econonomies of the global North, there are a lot of countries that cannot afford it. As countries like Vietnam and India get richer, it is not surprising to see them begin planning or constructing large HSR networks that they might not have been able to afford a decade or two ago. Vietnam in particular is currently planning a $58B, 1,545km HSR network. Vietnam also went from a nominal GDP of $34B in 1997 to an expected GDP of $408B this year. The fact that they didn&rsquo;t have HSR last century and they&rsquo;re planning it now is indicative of nothing more than their economy.</p>
<h2 id="global-warming-and-transit">Global Warming and Transit</h2>
<h3 id="co2">CO2</h3>
<blockquote>
<p>Alternatively, synthetic aviation fuel is under development to make aircraft carbon neutral. Indeed, at Terraform Industries we think synthetic fuel will ultimately be even cheaper than current options, expanding access to the convenience, speed, and safety of air travel.</p>
</blockquote>
<p>First off, big conflict of interest here. Casey is a co-founder of Terraform Industries, so he is not a neutral party in this discussion, and he should have disclosed that. Given that Casey seems to believe that his company may be able to sell synthetic jet fuel, America shifting some of its transit from airplanes to HSR would have a negative impact on his company&rsquo;s potential future profits.</p>
<p>But even if synthetic jet fuel is cheaper than refined kerosene, and I genuinely doubt it ever will be, this will not be enough to make jet travel &ldquo;green&rdquo;. The exact numbers vary depending on whose model you trust, but a huge chunk of the warming effect from commercial aviation comes from gasses other than CO2. Various mixes of particulate matter, black carbon, nitrous oxides, and sulfer compounds from the fuel interact in the upper atmosphere in an insanely complicated to model way, and tend to have a cumulative warming effect. There is also a big difference in spreading CO2 at sea level vs. high up in the atmosphere, even if it&rsquo;s previously captured CO2 rather than new from the ground.</p>
<p>But the worst offender by far is water vapor. The contrails left visibly behind jets is created by water in the exhaust gases condensing in the atmosphere. While these gases are short lived, they do have a large warming effect for their lifetime. Per the <a href="https://www.eesi.org/papers/view/fact-sheet-the-growth-in-greenhouse-gas-emissions-from-commercial-aviation"target="_blank" rel="noopener noreferrer">EESI</a>
: &ldquo;The effect is so large today that it exceeds the total warming influence of all the CO2 emitted by aircraft since the beginning of powered flight.&rdquo; Synthetic fuels will do <em>nothing</em> to solve this. Water is an unavoidable by product of the hydrocarbon combustion process, and Terraform Laboratories making synthetic methane<sup id="fnref:13"><a href="#fn:13" class="footnote-ref" role="doc-noteref">13</a></sup><sup id="fnref:14"><a href="#fn:14" class="footnote-ref" role="doc-noteref">14</a></sup> probably reduces the warming effect of air travel by less than half. As we&rsquo;ll see, HSR generally reduces the energy consumption per passenger km by a factor of 3 or more<sup id="fnref:15"><a href="#fn:15" class="footnote-ref" role="doc-noteref">15</a></sup>. And that&rsquo;s before you consider the fact that it&rsquo;s using electricity, which can be powered by a variety of sources.</p>
<h3 id="concrete">Concrete</h3>
<blockquote>
<p>HSR grades cannot be built between nearly any city pair on Earth without moving a LOT of dirt and rock and pouring a LOT of (CO2-emitting) concrete</p>
</blockquote>
<p>What, and airports don&rsquo;t have a lot of concrete too? JFK airport has four runways totaling 44,900 feet in length, all are 200 feet wide and 18 inches thick for a total volume of 13,470,000 cubic feet. The Shinkansen trains seem to use the most concrete for HSR because they use slabs of concrete rather than concrete &ldquo;sleepers&rdquo; like in other countries. These slabs are 2200mm wide, 4900mm long, and 190mm thick. This gives us a total volume of 418 cubic meters per kilometer of track<sup id="fnref:16"><a href="#fn:16" class="footnote-ref" role="doc-noteref">16</a></sup>, or 14761.5 cubic feet per kilometer. So just the runway at JFK contains enough concrete to make 912km of Shinkansen, or about 1/3rd of the system&rsquo;s length. And that&rsquo;s before we consider the taxiway, terminal, parking lots at the terminal, maintenance facilities, etc.</p>
<p>And yes, stations also contain concrete, but train stations are much smaller than airports. The Atlanta airport terminal covers 130 acres, or 0.52 square kilometers. Tokyo station is 0.182 square kilometers in size. Oh and Tokyo station moves 500,000 people a day to Atlanta&rsquo;s 300,000. There&rsquo;s also random bridges and viaducts and what not, but there&rsquo;s really no way to slice this so that HSR is using more concrete than its alternatives<sup id="fnref:17"><a href="#fn:17" class="footnote-ref" role="doc-noteref">17</a></sup>:</p>
<h2 id="frequency-and-scale">Frequency and Scale</h2>
<blockquote>
<p>But rail has relatively narrow limits in terms of train size and frequency meaning that any route will be both congested at peak times and under-utilized for much of the rest.</p>
</blockquote>
<p>The statement about size and frequency is really not true. HSR shows a huge variation in train size both internationally and within the same system, often significantly more variation than a lot of airlines. Furthermore train frequency is also much more variable than is implied here.</p>
<p>First a note on sizing. Both airplanes and trains can be configured to make tradeoffs between seating capacity and seating price. This often says less about the fundamental capacities of the transport, and more about the market segment the operator fits in. Therefore I&rsquo;m going to try and represent the maximum ranges for models in use, to be fair. Exceptions will be made if configurations are available but are not purchased in practice.</p>
<p>I am also going to disregard historical vehicles. There is a lot of cool stuff that is no longer in use, like the Concorde, but they tell us nothing about vehicle tradeoffs today and going forward.</p>
<h3 id="aircraft-size">Aircraft Size</h3>
<p>Lets start with aircraft size. I am going to explicitly exclude private airplanes, which typically seat few people and don&rsquo;t really fit in a discussion of mass transport. This includes Cessna type general aviation craft, and private chartered jets like the Leerjet.</p>
<p>The absolute smallest commercial craft are going to be turboprops used by regional and commuter lines. There tend to be a lot fewer of these than their low purchase price would imply, and they&rsquo;re under a lot of pressure from narrow body jets, but they do exist so lets look at them.</p>
<ul>
<li>ATR 42
<ul>
<li>Seats 48</li>
<li>232 in airline service</li>
</ul>
</li>
<li>ATR 72
<ul>
<li>Seats 72</li>
<li>444 in service</li>
</ul>
</li>
<li>De Havilland Canada Dash 8 Q400
<ul>
<li>82-90 seats</li>
<li>508 in service</li>
</ul>
</li>
</ul>
<p>A step up from that are narrow body jets. These represent the bulk of commercial aviation both in terms of aircraft sales and passenger miles. This set includes the 737, which is basically eating up all of aviation now that it has the range to handle long range travel.</p>
<ul>
<li>A220
<ul>
<li>108-160 seats</li>
</ul>
</li>
<li>A300
<ul>
<li>228-361 seats</li>
</ul>
</li>
<li>A320
<ul>
<li>150-186 seats</li>
</ul>
</li>
<li>737
<ul>
<li>85-215 seats</li>
</ul>
</li>
</ul>
<p>And lastly we have the wide body jets. These are less common thanks to improvements to narrow body jet ranges and fuel economies, but they definitely exist and are in operation.</p>
<ul>
<li>747
<ul>
<li>467-605 seats</li>
</ul>
</li>
<li>777
<ul>
<li>301-550 seats</li>
</ul>
</li>
<li>A380
<ul>
<li>555-853* seats</li>
</ul>
</li>
</ul>
<p>There&rsquo;s an issue with that A380 number. As best as I can tell, nobody ever flew the A380 with the 853 seat configuration. The largest operator and the operator of the largest A380, Air Emirates, has a maximum seating of 615. Most operators of the A380 ran it with 400-500 odd passengers, presumably for economic reasons.</p>
<p>So that&rsquo;s the range we&rsquo;ve got, 48-615 seats if you include turboprops. Limiting yourself to jets you end up with 108 to 615 seats.</p>
<h3 id="train-size">Train Size</h3>
<p>Like airplanes HSR cars can be configured for a mix of seating types. Unlike HSR trains can be adjusted in length to change capacity with the same equipment. In practice most HSR routes purchase fixed trainsets with known capacities, but there is a trend towards more dynamically reconfigurable options, both in terms of train composition and train interiors. More on that in a moment.</p>
<p>HSR train sets tend to come in two large design categories. Some use dedicated power cars, usually two per train set, with unpowered carriages in between for passengers. These appear to generally be cheaper, but are limited to 9-10 carriages per train set. Almost all of the small HSR trains are of this configuration, including:</p>
<ul>
<li>Alstrom AGV
<ul>
<li>245-446 seats</li>
<li>NTV rail line in Italy</li>
</ul>
</li>
<li>Acela Express Trainset
<ul>
<li>304 seats</li>
<li>In use with Amtrak</li>
</ul>
</li>
<li>Renfe 100
<ul>
<li>329 seats</li>
<li>In operation in Spain</li>
</ul>
</li>
<li>Renfe45 102
<ul>
<li>318 seats</li>
<li>In operation in Spain</li>
</ul>
</li>
</ul>
<p>These are just the smallest train sets of this configuration I could find. Lots of trains of this design are significantly bigger, with the norm being 400-500 seats.</p>
<ul>
<li>KTX-Sancheon
<ul>
<li>363-410 seats</li>
<li>In operation in South Korea</li>
</ul>
</li>
<li>TGV Réseau
<ul>
<li>377 seats</li>
<li>In operation in France</li>
</ul>
</li>
<li>Euroduplex
<ul>
<li>509-533 seats</li>
<li>France and Morocco</li>
</ul>
</li>
<li>TGV Duplex
<ul>
<li>508 seats<sup id="fnref:18"><a href="#fn:18" class="footnote-ref" role="doc-noteref">18</a></sup></li>
<li>France, again</li>
</ul>
</li>
<li>TGV M
<ul>
<li>740 seats<sup id="fnref:19"><a href="#fn:19" class="footnote-ref" role="doc-noteref">19</a></sup></li>
<li>No points for guessing that this is also French</li>
</ul>
</li>
<li>FS Class ETR 500
<ul>
<li>422-671 seats</li>
<li>In operation in Spain</li>
</ul>
</li>
</ul>
<p>At this point we&rsquo;re above the A380 in capacity, but we&rsquo;re not done yet! There is another type of HSR railset, the Electrical Multiple Unit (EMU). EMU trains lack dedicated powered cars, and instead have some or all of the passenger compartments powering the train. These come at higher per-train cost, but can be configured to nearly arbitrary sizes, and can move an absurd number of people. EMU trainsets seem to vary anywhere from 8 to 20 cars. Different lengths on the same line to adjust capacity seem to be pretty common, with the Shinkansen preferring 8 and 16 car configuration. Some examples.</p>
<ul>
<li>700 Series &ldquo;E&rdquo; configuration
<ul>
<li>8 cars</li>
<li>571 seats</li>
<li>San&rsquo;yō Shinkansen and Hakata Minami Lines</li>
</ul>
</li>
<li>CRH3
<ul>
<li>8-16 cars</li>
<li>551-1053 seats</li>
<li>In operation in China</li>
</ul>
</li>
<li>Fuxing
<ul>
<li>8, 16, or 17 cars</li>
<li>575-1283 seats</li>
<li>In operation in China</li>
</ul>
</li>
<li>N700A &ldquo;K&rdquo; configuration
<ul>
<li>16 cars</li>
<li>1,260 seats</li>
<li>In operation in Japan</li>
</ul>
</li>
<li>N700S-3000
<ul>
<li>16 cars</li>
<li>1,323 seats!!</li>
<li>In operation in Japan</li>
</ul>
</li>
</ul>
<p>So that is our range for HSR, anywhere between 245 seats to 1,323 seats. Not exactly a relatively &ldquo;narrow&rdquo; limit, I would say. I&rsquo;ll certainly grant that airplanes give more flexibility at the low end of the spectrum with things like turboprops and very small narrow body jets like the A220 not having a direct HSR equivalent. But at the top end HSR wins the size comparison handily, plus it gives operators the ability to reconfigure train size quickly and cheaply if need be. There is no air equivalent to putting another carriage on the TGV M, or mixing and matching cars to make a TGV Duplex, or doubling the size of a CRH3.</p>
<h2 id="frequency">Frequency</h2>
<p>Okay, but are airplanes more frequent? Let&rsquo;s see!</p>
<p>Before we start, let&rsquo;s set the ground rules for comparison. First, frequency is largely driven by demand, so low frequency routes tell us very little about the system <em>could</em> do. The flight route between nowhere and east armpit doesn&rsquo;t really have a lot of demand, so it doesn&rsquo;t tell us what the flight route between LAX and SFO could theoretically handle. Second, we want to be very careful when comparing system wide stats to individual routes. At any given point there are more HSR trains in operation than there are flights between two arbitrary cities, but that infrastructure demand is spread out, and does not tell us what the throughput between two given cities could be. More simply put, frequency is driven by demand but limited by infrastructure.</p>
<h3 id="airplanes">Airplanes</h3>
<p>The first limiting factor for airplane frequency is that they can have a very long turnaround time, which is the amount of time it takes to swap one set of passengers for the next and prepare the plane for flight. The larger the plane, the worse this gets due to the ratio of passengers to exits. So for your very large aircraft like an A380, your turnaround time is 90-110 minutes, or nearly two hours worth of time not traveling. Smaller aircraft do this better. Southwest used to be able to do a <a href="https://apex.aero/articles/2020-11-17-turn-back-the-clock-southwests-quick-turnarounds/"target="_blank" rel="noopener noreferrer">10 minute</a>
turnaround with their 737-200s back in 1977, but these only seated 130 people max. Now that Southwest runs 175 seat 737 Max 8&rsquo;s, their average turnaround seems to be about 35 minutes pre-pandemic. During the pandemic that expanded to 50 minutes due to the time required to clean surfaces. Rounding the math a bit, a 30 minute dwell time for a one hour route puts the maximum frequency of 8 round trips per day per plane. The 90 minute turnaround time for an A380 only allows for a bit under 5 round trips per day per plane.</p>
<p>The obvious solution here is to buy more than one plane. Airlines make money on all but the smallest routes (which are often subsidized), so assuming there is customer demand it&rsquo;s pretty easy to justify buying another plane. Assuming that you can get a crew for it (there is a pilot shortage at the moment), two 737s would allow Southwest to run 16 round trips a day, and three would get you 24. Continuing to assume that we can lease enough planes and hire enough pilots, what&rsquo;s our limiting factor?</p>
<p>Turns out that gates are our limiting factor. We&rsquo;re all familiar with specific airlines being in specific terminals (Southwest is in terminal 1 at LAX), but most people don&rsquo;t know that airlines lease individual gates from the airline too. Currently Southwest has <a href="https://www.lawa.org/news-releases/2021/news-release-027"target="_blank" rel="noopener noreferrer">13</a>
gates at LAX, so let&rsquo;s start with that as our number. 13 gates means that we can have no more than 13 planes currently turning over in parallel; any more and our turnaround time will increase and our frequency will not change. Sticking with our generous 30 minute turnaround time, this means that a new plane can arrive every 30/13 or every 2.3 minutes. At this frequency, with no mistakes, every time a plane leaves to take off, another will be arriving to take its spot. This frequency gets us 626 round trips per day from 13 gates with a 30 minute turnover time with no variation or mistakes.</p>
<p>But wait! Capacity at the other side matters too! SouthWest shares one gate with JetBlue and has five all to itself at SFO. This means our capacity on the SFO side is about 5 gates, depending on how JetBlue and SouthWest split gate B8. This drops our frequency for LAX&lt;-&gt;SFO down to 30/5, or every six minutes for a total of 240 a day.</p>
<p>But there are still issues! Those gates are not intended to serve just one route they&rsquo;re intended to serve <em>all</em> routes. If we use that to run one route at maximum frequency, Southwest will not be able to fly anywhere else from SFO. Southwest in fact flies to 7 different cities direct from SFO. Even assuming that the route route is twice as important as the rest (I made this number up) we get a much smaller 60 flights per day. But still, we do have a workable formula here: the maximum flights possible for an airline at an airport is <code>(turnover time)/(min(gates at airport a, gates at airport b))</code>.</p>
<p>We&rsquo;re not being terribly fair to airplanes here though. The number of users who will refuse to fly to any given city if it&rsquo;s not on their favorite airline is small, most users will price shop. Rather than doing more math, I think the best way to actually figure this out is to look at real world route numbers. This should give us an idea of what the high water mark is across all cariers in an airport. So, what is the busiest route that actually exists in the world?</p>
<p>The busiest in terms of both passenger count and plane trips is Jeju South Korea (CJU) to Seoul (GMP). Between January and November this route totaled 71,388<sup id="fnref:20"><a href="#fn:20" class="footnote-ref" role="doc-noteref">20</a></sup> trips, and it totaled 17,082,700 passegners for all of 2021. This time frame gives us 334 days, and an average of 213 flights per day. Presumably this number varies a lot on a day to day basis, given that Jeju is a tourist destination. After this route the numbers fall off dramatically, with the next most populous route being Seoul to Busan South Korea, with 28,809 flights between January and November of 2021, or 86 a day averaged. LAX to SFO ran 15,828, or a mere 47 a day averaged. While a few routes are extremely busy, most routes do not actually see that many planes per day.</p>
<h3 id="hsr">HSR</h3>
<p>HSR frequency is actually pretty tricky to figure out, because it depends heavily on track design. Trains do not accelerate and decelerate quickly, so all trains must keep a minimum safe distance between each other measured in minutes. Simplistically this puts an absolute ceiling on the frequency that trains can travel. For the Shinkansen the minimum safe headway is 3 minutes<sup id="fnref:21"><a href="#fn:21" class="footnote-ref" role="doc-noteref">21</a></sup>, giving you a maximum frequency of 60/3=20 per hour.</p>
<p>There is also the concept of dwell time, which is the amount of time that the train spends at the station waiting for passengers. Dwell times for trains are much smaller than turnover for planes due to a much higher door/passenger ratio, but they are not instant. They are also partially decided by cultural factors about how compliant people are in queueing and boarding. For the Shinkansen system the average dwell time is 3 minutes, and 5 at the airport for baggage. The TGV tends to be 5 minutes. Lets be pessimistic and assume 5 minute dwell times. Assuming simplistic signaling, all trains must be minimum headway + dwell time apart to ensure that following trains have enough headway while the preceding train finishes its transfer, which gives us 8 minutes for the Shinkansen. More intelligent signaling ought to be able to reduce the headway as trains decelerate, since a slower train stops faster, that way each train does not need to maintain a full 3 minutes headway as its decelerating. So our minimum spacing in this case drops to either the maximum dwell time among the stations, or the minimum safe headway, whichever is lesser. For most HSR routes it&rsquo;s going to be the dwell time, since 5 minute dwell times seem to be pretty normal for stations connecting to (ironically) airports.</p>
<p>Of course this assumes that each station has only one platform and every train stops at every station, which is a very bad assumption to make. To stick with the Tokaido Shinkansen we see that they run three named services on the line with sixteen stations. Only one service, the Kodama, stops at every stop. The Nozomi only stops at six stations on the route, and the Hikari changes what stations it stops at depending on the time of day. Having different trains stop at different stations lets the operators bypass slow stations for express routes, and move more trains than the station design might otherwise allow. Shinkansen stations are also universally multi-platform, which will allow trains to travel closer together than their dwell time, and overlap slightly in the station. The only station on this route that only serves the Shinkansen is Shin-Fuji station, and it has two platforms. The rest have more platforms to both service the Shinkansen and various other commuter rails. Excepting the mega stations near the end of the line, the median station on this line seems to have six platforms, and most serve not just HSR but local commuter rail as well.</p>
<p>Okay, enough theoretical talk, what is the actual observed frequency of HSR? It varies. European HSR seems to run at relatively low frequencies, such as the Eurostar Paris-&gt;London route with 12-14 daily trips, and the Paris-&gt;Lille service offers 18 daily trips. German ICE trains tend to have hourly or every other hour service. Chinese HSR varies from 1 a day (Beijing–Suzhou) to 238 a day (Huning PDL), with the dedicated HSR lines seeing much more frequent and rapid use. None of their dedicated linesn sees fewer than 12.</p>
<p>The real high water mark for HSR is again the Tokaido Shinkansen, which operates 365 daily trips, peaking at 16 per direction per hour. This combined with the largest trains is certainly why their ridership is the highest.</p>
<h2 id="takeaways">Takeaways</h2>
<p>As is expected, there is a lot of variation. But on the whole HSR shows higher capacity, <em>and</em> the possibility of higher frequency operation than all but maybe one or two air routes. Even moderately sized HSR trains like the Euroduplex exceed all but the largest aircraft, while many EMU trains more than double the seating capacity of any aircraft for sale today.</p>
<p>Frequency tends to vary a lot as well. Most HSR and air route do not see a lot of trips, but the heavily used routes see a <em>lot</em> of daily trips, more than all but one or two air routes. The Tokaido Shinkansen moved 452,000 people <em>per day</em> back in 2016. The busiest air route in 2021 moved 17 million people for the entire year, which one line on the Shinkansen exceeded in 38 days. The busiest route in America, NYC to LAX is equivalent to less than 9 days of Tokaido Shinkansen, SFO to LAX is 8 (2018 numbers for both air routes). And we&rsquo;re handicaping the Shinkansen by using 2016 numbers for it and later dates for the air routes. HSR can move an unbelievable amount of people if the will is there.</p>
<p>Why am I focusing on this so much? Because Casey seems to have a drastic misunderstanding of the capabilities of HSR. He had this comment in the follow up discussion from his article.</p>
<blockquote>
<p>HSR headway requirements mean they move not that many people either. 740 people per train is great, but how many trains move per hour? Even Japan I think does maybe 70 trains per day on the busiest routes, or &lt;3/hour.</p>
</blockquote>
<p>There is literally no part of this sentence that is true! All the numerical claims are not just wrong, they are all a digit short of the correct answer. I get that this is a blog written for free &ldquo;in about an hour between putting the kids to bed and collapsing from exhaustion&rdquo;<sup id="fnref:22"><a href="#fn:22" class="footnote-ref" role="doc-noteref">22</a></sup>, but these numbers were not hard at all for me to verify. I think the argument that most HSR does not have the same scale as airlines is probably true, but Casey said that they &ldquo;can&rsquo;t&rdquo;, and that is clearly false.</p>
<h2 id="rail-is-outdated">Rail is Outdated?</h2>
<blockquote>
<p>Even in 2022, freight by rail is much slower as rail cars must wait in yards for trains to be assembled.</p>
</blockquote>
<p>I&rsquo;m going to keep this discussion brief, because going into freight rail is going to make this long post longer. The issues listed here are actually an issue with American rail specifically, and how it&rsquo;s organized. It is <em>not</em> endemic to all rail systems. Basically in the 1970s American freight rail operators made the decision to make trains longer and less frequent. This has reduced labor costs for the railways, but has resulted in more derailments, more traffic jams, inconsistent schedules, and low quality of life for rail workers. Not every nation has gone down this path, with countries like Switzerland producing freight systems that has drastically reduce the amount of trucking in the country. The result is that US freight rails are largely bulk, time insensitive goods (grain, aggregate, coal, etc.), a larger percentage of European freight rail is individual wagon loads destined for smaller enterprises, rather large unit trains for massive consumers like power plants. For more, check out Justin Roczniak&rsquo;s <a href="https://www.nytimes.com/2022/10/09/opinion/business-economics/freight-train-mismanagement.html"target="_blank" rel="noopener noreferrer">recent NYTimes piece</a>
or the episode on <a href="https://www.youtube.com/watch?v=V0qcxyyllQ4"target="_blank" rel="noopener noreferrer">battery electric trains</a>
.</p>
<h1 id="von-kármángabrielli-diagram">von Kármán–Gabrielli Diagram</h1>
<p>I&rsquo;m going to break out an entire section to talk about von Kármán–Gabrielli diagrams, because this matters. See the image from Casey&rsquo;s blog below.</p>
<p><img src="http://ashtonkemerling.com/images/trains/casey-g-k.png"
alt="von Kármán–Gabrielli Diagram from blog"/></p>
<p>First, lets explain this chart. This chart is designed to represent how efficient an entire mode of transportation can be in a way that is trivially comparable. This is necessary (and brilliant!) because it can be somewhat hard to compare the efficiency of different modes of transport using more naive methods.</p>
<p>On the X axis we have speed in miles per hour. This exists because every mode of transport has both a minimum and maximum reasonable speed, nothing in the world is going to make a horse go 100mph for example, and efficiency changes over those speeds in different ways for different modes of transport.</p>
<p>The Y axis is a unitless efficiency rating, which is not quite the same as efficiency as you or I might be used to. The goal is to compare modes of transport, not just individual vehicles. The unit is <code>energy used / (vehicle mass x velocity)</code>. This efficiency lets us both compare across vehicle types, but also eliminates rather simple forms of analysis. If you throw a ton of bricks in the back of your truck and your fuel economy goes down, it has not necessarily gotten less efficient as a means of transport, you&rsquo;re just asking it to do more. Making your vehicle out of light weight composites will likewise improve energy consumption, but will not drastically change the line on this graph. But if you replace a steam train with an electric one, then we&rsquo;d expect the number to change. Put more sincinctly this graph responds to large jumps in efficiency, not incremental ones.</p>
<p>Two other things. First there is a marked &ldquo;limit line&rdquo; on the graph. This isn&rsquo;t some iron-clad rule of the universe, it&rsquo;s just the apparent limitation of technology at the time. Second both axis are logarithmic, so straight lines are deceiving.</p>
<p>Here&rsquo;s Casey&rsquo;s argument with this graph.</p>
<blockquote>
<p>The zeroth order truth of the vK-G diagram is that there is a limit line of vehicular performance, which is essentially determined by momentum transfer limitations for vehicles that have to displace water or air to move along. It does not apply to spacecraft!</p>
</blockquote>
<blockquote>
<p>The first order truth is that, above 100 mph, the most efficient transport mechanism shifts from ground-based to air-based. For smaller creatures than humans, the transition speed is a lot lower – most insects fly instead of walk.</p>
</blockquote>
<p>And if you look at the graph you can indeed see his point. The &ldquo;autorail&rdquo; line is both further to the left of airplanes, and the line is sloping up quickly. This if we extrapolate from the train line, it&rsquo;s pretty clear that at a minimum it is going to be much less efficient than an airplane at around 300mph, which is where airplanes are the most efficient.</p>
<p>But, wait a second, something weird is happening here. This clearly shows trains topping out at 100 miles per hour, but plenty of train lines hit 200 miles per hour. And it shows airplanes being the most efficient at 300mph and maxing out at 400mph, when the cruising speed for a 737 is about 515mph. And what the hell is &ldquo;autorail&rdquo;? Something is up. So, let&rsquo;s be good investigators and check the citation, rather than just the graph.</p>
<p><img src="http://ashtonkemerling.com/images/trains/casey-g-k-citation.png"
alt="von Kármán–Gabrielli Diagram Citation"/></p>
<p>Oh&hellip; Oh no. This graph is from 1950. While the methodology is still sound, I do not think that the actual numbers hold true 72 years later. At a minimum these numbers represent propeller driven aircraft, and potentially steam trains<sup id="fnref:23"><a href="#fn:23" class="footnote-ref" role="doc-noteref">23</a></sup>. We cannot draw any meaningful lessons about today&rsquo;s technology using this.</p>
<p>So, here&rsquo;s an updated graph! It&rsquo;s from 2004, and while that&rsquo;s also oldish, at least vehicles manufactured in 2004 are still in regular use today.<sup id="fnref:24"><a href="#fn:24" class="footnote-ref" role="doc-noteref">24</a></sup></p>
<p><img src="http://ashtonkemerling.com/images/trains/updated-g-k.jpg"
alt="Updated von Kármán–Gabrielli Diagram"/></p>
<p>This graph is a tiny bit harder to read, because the authors added a few new features. First, each vehicle now has <em>two</em> lines, one for 1950 and one for 2004. Solid lines are old, dashed lines are updated. This lets us see how things have changed. Second, the creator of this chart has added specific vehicles to the lines, so for example Concorde is pointed out specifically. These represent the far edge of what a given mode of transport can do.</p>
<p>First thing you&rsquo;ll notice is that super tankers and passenger rail is now below the line. We&rsquo;ve clearly pushed the limits of technology since 1950, which is good and expected. The second thing you&rsquo;ll notice is that the curve for passenger rail is now clearly <em>below</em> that of airplanes. Casey&rsquo;s assertion that &ldquo;above X mph the most efficient form of transport shifts to air&rdquo; is at least no longer obviously true, and may in fact be false.</p>
<p>This holds up when we consider the real world numbers from the Economic Analysis book, which lists the following figures for MJ per passenger km:</p>
<ul>
<li>Gasoline car on highway: 0.47<sup id="fnref:25"><a href="#fn:25" class="footnote-ref" role="doc-noteref">25</a></sup>
<ul>
<li>This assumes 5 passengers. so 2.35 for single occupancy</li>
</ul>
</li>
<li>Diesel car on highway: 0.34
<ul>
<li>Same as gasoline car. 1.7 for single occupancy</li>
</ul>
</li>
<li>Passenger aircraft for 500km flight: <em>1.8</em><sup id="fnref:26"><a href="#fn:26" class="footnote-ref" role="doc-noteref">26</a></sup></li>
<li>Intercity rail: 0.22</li>
<li>HSR: 0.53</li>
</ul>
<p>I will admit, I got more than a tiny bit snarky in the comments about this on Casey&rsquo;s blog. We all make mistakes, I&rsquo;m sure I&rsquo;ve made some here, but this one is pretty glaring. That being said it&rsquo;s the response to the error that really sits poorly with me, as Casey&rsquo;s eventual response is that the blog is free<sup id="fnref:27"><a href="#fn:27" class="footnote-ref" role="doc-noteref">27</a></sup> and he owes me nothing. Obviously my own snark contributed to that interaction, but I think he owes his readers more intellectual rigor than this. My assertion is not that he owes me specifically an apology, but rather I think that he owes his readers in general some level of intellectual rigor and honesty.</p>
<p>Also very interesting is that &ldquo;transrapid 08&rdquo; mark, which is a maglev train. Most people know that maglev trains are really, really fast, but I don&rsquo;t think people realize how efficient they are too. To be fair, a lot of the concerns about the cost of building HSR <em>absolutely</em> apply to maglev trains. The only existing one cost a pretty absurd $1.33B for only 19 miles of track. But it can also go 431kph, and is several times more efficient than an equivalent plane. They can also apparently handle steeper gradients, which is very interesting. They might be a game changer, or they might be a dead end due to construction costs, it&rsquo;s too early to say<sup id="fnref:28"><a href="#fn:28" class="footnote-ref" role="doc-noteref">28</a></sup>.</p>
<h1 id="funny-accounting">Funny Accounting</h1>
<p>It&rsquo;s time that we talk about the money.</p>
<h2 id="airport-time">Airport Time!</h2>
<blockquote>
<p>If I build another airport, I have added 15,000 potential connections to the network. If I build another rail terminal and branch line, at significantly greater cost than an airstrip, I have added only one additional connection to the network.</p>
</blockquote>
<p>This quote is expressing two distinct ideas.</p>
<ol>
<li>Creating an airport enables more types of travel than HSR</li>
<li>HSR is much more expensive than an airport.</li>
</ol>
<p>I think there is a defensible argument in here! It is obviously true that creating an airport enables types of travel that HSR cannot, especially in a country the size of America. I am certainly not going to argue that my city does not need an airport, as there is no reasonable world where that airport can be replaced with HSR to where I want to go.</p>
<p>But, I disagree with the sentiment expressed in the quote in some very specific ways.</p>
<ol>
<li>It is drastically overstating network effects of airports. Adding a new airport does not come anywhere close to 15,000 connections</li>
<li>It implies that HSR and air is an either or proposition</li>
<li>It drastically understates the cost of air travel infrastructure.</li>
</ol>
<h3 id="hey-how-many-airports-are-there-anyways">Hey, how many airports are there anyways?</h3>
<p>Really, 15,000 airports? That feels wrong. I&rsquo;ve moved around and travelled a decent bit, and I can only name 21 I&rsquo;ve been to in the United States, which is a measly 0.14%. Is it true that building a new airport gives you access to <del>15,000</del> 19,000<sup id="fnref:29"><a href="#fn:29" class="footnote-ref" role="doc-noteref">29</a></sup> airports?</p>
<p>Well, no. The vast majority of these are &ldquo;general aviation&rdquo; (GA) airports that largely serve private pilots. This is really sweet if you&rsquo;re one of the 160k<sup id="fnref:30"><a href="#fn:30" class="footnote-ref" role="doc-noteref">30</a></sup> Americans who have a private pilots license<sup id="fnref:31"><a href="#fn:31" class="footnote-ref" role="doc-noteref">31</a></sup> and can afford to own<sup id="fnref:32"><a href="#fn:32" class="footnote-ref" role="doc-noteref">32</a></sup> one of the roughly 210,000 GA aircraft registered in the US, but this is not relevant to the vast majority of the population. Technically these airports can offer non-scheduled private flights, known as chartered or air taxi service, but this is such a miniscule<sup id="fnref:33"><a href="#fn:33" class="footnote-ref" role="doc-noteref">33</a></sup> percentage of US flight miles, we can effectively ignore it. To the vast majority of the American population, these general aviation airports provide no utility in transporting them around the country.</p>
<p>Okay, so how many airports can you buy scheduled service to? According to the ASCE, 520. These are further categorized into large, medium, small, and reliever hubs. Here are the counts:</p>
<ul>
<li>Large
<ul>
<li>Count for at least 1% of US enplanements</li>
<li>There are 30 of them</li>
</ul>
</li>
<li>Medium
<ul>
<li>0.25-1% of total enplanements</li>
<li>I could find 31</li>
</ul>
</li>
<li>Small
<ul>
<li>0.05-0.25% of US enplanements</li>
<li>I could find 71</li>
</ul>
</li>
<li>Nonhub
<ul>
<li>&lt; 0.05%</li>
<li>264</li>
</ul>
</li>
<li>Reliever
<ul>
<li>Only exists to relieve congestion at a larger airport.</li>
<li>I could not be bothered to actually count these, but if the ACSE is right then the answer is 124.</li>
</ul>
</li>
</ul>
<p>Realistically, the vast majority of air traffic is going to go through large, medium, and small airports, which is a pretty small set. We&rsquo;ve now droped from 15,000 originally down to 132<sup id="fnref:34"><a href="#fn:34" class="footnote-ref" role="doc-noteref">34</a></sup>. So constructing a new airport theoretically gives you access to not 15,000 airports, but 132 airports for scheduled flights. That is far less impressive, but to be fair a lot of these 132 will be in large population centers where lots of people want to fly to.</p>
<p>For funsies I was able to find 223 stations served by TGV, including international ones like London-St Pancras. So there are more TGV stations than there are large airports in the US, which is interesting. By the numbers, building a new TGV station gives you access to more cities inside France than building a new airport gives you access to airports in America. But, to be fair more American Airports are going to be outside that magic 4.5 hour limit.</p>
<h3 id="network-effects">Network Effects</h3>
<p>The thing we&rsquo;re obliquely talking about in the previous section is the network effect. The network effect is the process by which certain types of systems become more valuable the bigger they are <em>in a non linear fashion</em>. This process doesn&rsquo;t just apply to transit<sup id="fnref:35"><a href="#fn:35" class="footnote-ref" role="doc-noteref">35</a></sup>, but we&rsquo;ll focus on transit here.</p>
<p>Imagine that the world has no airports, and you make the very first one at city A. This airport is basically a novelty, you can take off from it, but there is nowhere else to go; you can fly around a bit, but you&rsquo;re forced to land back at A again. Our total number of routes is 0. Building the second airport at city B increases the number of routes to 1; people in A can go to B and vice versa, so one new airport added one route. A third airport at C adds two more routes to our network even though it only added one extra place you can go to from A or B. Our routes now include A-B, A-C, and B-C. Adding a fourth airport adds three more routes, and so on and so forth. The size of the network is basically <code>(N-1)!</code><sup id="fnref:36"><a href="#fn:36" class="footnote-ref" role="doc-noteref">36</a></sup>. This is an exponential process, and is what Casey is talking about when he says that adding a new airport gives you more options than a new train route.</p>
<p>Of course, this is not actually how airports work. Not every airport has a connection to every other airport, there is and never will be enough infrastructure to handle that layout. Instead most airports connect to the destination through a regional hub. So my airport (Boise) only offers direct flights to a handful of major cities, and mostly close ones at that<sup id="fnref:37"><a href="#fn:37" class="footnote-ref" role="doc-noteref">37</a></sup>. I can&rsquo;t even fly direct to NYC from where I live. If I want to travel to anywhere not on this short list, I have to fly to one on the list and transfer. So trips to NYC almost certainly require a layover in Denver, Atlanta, or Chicago. This drives up travel time far above what the straight line speed of an aircraft would imply, and certainly is a drag on customer usage.</p>
<p>But wait, it gets worse! All of this only applies to airports that are big enough and expensive enough to attract even a small number of airlines. Even among airports offering scheduled service, this is not the majority. If I lived over in Twin Falls, my flight options look a lot worse. Twin Falls airport offers scheduled service and is classified as a &ldquo;nonhub&rdquo; airport, but it only offers direct scheduled flights to Salt Lake City. A flight to Boise from Twin Falls involves a layover in Salt Lake City, plus $600 or more. All this for a 128 mile trip which could be served well by basic intercity rail<sup id="fnref:38"><a href="#fn:38" class="footnote-ref" role="doc-noteref">38</a></sup>. Instead we count on cars, which is both expensive (more on that in a second), has a lot of externalities<sup id="fnref:39"><a href="#fn:39" class="footnote-ref" role="doc-noteref">39</a></sup>.</p>
<p>When researching this article, I ended up considering the case of Youngstown OH. Youngstown has a regional airport, but that airport lost its last scheduled flight provider in 2018, meaning that everyone in the region now has to drive about an hour to CLE for flights. The frustrating thing is that Youngstown is precisely the kind of place that would be served by HSR (or a quick interurban connection to HSR) in Europe because it lies between major population centers that can support HSR traffic. In fact the Capitol Limited<sup id="fnref:40"><a href="#fn:40" class="footnote-ref" role="doc-noteref">40</a></sup> used to do exactly that! Our disinvestment in rail and preference for air travel has left places like Youngstown very vulnerable to positive feedback loops where loss of population and industry makes the airport less profitable, losing flights and routes which hinders economic recovery. I suspect that upgrading the Capitol Limited to even Category II EU standards might be worth it, but that will have to wait for another post; this one is far too long already.</p>
<p>Rail networks are much more complicated to model. It depends on the layout of the existing rail, and how new lines are added. Keeping in mind that 4.5 hour figure from above, it is not hard to see how adding a branch line from a LA-&gt;SF HSR to Sacramento would allow people in all 3 cities to reach each other. As a general rule adding a new station enables access between the new branch and anywhere else in the network that is 4.5 hours away, which can often be significantly more than just &ldquo;one additional connection&rdquo;. This is particularly true when the new branch offers <a href="https://en.wikipedia.org/wiki/Through_service"target="_blank" rel="noopener noreferrer">through service</a>
, which is common in a lot of interurban rail. Through service means that a train on one branch &ldquo;changes&rdquo; its name and continues operation on another route. This means customers can avoid transferring trains and travel through. This is not a panacea for network effects in general, but it does make the situation a lot rosier than Casey states.</p>
<p>Also, at the risk of being snarky, rail system designers are not dumb. The tradeoffs and usage patterns for HSR vs plane vs car are very well known at this point in time. Lines are added to connect as many people to as many points on the network as is reasonably possible, and to shorten as many trips as is possible. If a route will provide minimal value to the overall network, it just won&rsquo;t get made.</p>
<h3 id="either-or-fallacies">Either Or Fallacies</h3>
<p>I think the big fallacy Casey is making here is that he&rsquo;s implying that we can have either an airport or a HSR. Obviously I think this is a mistake.</p>
<p>At first blush, this is a reasonable assumption to make. While we can haggle over how cheap we could possibly make a new HSR network, the practical floor for even a small set of routes through California is in the tens of billions. Airports are likewise expensive. It absolutely makes sense to avoid making two very large infrastructure decisions that seem to compete.</p>
<p>And yet, that is <em>exactly</em> what countries with HSR do. While it sounds dumb to say this explicitly, Paris has a big airport. It in fact has two airports, and it is the center of all of France&rsquo;s HSR offerings. What gives?</p>
<p>It&rsquo;s worth thinking about what happens to tranel between two cities with viable HSR. There are three possible things that can happen, and they are not mutually exclusive.</p>
<ol>
<li>Airline travel shifts over to HSR</li>
<li>Non-airline travel shifts over to HSR, typically car trips</li>
<li>HSR generates new trips</li>
</ol>
<p>If airline traffic shifts to HSR, then we free up gates in the airport. This lets us either use those gates for routes that HSR cannot possibly handle, or it allows us to build a smaller airport<sup id="fnref:41"><a href="#fn:41" class="footnote-ref" role="doc-noteref">41</a></sup> or defer incredibly expensive airport expansion. Which you choose depends on what demand for non-HSR routes looks like, and what the costs of expansion might be.</p>
<p>Non-airline car traffic shifting over to HSR is an unambiguous public good. Driving is inefficient, polluting, dangerous, and expensive. Getting people to reduce car trips voluntarily because we&rsquo;ve offered them something more convenient is a win-win. Less pollution, fewer car deaths, less traffic<sup id="fnref:42"><a href="#fn:42" class="footnote-ref" role="doc-noteref">42</a></sup>, what&rsquo;s not to love?</p>
<p>And finally HSR can generate new trips that did not exist before, increasing the total number of trips between the cities in question. This is your classic <a href="https://en.wikipedia.org/wiki/Induced_demand"target="_blank" rel="noopener noreferrer">induced demand</a>
, except that it&rsquo;s good for mass transit. Induced demand for roads is bad because roads do not scale well and traffic becomes an issue. Induced demand for trains is less of an issue because trains scale relatively gracefully. Relatively few HSR routes are capped out in terms of frequency and train size, so you can just run more trains<sup id="fnref:43"><a href="#fn:43" class="footnote-ref" role="doc-noteref">43</a></sup> if more people want to travel. This is extremely good. The purpose of mass transit is to move people around so that they can enjoy their lives and generate economic activity. If a shiny new HSR network makes more people do that, then it&rsquo;s doing exactly what we wanted it to do.</p>
<h3 id="airports-are-cheap-right">Airports are cheap, right?</h3>
<p>What about that &ldquo;at significantly greater cost&rdquo; bit? Is HSR more expensive than an airport?</p>
<p>Honestly, it&rsquo;s not exactly clear to me. The tradeoffs in terms of up front cost is extremely complicated, and requires us run through some counterfactuals that are way beyond my ability. How much would LAX cost to construct and run if most of its California bound traffic got shifted to HSR? Hell if I know.</p>
<p>Instead I&rsquo;m going to focus on the &ldquo;significantly greater cost&rdquo; half. Airports are, frankly, really fucking expensive in the US. But they are expensive in a way that is very hard for us to see. HSR tends to be either nationalized or run by a small number of highly visible companies whose budgets and subsidies are subject to easy visibility. Airports on the other hand are typically run by the city they&rsquo;re part of, which makes tracking down the sum total of subsidies and construction costs beyond what I can research easily. Also there tend to be a lot of hidden subsidies, such as joint civil military<sup id="fnref:44"><a href="#fn:44" class="footnote-ref" role="doc-noteref">44</a></sup> bases. My local airport hosts a portion of the Idaho national guard. How much does this subsidize the airport? Dunno.</p>
<p>Less directly, there are schenanigans involved in the financing of airport maintenance and work. Salt Lake City rebuilt their terminal last year (2021) for $4.1B. All of the articls I read were very, very specific to say that no tax payer money would go towards the project, and this is kind of true. Financing for the project was done through bonds issued by the city itself and repayable from revenue from the airport and trust accounts<sup id="fnref:45"><a href="#fn:45" class="footnote-ref" role="doc-noteref">45</a></sup>, and interest earned by investors is <em>tax free</em> both federally and at the state level for Utah residents. This provides the airport company a significantly lower cost of financing the project at the cost of lowered income taxes and leveraging the city&rsquo;s better credit rating. This kind of bond structure is not unique to Utah or airports, but I think we should be absolutely clear that this is a subsidy structured to not look like one.</p>
<p>Anyways, airports need to be constructed new and reconstructed on a regular basis. Here are a few projects I found that were completed.</p>
<ul>
<li>Denver International Airport (1995)
<ul>
<li>Budgeted: $2.8B</li>
<li>Actual: $4.8B<sup id="fnref:46"><a href="#fn:46" class="footnote-ref" role="doc-noteref">46</a></sup></li>
<li>Inflation adjusted: $8.5B</li>
</ul>
</li>
<li>Salt Lake City Airport Terminal (2021)
<ul>
<li>Budgeted: $3.6B</li>
<li>Actual: $4.1B</li>
</ul>
</li>
<li>Atlanta Airport Runway 10-28 (2006)
<ul>
<li>$1.28B</li>
</ul>
</li>
</ul>
<p>Clearly building even a terminal is fairly expensive. Worse still these need pretty expensive rebuilds on a constant basis. Airport Technology&rsquo;s <a href="https://www.airport-technology.com/airport-construction-projects/"target="_blank" rel="noopener noreferrer">project pipeline tracker</a>
lists 127 ongoing projects worth <em>$155B total</em>. Worse still, some of these projects are repeats, with recently rebuilt or expanded airports getting another pass of money. For example Denver International Airport is getting upgraded again to the tune of $2B, after the initial construction in 1995 went over budget by a factor of 2.</p>
<p>Here&rsquo;s a list of project that stood out to me. All of these are in execution at time of writing, and I&rsquo;ve included a few examples in countries with known HSR networks, for later comparison.</p>
<ul>
<li>John F. Kennedy International Airport Redevelopment ($15.5B)</li>
<li>O&rsquo;Hare International Airport Expansion ($9.8B)</li>
<li>O&rsquo;Hare International Airport Expansion II ($8.5B)<sup id="fnref:47"><a href="#fn:47" class="footnote-ref" role="doc-noteref">47</a></sup></li>
<li>LaGuardia Airport Redevelopment ($8B)</li>
<li>Hartsfield-Jackson International Airport Expansion ($6B)</li>
<li>LAX Automated People Mover System ($4.5B)</li>
<li>San Francisco International Airport Expansion ($4.1B)<sup id="fnref:48"><a href="#fn:48" class="footnote-ref" role="doc-noteref">48</a></sup></li>
<li>Henoko Runway Development ($8.5B)<sup id="fnref:49"><a href="#fn:49" class="footnote-ref" role="doc-noteref">49</a></sup></li>
<li>Frankfurt International Airport Expansion: Terminal III ($4B)</li>
</ul>
<p>What about rail? The <em>Economic Analysis of High Speed Rail in Europe</em> lists that the cost of HSR as being between €9,000,000 and €39,000,000 per km (€10,412,035.44 to €45,118,820.23 in 2020), while maintenance varies between €12,919 and €71,650 (€14,945.90 to €82,891.37 in 2020) for <em>European</em> HSR projects. Do these numbers hold up in the decade since publication? What about for Japan?</p>
<ul>
<li>Perpignan–Barcelona high-speed rail line
<ul>
<li>175km double track</li>
<li>8.3km tunnel</li>
<li>Cost €1.1 billion<sup id="fnref:50"><a href="#fn:50" class="footnote-ref" role="doc-noteref">50</a></sup> (€1.42 billion in 2020)</li>
</ul>
</li>
<li>LGV Bretagne-Pays de la Loire
<ul>
<li>214km double track</li>
<li>Cost €3.3 billion (€3.71 billion in 2020)</li>
<li>Includes 25 years of maintenance</li>
<li>Estimated cost should be between €2.3B and €10B</li>
</ul>
</li>
<li>LGV Sud Europe Atlantique
<ul>
<li>340km double track</li>
<li>€3.8 billion for the main track (€11,176,470)</li>
<li>€1.2 billion for connection, signal improvements, etc.</li>
</ul>
</li>
<li>Nishi Kyushu Shinkansen (2022)
<ul>
<li>66km</li>
<li>5 stations</li>
<li>$4.4B ($66m per km, or roughly €58.4m)<sup id="fnref:51"><a href="#fn:51" class="footnote-ref" role="doc-noteref">51</a></sup></li>
</ul>
</li>
<li>Hokkaido Shinkansen (2015)
<ul>
<li>148km (53km in an existing tunnel)</li>
<li>1 station rebuilt</li>
<li>$4.67B ($31.5m or €27.6m)</li>
</ul>
</li>
<li>Hokkaido Shinkansen Extension (2031)
<ul>
<li>211km, 76% in existing tunnels</li>
<li>2 new stations.</li>
<li>$11bn ($52M or €50.5m per km at 2022 rates)</li>
</ul>
</li>
</ul>
<p>A few clear takeaways. First off, it&rsquo;s hard to estimate per km track construction vs maintenance cost for the French because of how France structures these. SNCF loves to purchase maintenance along with the track, while Japan splits them out. That being said Japanese construction costs fall slightly outside the quoted range for EU HSR construction on the high end. This is actually quite unsurprising, given the terrain of Japan and the number of tunnels their trains go through. I also listed the stations that are new with these Shinkansen extensions, but it was not clear to me if they&rsquo;re included in the price. If they are included then the per-km cost of these projects drops dramatically, if they&rsquo;re not then they&rsquo;re still no more than 10-11% more expensive than a the worst case European HSR projects.</p>
<p>Secondly I&rsquo;d like to draw attention to the Perpignan-Barcelona project, which is structured differently than SNCF projects. It <a href="https://www.ladepeche.fr/article/2010/12/20/973804-historique-tgv-franchi-pyrenees-premiere-fois.html"target="_blank" rel="noopener noreferrer">appears</a>
that the project came in at the estimated cost of 1.1 billion euros including the tunnel which cost 300 million euros by itself. This brings the total cost of construction to an incredible 6.2 million euros per kilometer, way below the estimate. The company creating the project is going to run it for 53 years, and received a 540 million combined subsidy for its construction. To my eyes the only way this math works out is if that subsidy went entirely to constructing the route, and not to maintenance and operation, because if any is going to operation then the cost per km drops to implausibly low figures. This implies that at worst the expected operating loss is expected to be 540 million over 53 years, or 10 million per year.</p>
<h2 id="maintenance">Maintenance</h2>
<p>Casey goes on a long description about how wear works on HSR, which is very interesting but not something I need to copy and paste into this post. At the end of his description about HSR wear and maintenance, he makes this claim:</p>
<blockquote>
<p>Maintenance costs that were already on the order of $200,000/km/year, in 2003 dollars.</p>
</blockquote>
<p>Inflation adjusted that&rsquo;s $322,617.39 per year/km. I would <em>love</em> to know where he got that number, because I could not find it in any source Casey listed nor on my own.</p>
<p>What I was able to find was an analysis of European rail costs in 2009 in the Economic Analysis of High Speed Rail ni Europe, and they produce <em>drastically</em> different numbers than what is quoted here. The numbers I found from the 2009 paper listed a range from €12,919 to €71,650 per km total cost. I have a very hard time explaining how Italy is claiming a total maintenance cost of €12,919 per km (roughly $15,000)in 2002, while Japan is spending $200,000 per km in 2003 dollars. Yes, the Shinkansen sees more traffic than Italian HSR, but not enough to explain this difference. Rail maintenance costs scale with speed and frequency, and there is no reason to believe that HSR should cost that much to maintain in Japan. The Tokkaido Shinkansen operates 365 trains a day, compared to the 64 per day for the Florence-Rome line<sup id="fnref:52"><a href="#fn:52" class="footnote-ref" role="doc-noteref">52</a></sup>. The Shinkansen is faster (277kph vs 250kph), but the it&rsquo;s also heavier (715 tons vs 598 tons). They both run through mountainous terrain, and include some fairly expensive infrastructure like viaducts and tunnels. I&rsquo;m not sure which is likely to cost more, but I have an extremely hard time buying the idea that Japan is spending 13x per kilometer that Italy is.</p>
<h2 id="use-jets-instead">Use Jets Instead</h2>
<p>Right, so what about Casey&rsquo;s suggestion that we just use 737s instead? Where do we land on that suggestion?</p>
<blockquote>
<p>This capacity could also be served by a fleet of just 40 737s (less than current LAX-SFO traffic), of which Boeing makes more than 500 per year.</p>
</blockquote>
<p>Neither LAX nor SFO has the capacity to add this though. And while Boeing makes more than 500 a year, that&rsquo;s because a lot of people are buying them for a lot of different routes. Realistically buying 40 planes for this route means giving up on either replacing 40 older planes with new ones, or 40 planes elsewhere in the network. There just isn&rsquo;t spare capacity for that.</p>
<blockquote>
<p>Bought new, this fleet would cost $3.6b, and with a lead time of, at most, a few months.</p>
</blockquote>
<p>That&rsquo;s not how purchasing aircraft works. There is a backlog of aircraft based on other people&rsquo;s orders. Maybe you can negotiate your way up to the front of the queue, but that will definitely drive the price up.</p>
<p>Air Canada got its last 737 MAX 8 from its 2014 contract <a href="https://simpleflying.com/air-canada-takes-40th-boeing-737-max-8/"target="_blank" rel="noopener noreferrer">this August</a>
. As of September 2022 Boeing has 5,092 outstanding orders for the 737 MAX 8, and it&rsquo;s deliverd 926 total. They&rsquo;re hoping to get production up to get it up to 47 a month by 2023, but they&rsquo;re regularly stopping and starting production due to component shortages. The A320 neo family of craft has a backlog of 6,095 aircraft, and they were delivering them at ~450 a year pre-pandemic.</p>
<p>Not only are you not getting either of these aircraft in a few months, you&rsquo;ll be lucky to get them by the end of this decade.</p>
<blockquote>
<p>Upgrades to Modesto and Bakersfield airport terminals could service the 737 for mere $10s of millions.</p>
</blockquote>
<p>As we&rsquo;ve seen, this is nowhere close to correct. Terminal expansions and rebuilds cost in the billions, not tens of millions. Adding a few gates to Bakersfield is probably a $1B project, minimum.</p>
<p>Having lived in Los Angeles previously, I also find the idea of just upgrading Bakersfield kind of funny. You do realize how far Bakersfield is from LA, right? As I&rsquo;m writing this, Google Maps claims that the travel time between downtown Los Angeles and Meadows Field is 2 hours at the minimum. And anyone who&rsquo;s lived in Southern California knows that you cannot assume minimum travel times when it comes to traffic, I would either leave at an insane hour or pad that trip by 30-45 minutes just to be safe. There is a damned good chance that a HSR has made it from downtown LA to downtown SF before someone else has made it from LA to the Bakersfield terminal.</p>
<p>Google Maps also claims similar travel times between Modesto and downtown SF. I have never been to Modesto though, so I can&rsquo;t personally vouch for that.</p>
<h2 id="profitability">Profitability</h2>
<blockquote>
<p>Japan’s ostensibly private rail companies have gone bankrupt and been bailed out so many times I’ve lost count, racking up billion dollar yearly deficits year after year.</p>
</blockquote>
<p>Citation needed on the &ldquo;bankrupt and bailed out so many times&rdquo;. Yes, the privatization process involved the government absorbing a ton of debt, but since then they&rsquo;ve been profitable. JNR was plagued with cost overruns and inefficiencies in the post-war era, and those debts did need to go somewhere. But &ldquo;JNR was poorly run&rdquo; and &ldquo;none of the JR groups have turned a profit since then&rdquo; are distinct arguments.</p>
<p>JR Central has <a href="https://www.statista.com/statistics/695680/japan-net-income-jr-central/"target="_blank" rel="noopener noreferrer">increasing net incomes</a>
for the past 10 years, only going negative recently due to massive expenses constructing a new maglev shinkansen line<sup id="fnref:53"><a href="#fn:53" class="footnote-ref" role="doc-noteref">53</a></sup>. And it sure as heck looks like they&rsquo;re planning on paying for that maglev train without any direct subsidies. They&rsquo;ve borrowed 3 trillion yen from the state, and are building the rest up in a trust fund. Maybe we can gripe about subsidized government loans, but that applies to airports and airlines too.</p>
<blockquote>
<p>Indeed, as far as I know there isn’t a single HSR route anywhere on Earth that operates profitably on ticketing revenue, and so operation always requires substantial subsidies.</p>
</blockquote>
<p>So, what Casey is doing here is slipping in a political argument dressed as a practical financial one. Implicit in this discussion is the assertion that rail based transit must be profitable to be good. I disagree emphatically! Railways are a <a href="https://en.wikipedia.org/wiki/Natural_monopoly"target="_blank" rel="noopener noreferrer">natural monopoly</a>
, and a <a href="https://en.wikipedia.org/wiki/Club_good"target="_blank" rel="noopener noreferrer">club good</a>
. I am extremely comfortable with them losing money year over year and surviving on the back of public funds. If Casey wants to argue that rail <em>has</em> to be profitable, he should make that argument explicitly.</p>
<p>Of course, the original argument is that no HSR line has ever made money, and JR central runs a lot more than just HSR. If you dig into their annual <a href="https://global.jr-central.co.jp/en/company/ir/annualreport/_pdf/annualreport2021-13.pdf"target="_blank" rel="noopener noreferrer">report</a>
you will see that the Shinkansen represents only 29% of JR central&rsquo;s ridership, it represents 92% of the rail based revenue for JR Central. Even if we compare by passenger kilometers, the Shinkansen is 85% of the total. By passenger and by passenger kilometer, the Shinkansen makes more revenue than low speed rail.</p>
<p><strong>In fact, there is no way for the Shinkansen to not be profitable, according to their report. In FY2020.3 the Shinkansen made 1,261.3 billion yen in revenue, the conventional rail made 104.2 billion yen in revenue, and the overall rail business had an operating expense of 784.9 billion yen. Even if you believe that the conventional rail was literally free, then the Shinkansen still made 476.4 billion yen, four times what conventional rail pulled in.</strong> No matter how you divvy up the maintenance budget between conventional and HSR, HSR is not only profitable but overwhelmingly so compared to regular rail. The idea that the HSR is the money loser in this company is risible.</p>
<p>Oh yeah, and the original Shinkansen cost &hellip; 400 billion yen! It does not take an accounting wizard to see how to make the Shinkansen turn a profit, even including debt service, upgrades, infrastructure maintenance and rolling stock upgrades over the years. Apparently it even managed to pay back the emergency World Back loan in 22 years, despite JNR being largely insolvent at that point in time.</p>
<p>Of course there is another question worth asking: if we hold airlines up to this standard are they profitable? Because if the issue with HSR is construction costs, then shouldn&rsquo;t we consider the costs of airport construction when it comes to airline profitability too? Pick literally any airport older than 1990 and start digging through its history and it&rsquo;s easy to find billions of dollars of inflation adjusted government money. And that&rsquo;s before we consider the $3B in direct FAA subsidies per year towards airports, $315m a year for rural air travel the $9B cost of the TSA, and god knows how many subsidies to the airlines in terms of trade policy. Oh, and subsidies to Boeing and Airbus remain the subject of international diplomatic conflict going back decades. The exact amount is disputed, but it&rsquo;s in the billions easily.</p>
<p>To be clear, I&rsquo;m not saying that all of this is bad per se. I am personally very comfortable with government funding for things that are beneficial to the public, including very expensive infrastructure. What I am pointing out is that the standard of &ldquo;profit without subsidies&rdquo; is a standard that is selectively applied to rail travel and rail travel alone. That&rsquo;s bullshit.</p>
<blockquote>
<p>Of course roads also operate with public subsidies</p>
</blockquote>
<p>This is true, but notice how we&rsquo;ve subtly switched to a different standard from <em>profit</em> to <em>subsidies</em>. Casey is holding rail up to the standard of profitable, but reducing public contributions towards roads to mere &ldquo;subsidy&rdquo;. This is completely backwards though: most roads make <em>no</em> profit! None! Their construction and maintenance is paid for out of a variety of taxes, precisely because they&rsquo;re a common good. As a society we recoup those costs<sup id="fnref:54"><a href="#fn:54" class="footnote-ref" role="doc-noteref">54</a></sup> via economic activity and taxes on top of them.</p>
<h1 id="ca-hsr">CA HSR</h1>
<p>Okay, we do need to finally talk about CA HSR.</p>
<blockquote>
<p>If we want to reduce CO2-generating air traffic between San Francisco and Los Angeles (a worthy goal!) then the HSR route must be, above all, fast. The oft-stated goal time of 2 hours and 40 minutes is both unachievably rapid with finite money and current technology, and also too slow to compete with aircraft</p>
</blockquote>
<p>Phase 1 of this project goes from Los Angeles to San Francisco, and has a distance of 840km. Traversing this in 2 hours and 40 minutes requires an average speed of 315kph. This is quite high for HSR, but not &ldquo;unacheivably rapid with finite money and current technology&rdquo;. The Jinghu High Speed Railway averages 298km right now, with the goal of getting that up to a 328kph average. Even if a more pedestrian average of 300kph is managed that&rsquo;s 2 hours and 48 minutes. I would not call this project a failure if it&rsquo;s 2:48 when the goal was 2:40.</p>
<p>Meanwhile a flight from LAX to SFO is anywhere from 1hr 10min to 1hr 30 min. Getting to and through LAX in an hour is a miracle in my experience<sup id="fnref:55"><a href="#fn:55" class="footnote-ref" role="doc-noteref">55</a></sup>, so plus the whatever it takes to get from SFO to your destination. Even on time alone, beating a plane on this route is not at all impossible. Heck, it doesn&rsquo;t even seem that hard.</p>
<blockquote>
<p>but for insane TSA security delays that will probably also affect HSR</p>
</blockquote>
<p>Why are we assuming that HSR will have TSA checks? You can&rsquo;t hijack a train, what function would the TSA perform? And why are we assuming that CA HSR will have TSA checks when Amtrak, regional rail systems, subway systems, and our peer nations don&rsquo;t? There&rsquo;s no reason we need the TSA here, we could just &hellip; not use them.</p>
<blockquote>
<p>Routing HSR on the east side of the central valley via Bakersfield and Modesto means those cities can have a station, but frequent services means that most trains have to stop there, and each stop adds 20 minutes to the travel time. Alternatively, the stations and their railway corridors are extremely expensive city decorations that help no-one because the trains, dedicated to a high speed SF-LA shuttle, never stop.</p>
</blockquote>
<p>It is really weird to assert that all trains will stop, or none. The obvious solution to this, and the one that most systems use is to run a mix of trains that stop at every station and only some. To pick a random example the Tōhoku Shinkansen line in Japan runs four distinct services on the same track, each with their own mix of stations that they stop at and bypass.</p>
<p>This obviously increases operating costs, but it would also increase ticket revenue to offset, since people won&rsquo;t take HSR that doesn&rsquo;t have convenient schedules. Solving this is not exactly rocket science.</p>
<blockquote>
<p>To a good approximation, HSR lines have to be dead straight. In Kansas or California’s central valley, this is fine, up to a constant in Eminent Domain. But both LA and SF are ringed by a series of extremely geologically active, steep, and tall mountain ranges. The Interstate 5 out of LA goes through the Grapevine, passing through a point where 5 (5!!) different active fault lines intersect in one place. Maintaining a useful speed through these mountains, not to mention densely populated areas nearby, requires nearly 100 miles of tunnels.</p>
</blockquote>
<p>I mean, one of the most prolific HSR using and building nations in the world is Japan. 100 miles is not a lot tunnels to be honest. Sure, tunnels are more expensive than over flat terrain, but let&rsquo;s not pretend that they&rsquo;re some insurmountable obstacle. If Japan can make 33 miles of <em>undersea</em> tunnel for $7B, I would hope that America could figure out tunneling through a mountain too. Also, Japan is probably more seismically active than California.</p>
<p>HSR also does not need to be dead straight. The TGV has grades up to 3.5%<sup id="fnref:56"><a href="#fn:56" class="footnote-ref" role="doc-noteref">56</a></sup>, and curve radii anywhere between 4km (for 320kph service) and 7km for future<sup id="fnref:57"><a href="#fn:57" class="footnote-ref" role="doc-noteref">57</a></sup> speed improvements. Tilting trains are also an option here, and are commonly used for 250kph service on existing rights of way. Tilting trains of 350kph service would be new, but not revolutionary, and they should let the minimum radius for 350kph be as low as 4km.</p>
<blockquote>
<p>of tunneling costs are orders of magnitude too high,</p>
</blockquote>
<p>This is a political issue in America, maybe we should fix that instead of abandoning the construction of important infrastructure?</p>
<h1 id="weird-assertions">Weird Assertions</h1>
<p>Here&rsquo;s a list of weird, one off assertions that irked me. They&rsquo;re not that important to my central thesis, but I just couldn&rsquo;t let them go.</p>
<h2 id="ground">Ground</h2>
<blockquote>
<p>Hovercrafts have not caught on for the same reason as HSR – above 100 mph, the Earth is too rough to travel close to its surface.</p>
</blockquote>
<p>No, they didn&rsquo;t catch on because they&rsquo;re about as energy hungry as airplanes are, while traveling much slower. Scroll up to the von Kármán–Gabrielli Diagram section again and check out the updated graph.</p>
<blockquote>
<p>This is also intuitively obvious to pilots, who understand that making a habit of flying planes within 20 m of the surface, particularly in mountains, is a career-limiting move.</p>
</blockquote>
<p>Erm, isn&rsquo;t the problem less that the ground is bumpy, and more that aircraft aren&rsquo;t designed to fly close to the ground all the time? This is a bit like saying that the space shuttle doesn&rsquo;t fly as well as a 737; you&rsquo;re evaluating a vehicle in a context wildly different from the one it was designed for.</p>
<p>Also, we absolutely do have vehicles that go above 100mph, it&rsquo;s called High Speed Rail! They literally exist and literally go above 100mph. <a href="https://knowyourmeme.com/memes/i-feel-like-i-m-taking-crazy-pills"target="_blank" rel="noopener noreferrer">I feel like I&rsquo;m taking crazy pills!</a>
</p>
<h2 id="los-angeles">Los Angeles</h2>
<blockquote>
<p>In Los Angeles during the age of streetcars, a fire anywhere in the city would result in water hoses crossing the street from hydrant to firetruck, and then the network ground to a halt because steel wheels can’t cross a hose or surmount a temporary hump!</p>
</blockquote>
<p>Perhaps this is historically true, but there are pretty easy fixes to this. You can just put in more fire hydrants, or stop a streetcar if it&rsquo;s too close to a fire. Heck, you should probably do that anyways for safety reasons.</p>
<p>Also, the number of fires fought per year by fire fighters per year has been <a href="https://www.vox.com/2014/10/30/7079547/fire-firefighter-decline-medical"target="_blank" rel="noopener noreferrer">dropping</a>
for a while now. Part of the reason why they&rsquo;re always at car crashes is because we&rsquo;ve trained them as paramedics to give them something to do. I personally don&rsquo;t think we should adjust the transit mechanism for an entire city soley because we&rsquo;ll have to ocasionally stop one line in the case we end up having to fight a fire despite fires being drastically less common nowadays.</p>
<blockquote>
<p>Building a metro system in an existing dense city is also great (if we can avoid cost disease) but for most of the cities in the US, the suburbs are already not walkable enough to enable non-vehicle transport to a neighborhood station. The suburbs of LA will never be able to depend on a Manhattan or Vienna-style underground railway.</p>
</blockquote>
<p>&hellip; You were literally just talking about the streetcar network LA had previously? I don&rsquo;t see why we can&rsquo;t just &hellip; rebuild that. Especially since it&rsquo;s not like it wasn&rsquo;t popular beforehand, <a href="https://en.wikipedia.org/wiki/General_Motors_streetcar_conspiracy"target="_blank" rel="noopener noreferrer">it was purchased and sabotaged by car companies on purpose</a>
.</p>
<h2 id="japan">Japan</h2>
<blockquote>
<p>Add to that various Japanese prohibitions on certain weapons technology in the post war period and high speed rail served as a government imposed solution to mass transportation.</p>
</blockquote>
<p>It&rsquo;s a minor thing, but trains are critical military infrastructure, we&rsquo;ve just forgot that. JNR was literally taken over by the Japanese military during WW2. The US nationalized the rail roads in WW1. The US army still has a MOS for driving a train, 88U.</p>
<p>Even if you&rsquo;re an island nation, the ability to move people around quickly and cheaply has obvious military implications.</p>
<blockquote>
<p>Japan and much of China is relatively mountainous, historically relatively poor, and historically beset by relatively poor transport networks.</p>
</blockquote>
<p>&hellip; But I thought the argument was that HSR is too expensive and doesn&rsquo;t work wherever the earth isn&rsquo;t that flat? You can&rsquo;t have it both ways here, either it&rsquo;s inherently expensive, or it&rsquo;s the choice of poor countries that can&rsquo;t afford a lot of air and car travel. It can&rsquo;t be both.</p>
<h2 id="road-cost">Road Cost</h2>
<blockquote>
<p>For example, the I-70 cost an average of about $2m/mile, despite routing through remote and mountainous parts of Utah</p>
</blockquote>
<p>No way. Here are three major pieces of infrastructure along that road, inflation adjusted to 2020 dollars.</p>
<ul>
<li>Eisenhower tunnel bore: $490m</li>
<li>Johnson tunnel bore: $384m</li>
<li>Glenwood Canyon: $828 m</li>
<li>San Rafael Swell: $1.3B</li>
</ul>
<p>These sum up to $3B, which leaves a measily $1B for the <em>rest of the highway</em>, or an impossible $450K per mile. These must be 1950 dollars.</p>
<p>A 2011 <a href="https://westdavis.udot.utah.gov/wp-content/uploads/2019/10/TM16_Level_2_Screening_Cost_Estimates-0.pdf"target="_blank" rel="noopener noreferrer">memorandum</a>
on the West Davis corridor project estimated $8M per mile of new four lane highway, $10M per five lane arterial, and $19M per interchange. Florida DOT <a href="https://www.fdot.gov/programmanagement/estimates/documents/costpermilemodels"target="_blank" rel="noopener noreferrer">estimates</a>
that a new 4 lane divided interstate costs $6M a mile in rural areas, and $13M in urban areas. And Florida doesn&rsquo;t really have mountains. No way you&rsquo;re getting a highway through that kind of terrain for $2M a mile in 2020 dollars.</p>
<p>People drastically underestimate how much roads cost.</p>
<h2 id="cost-overrun">Cost Overrun</h2>
<blockquote>
<p>The vast majority of this is unfunded, and yet the final project will almost certainly cost at least 10x this if it ever completed</p>
</blockquote>
<p>I agree that this project is overly expensive, but now you&rsquo;re just making numbers up.</p>
<h1 id="conclusions">Conclusions</h1>
<p>Train good. Faster train better.</p>
<section class="footnotes" role="doc-endnotes">
<hr>
<ol>
<li id="fn:1" role="doc-endnote">
<p>The first draft said &ldquo;ealier today&rdquo;. That was an optimistic assumption on my part about how long this would take to write.&#160;<a href="#fnref:1" class="footnote-backref" role="doc-backlink">&#x21a9;&#xfe0e;</a></p>
</li>
<li id="fn:2" role="doc-endnote">
<p>With some very basic back of the envelope estimates, track construction should cost anywhere between $8.4B and $37B based on historical estimates of European HSR construction, with another few billion for stations and rolling stock. Instead it&rsquo;s going to cost $113B, or about three times too much.&#160;<a href="#fnref:2" class="footnote-backref" role="doc-backlink">&#x21a9;&#xfe0e;</a></p>
</li>
<li id="fn:3" role="doc-endnote">
<p>There is no way this post can be considered &ldquo;concise&rdquo;&#160;<a href="#fnref:3" class="footnote-backref" role="doc-backlink">&#x21a9;&#xfe0e;</a></p>
</li>
<li id="fn:4" role="doc-endnote">
<p>Even using inflation alone is somewhat suspect. Inflation generally measures the change in price for a &ldquo;basket of goods&rdquo; that end users are price sensitive for. Milk, meat, housing, gasoline, etc. While a lot of this does affect construction costs (workers need to afford food and housing, etc.), they are not directly linear. Similarly steel costs do not directly affect consume good prices, but indirectly. None of this also accounts for improvements in productivity. Just because something cost $X dollars in 1950 does not mean it&rsquo;ll cost $X inflation adjusted now if we&rsquo;re using more efficient machines and techniques. But we&rsquo;ve gotta do something to compare numbers, and I don&rsquo;t see a better tool available.&#160;<a href="#fnref:4" class="footnote-backref" role="doc-backlink">&#x21a9;&#xfe0e;</a></p>
</li>
<li id="fn:5" role="doc-endnote">
<p>This is probably a partial explanation for why China has built so much HSR.&#160;<a href="#fnref:5" class="footnote-backref" role="doc-backlink">&#x21a9;&#xfe0e;</a></p>
</li>
<li id="fn:6" role="doc-endnote">
<p>Personally I think the EU&rsquo;s definition structure makes sense, although I would fiddle with the numbers a bit. I think that defining HSR as only being above 250kph/155mph leaves us with the rather unsatisfying situation of considering both a 125mph interurban and a 60mph urban metro as being equivalently slow. I would&rsquo;ve made Category I the slowest, and Category III the fastest, which makes adding Categories IV and V trivial if we make faster rail one day. I don&rsquo;t think categorizing a 250kph TGV and the 431khp Shanghai maglev as both being equally &ldquo;Category I&rdquo; feels correct.&#160;<a href="#fnref:6" class="footnote-backref" role="doc-backlink">&#x21a9;&#xfe0e;</a></p>
</li>
<li id="fn:7" role="doc-endnote">
<p>They also define &ldquo;very high speed rail&rdquo; as peaking over 250kph and averaging 200kph.&#160;<a href="#fnref:7" class="footnote-backref" role="doc-backlink">&#x21a9;&#xfe0e;</a></p>
</li>
<li id="fn:8" role="doc-endnote">
<p>Indeed, once we define HSR as 250kph and above we end up with 21 countries with operating service, 9 actively building or upgrading lines, 8 planning, and another 3 with plans that are currently on hold.&#160;<a href="#fnref:8" class="footnote-backref" role="doc-backlink">&#x21a9;&#xfe0e;</a></p>
</li>
<li id="fn:9" role="doc-endnote">
<p>Airports are fundamentally a nuisance, so there are practical, political limits on where they can be placed. In all but one of the cities I&rsquo;ve lived in it took an average of an hour or more to get from my house to the airport door. The worst was LAX, by far. Generally the smaller the airport the better, but alas these also represent a proportionally small percentage of travel miles.&#160;<a href="#fnref:9" class="footnote-backref" role="doc-backlink">&#x21a9;&#xfe0e;</a></p>
</li>
<li id="fn:10" role="doc-endnote">
<p>Some of these could be improved, but my suspicion is that most are inherent. Nothing is going to move LAX to a more convenient location, and there are several profit-motivated actors involved that want to minimize these delays so that they can sell more tickets and move more people with the same infrastructure spend. If Southwest cannot get the turnaround time down further, then there is probably very little room for improvement.&#160;<a href="#fnref:10" class="footnote-backref" role="doc-backlink">&#x21a9;&#xfe0e;</a></p>
</li>
<li id="fn:11" role="doc-endnote">
<p>Which comes out to 150mph. Presumably if America used metric they would&rsquo;ve gone with 250kph, since people do love nice round numbers.&#160;<a href="#fnref:11" class="footnote-backref" role="doc-backlink">&#x21a9;&#xfe0e;</a></p>
</li>
<li id="fn:12" role="doc-endnote">
<p>This is not a typo.&#160;<a href="#fnref:12" class="footnote-backref" role="doc-backlink">&#x21a9;&#xfe0e;</a></p>
</li>
<li id="fn:13" role="doc-endnote">
<p>Also, methane isn&rsquo;t jet fuel.&#160;<a href="#fnref:13" class="footnote-backref" role="doc-backlink">&#x21a9;&#xfe0e;</a></p>
</li>
<li id="fn:14" role="doc-endnote">
<p>Personally I think that if you&rsquo;re creating methane from atmospheric carbon, the best thing you can possibly do is bury it rather than burning it again and potentially leaking some. Methane has a warming potential about 80X of CO2 over the first 20 years, so if you leak more than 1/80th (1.25%) of the produce methane, you&rsquo;re actually making the situation worse. Leaking methane from power and home heating is actually a big issue, we should do something about that.&#160;<a href="#fnref:14" class="footnote-backref" role="doc-backlink">&#x21a9;&#xfe0e;</a></p>
</li>
<li id="fn:15" role="doc-endnote">
<p>JR Central claims that the Shinkansen beats air travel for the same route by a factor of 1:8 per MJ and 1:12 for CO2 per seat. If we adjust for the non-CO2 warming of jet travel it&rsquo;s 1:24 or higher. Even using synthetic fuels captured from atmospheric carbon doesn&rsquo;t move the ratio beyond 1:12.&#160;<a href="#fnref:15" class="footnote-backref" role="doc-backlink">&#x21a9;&#xfe0e;</a></p>
</li>
<li id="fn:16" role="doc-endnote">
<p>God, I love the metric system.&#160;<a href="#fnref:16" class="footnote-backref" role="doc-backlink">&#x21a9;&#xfe0e;</a></p>
</li>
<li id="fn:17" role="doc-endnote">
<p>Especially since the alternative more often than not is just highways.&#160;<a href="#fnref:17" class="footnote-backref" role="doc-backlink">&#x21a9;&#xfe0e;</a></p>
</li>
<li id="fn:18" role="doc-endnote">
<p>The TGV Duplex highlights the flexibility of rolling stock design, because it uses a mix of refurbished TGV Réseau carriages and Euroduplex carriages.&#160;<a href="#fnref:18" class="footnote-backref" role="doc-backlink">&#x21a9;&#xfe0e;</a></p>
</li>
<li id="fn:19" role="doc-endnote">
<p>Maximum theoretical configuration. This train is not yet in operation. The TGV M features a modular interior, and is designed to run with anywhere between 7 and 9 carriages. Most will be smaller than this.&#160;<a href="#fnref:19" class="footnote-backref" role="doc-backlink">&#x21a9;&#xfe0e;</a></p>
</li>
<li id="fn:20" role="doc-endnote">
<p>I do not have 2019 numbers available, but 2018 was smaller than 2021 in terms of total passengers, so I think this number is safe to use.&#160;<a href="#fnref:20" class="footnote-backref" role="doc-backlink">&#x21a9;&#xfe0e;</a></p>
</li>
<li id="fn:21" role="doc-endnote">
<p>The minimum safe headway of a rail system is determined by signal design, driver reaction speed, and vehicle braking performance. This is part of the rationale for a maglev train, which can accelerate at higher speeds and therefore can reduce the minimum safe headway and travel time. The L0 maglev train should take a bit under 4 minutes to hit 603 kph, while the N700S takes 3 minutes to hit 270kph.&#160;<a href="#fnref:21" class="footnote-backref" role="doc-backlink">&#x21a9;&#xfe0e;</a></p>
</li>
<li id="fn:22" role="doc-endnote">
<p>Then again, I&rsquo;m writing this note at 3:42AM for largely similar reasons.&#160;<a href="#fnref:22" class="footnote-backref" role="doc-backlink">&#x21a9;&#xfe0e;</a></p>
</li>
<li id="fn:23" role="doc-endnote">
<p>The original paper did not make it clear what kind of train it was, but given the very low max speed I suspect it&rsquo;s steam.&#160;<a href="#fnref:23" class="footnote-backref" role="doc-backlink">&#x21a9;&#xfe0e;</a></p>
</li>
<li id="fn:24" role="doc-endnote">
<p>The lifecycle for HSR appears to be about 25 to 30 years for high speed service. Sometimes older models are refurbished and reused for slower or less important routes.&#160;<a href="#fnref:24" class="footnote-backref" role="doc-backlink">&#x21a9;&#xfe0e;</a></p>
</li>
<li id="fn:25" role="doc-endnote">
<p>This implies that driving by road might be more energy efficient once a car has two to three people in it, which seemed counterintuitive to me. The Sierra Club had a <a href="https://www.sierraclub.org/sierra/ask-mr-green/whats-better-for-environment-driving-or-flying"target="_blank" rel="noopener noreferrer">Q&amp;A</a>
about this and seem to largely agree with this assertion though. They also then argued for hitch-hiking, because you know, it&rsquo;s the Sierra club.&#160;<a href="#fnref:25" class="footnote-backref" role="doc-backlink">&#x21a9;&#xfe0e;</a></p>
</li>
<li id="fn:26" role="doc-endnote">
<p>Since 2009 several narrow body jets have converted to the more efficient CFM Leap engine, including the A320-neo and the infamous 737 MAX series. Airbus claims 15-20% lower full burn for the A320-neo, and Boeing claims 14% less than the previous 737NG. Applying these numbers gets us anywhere between 1.44 and 1.53.&#160;<a href="#fnref:26" class="footnote-backref" role="doc-backlink">&#x21a9;&#xfe0e;</a></p>
</li>
<li id="fn:27" role="doc-endnote">
<p>Personally I think &ldquo;free&rdquo; is the wrong way to view the interaction between authors and their readers. Both of us are writing blogs to persuade people and convince our readers that we&rsquo;re smart people who have good ideas; we both get something out of this, even if it&rsquo;s not money.. I think that part of this interaction is that authors should try and exercise diligence when writing, and correct honest mistakes when they&rsquo;re pointed out. We owe our readers some level of rigor even they&rsquo;re not paying us.&#160;<a href="#fnref:27" class="footnote-backref" role="doc-backlink">&#x21a9;&#xfe0e;</a></p>
</li>
<li id="fn:28" role="doc-endnote">
<p>There exist one maglev train in operation, and one seriously being constructed. The one in use is a relatively short line between Shanghai and its airport. Cool, but not that impactful. The interesting one is the Chūō Shinkansen, which is being built. JR Central is spending a gobsmacking amount of money on this, and I have no clue why, since to my amateur eye I don&rsquo;t think regular HSR wouldn&rsquo;t work. But it&rsquo;s not my money, and I personally really love the &ldquo;dudes rock&rdquo; energy they&rsquo;re showing here.&#160;<a href="#fnref:28" class="footnote-backref" role="doc-backlink">&#x21a9;&#xfe0e;</a></p>
</li>
<li id="fn:29" role="doc-endnote">
<p>The correct number seems to be 19,920, although the data on the smallest airports appears to be kind of sketchy. I am assuming his number is old, but this correction strengthens his argument.&#160;<a href="#fnref:29" class="footnote-backref" role="doc-backlink">&#x21a9;&#xfe0e;</a></p>
</li>
<li id="fn:30" role="doc-endnote">
<p>This excludes commercial pilots. I feel like including them is a bit like including train operators or taxi drivers in this analysis: their means of transit is drastically affected by their chosen vocation to the point where it&rsquo;s not representative of the general population. Also, there is no guarantee that commercial pilots own their own planes for use in general aviation airports.&#160;<a href="#fnref:30" class="footnote-backref" role="doc-backlink">&#x21a9;&#xfe0e;</a></p>
</li>
<li id="fn:31" role="doc-endnote">
<p>Casey has indicated that he is a pilot, so he has access to all these airports. Which, good for him! More than once I&rsquo;ve dreamed about getting my own license and plane, and I&rsquo;m sure it&rsquo;s nice to hop in your plane and travel without having to deal with traffic and what not. But the percentage of the US population who can reasonably do this is so small, I do not think it&rsquo;s fair or reasonable to include it in a comparison between HSR and air travel.&#160;<a href="#fnref:31" class="footnote-backref" role="doc-backlink">&#x21a9;&#xfe0e;</a></p>
</li>
<li id="fn:32" role="doc-endnote">
<p>In general I think it&rsquo;s a mistake to compare private owner-operated general aircraft to mass transit, because these planes are really more about enjoyment than practical transit. You buy and operate a plane because you like flying, not because it&rsquo;s necessarily an efficient way to get around. Owning a plane involves a lot of fixed costs, and you have to fly a lot of hours before the per hour cost gets under control. But since this is about comparing things, I do feel compelled to point out that these planes are pretty danged slow compared to scheduled air service or HSR. There are indeed general avitaion planes that can outrun HSR, like the Mooney M20 (278 mph cruise) or the Cirrus SR22 (211mph), but the vast majority of private planes are going to be your used Cessna 172s and Piper Cherokees, both of which top out around 140mph.&#160;<a href="#fnref:32" class="footnote-backref" role="doc-backlink">&#x21a9;&#xfe0e;</a></p>
</li>
<li id="fn:33" role="doc-endnote">
<p>According to the Bureau of Traffic Statistics, in July of 2022 there were 467,000 non-scheduled flights, and 80,360,000 scheduled flights. Similarly over the 12 months ending in July of 2022 there were 4,421,000 non-scheduled flights and 808,627,000 scheduled flights. So non-scheduled flights represent 0.56% of overall flights. Revenue passenger miles show similar proportions. This is such a tiny percentage I feel ok in ignoring this type of flight and the airports that only serve it from our analysis.&#160;<a href="#fnref:33" class="footnote-backref" role="doc-backlink">&#x21a9;&#xfe0e;</a></p>
</li>
<li id="fn:34" role="doc-endnote">
<p>It also brings my personal travel record up to anywhere between 4-15% depending on whether on whether we&rsquo;re including nonhub and reliever airports or not. This feels much more intuitively correct.&#160;<a href="#fnref:34" class="footnote-backref" role="doc-backlink">&#x21a9;&#xfe0e;</a></p>
</li>
<li id="fn:35" role="doc-endnote">
<p>Communication tools like email and social media tend to show strong network effects.&#160;<a href="#fnref:35" class="footnote-backref" role="doc-backlink">&#x21a9;&#xfe0e;</a></p>
</li>
<li id="fn:36" role="doc-endnote">
<p>Factorial, not a generic explanation mark.&#160;<a href="#fnref:36" class="footnote-backref" role="doc-backlink">&#x21a9;&#xfe0e;</a></p>
</li>
<li id="fn:37" role="doc-endnote">
<p><a href="https://www.iflyboise.com/travel-planner/nonstop-destinations/"target="_blank" rel="noopener noreferrer">Here</a>
is the map.&#160;<a href="#fnref:37" class="footnote-backref" role="doc-backlink">&#x21a9;&#xfe0e;</a></p>
</li>
<li id="fn:38" role="doc-endnote">
<p>This is precisely the case I made at the beginning of this article. Not every pair of cities makes sense to connect via HSR. Your basic passenger train could trivially outrun cars on this route, and even with stops in between. The MPI MPXpress used by the Chicago Metra maxes out at 102 mph, and could do an express run in about half as long as a car can. Oh, and it was made in Boise, the irony.&#160;<a href="#fnref:38" class="footnote-backref" role="doc-backlink">&#x21a9;&#xfe0e;</a></p>
</li>
<li id="fn:39" role="doc-endnote">
<p>The effective result of not having even regular speed rail offerings in the US is that a lot of trips get shifted from mass transit to individual vehicles. This has a lot of downsides that are not immediately obvious, including increased road deaths and health costs associated with road air pollution. While we will never be able to get these numbers down to zero, there is an argument that creating transit options that reduce car miles travelled would pay for itself in the reduced externalities of excess road miles. But that&rsquo;s the subject for another post.&#160;<a href="#fnref:39" class="footnote-backref" role="doc-backlink">&#x21a9;&#xfe0e;</a></p>
</li>
<li id="fn:40" role="doc-endnote">
<p>The one offered by the defunct B&amp;O, not the Amtrak line of the same name. Amtrak does not offer the branch service to Youngstown.&#160;<a href="#fnref:40" class="footnote-backref" role="doc-backlink">&#x21a9;&#xfe0e;</a></p>
</li>
<li id="fn:41" role="doc-endnote">
<p>Consider how small Charles De Gaulle airport is, for example. It&rsquo;s only the 31st busiest airport in 2021, despite it serving the largest metro in Europe and being one of the most visitied cities in the world. And sure, you expect cities like Delhi Beijing to be busier, but what&rsquo;s shocking is how many American airports are busier. Charlotte North Carolina saw 20 million more passengers than Charles De Gaulle did. Oh, and CDG was unbelievably cheap to construct, too. Inflation adjusted it only cost $1.4B. Denver International Airport cost 6x as much, and it was made in an empty field outside of Denver rather than in Europe&rsquo;s biggest city.&#160;<a href="#fnref:41" class="footnote-backref" role="doc-backlink">&#x21a9;&#xfe0e;</a></p>
</li>
<li id="fn:42" role="doc-endnote">