I tried running my own but it turned out to be more complex than I was expecting (and desiring). I ended up paying a bit for a hosted server at ShockByte.
The idea of using a subset of an existing popular language is very wise IMHO. We can (and apparently are) debating the merits of the language runtime, but what a subset gives you is immediate access to a large pile of existing tooling that you'd have to write yourself, eg linters, formatters, lsps, etc. Stuff that is purely source-oriented.
You may well know this already, but the 2002 "Shackleton" miniseries starring Kenneth Branagh is a pretty faithful dramatisation of Alfred Lansing's book. Well worth a watch if you can get hold of it.
Indeed, Stonehenge is not much older. But given that, in human history, Egypt has always been an island of fertile land in a sea of desert, it's not so surprising that the area has persisted as a separate political, social and cultural entity, even when remembering that in fact it has constituted multiple kingdoms and dynasties over its history.
Egypt's greatest legacy is that its early history was so spectacular, and evidence of that is so visible today.
"Gin" is also an abbreviation for "engine", as applied to various machines during the industrial revolution. Eg, cotton gin. In that sense, it's quite a good name.
I think this may be a US thing. Fords built in Europe are pretty decent. Reliable (compared with most other makes), cheap parts and ubiquitous servicing. I've bought Fords (in the UK) for about the last 20 years and have in the main been very satisfied.
Punch cards are just text editors in primitive form though, ie columns across and lines down. All very 2D.
A visual programming canvas is free of that, and thus can display connections and relationships far more deeply and conveniently than text-based languages.
It's the 2D nature of our languages that has a lot to answer for.
A very long time ago I wrote an Eclipse plug in that would read from source comments an ascii diagram describing the state/transition flow of a java class object, and generate/update the necessary state fields and transition methods.
It was pretty cool in principle but nearly unworkable in practice, purely because maintaining an ascii diagram in a text editor for anything more than "Hello world" is a massive PITA.
The simple text editor has a lot to answer for when it comes to how we think about programming, in a Sapir-Whorf kind of way. It's a shame there has been no cast iron standard for mixing live text and visuals. Our industry might look very different.
"The right tools" in this case might presumably include, eg, a set of repos + docs and specs on the various technologies being used. Or a library of text/images and background docs on style and techniques use to create them.
That plus this model should give you a very powerful and focussed assistant.
Water depth in the Rove tunnel is 4m, and 12m in the Stad tunnel. They don't say at what state of the tide that is though, which I would have thought affects the size of ship that can pass through significantly (unless it has locks either end I suppose).
From Wikipedia:
Rove:
Length - 7,120 metres (23,360 ft) long
Clearance - 15 m (49 ft)
Width - 22 m (72 ft)