Being two separate tunnels, it also needs twice as much excavation work. It's also ~25x deeper than Toei Oedo (4000ft vs 157ft). At 4000ft the rock itself is 45-50C!
> Being two separate tunnels, it also needs twice as much excavation work.
Yet another great point. At some of the Toei Oedo stations, you can see a miniature model of the weird overlapping twin tunnel boring machines. So, in theory it is two tunnels, but in practice, it was dug as a single, weird overlapping twin tunnel.Kanto is flat, it's the only region in Japan that could sustain feeding such a massive population and could allow building the first mega city on the planet.
Combine that with the massive engineering and rail experience Japanese have, and it's no surprise imho that combined with favorable geography they could build it quickly.
[1] https://upload.wikimedia.org/wikipedia/commons/2/28/Topograp...
Does that term have special meaning in the AI/LLM world? I never heard it before. I Google'd the term "System Card LLM" and got a bunch of hits. I am so surprised that I never saw the term used here in HN before.
Also, the layout looks exactly like a scientific paper written in LaTeX. Who is the expected audience for this paper?
How is there no unifying design language for these?
... it looks like a multi-multi-multi-phase project. Hats off to making this work.
Second, I noticed how long it took to build this tunnel: Koralm Tunnel -> https://en.wikipedia.org/wiki/Koralm_Tunnel
It is 33km, and it took from 2008 to 2025 to build it. That is a damn long time! The Toei Oedo line in Tokyo is 40+km and was built in about 10 years. My guess about the wild difference: The geoengineering of the Koralm Tunnel is way more complex, and/or the rock is much harder. Can anyone with experience in this area comment? I would like to learn more. I guess that most of central Tokyo is aluvial plains (Shanghai is similar), so you are basically digging through clay and sand -- easy stuff for modern tunnel boring machines.
> disliking exceptions seemed crazy then but it's pretty normal now
Help me to clarify. Are you saying that when Joel posted (~20 years ago), disliking exceptions was considered crazy? And, now it is normal to dislike exceptions?Assuming that my interpretation is correct, then I assume that you are a low level systems programmer -- C, C++, Rust, etc? Maybe even Golang? If you are doing bog standard enterprise programming with Python, Java or C#, exceptions are everywhere and unavoidable. I am confused. If anything, the last 20 years have cemented the fact that people should be able to choose a first class citizen (language) that either has exceptions or not. The seven languages that I mentioned are all major and have billions of lines of legacy code in companies and open source projects. They aren't going anywhere soon. C++ is a bit special because you can use a compiler flag to disable exceptions... so C++ can be both. (Are there other languages like that? I don't know any. Although, I think that Microsoft has a C language extension that allows throw/catch!)
Was this a local model?
> It is the year 2035. The average "Hello World" application now requires 400MB of JavaScript, compiles to a 12GB WebAssembly binary, and runs on a distributed blockchain-verified neural mesh. To change the color of a button, we must query the Global State Singularity via a thought-interface, wait for the React 45 concurrent mode to reconcile with the multiverse, and pay a micro-transaction of 0.004 DogeCoin to update the Virtual DOM (which now exists in actual Virtual Reality).
This is all too realistic... If anything, 400MB of JS is laughably small for 2035. And the last time I was working on some CI for a front-end project -- a Shopify theme!! -- I found that it needed over 12GB of RAM for the container where the build happened, or it would just crash with an out-of-memory error.
> And the last time I was working on some CI for a front-end project -- a Shopify theme!! -- I found that it needed over 12GB of RAM for the container where the build happened, or it would just crash with an out-of-memory error.
This sounds epic. Did you blog about it? HN would probably love the write up!