What's the intersection between future of coding and distributed computing? I'll go first: unison and t2tile, are there more?

... not as concrete as your examples ... I argue that programming becomes much easier when synchrony is expunged --> FoC, distributed, visual, etc, etc. [more discussion](https://guitarvydas.github.io/2022/04/11/Future-of-Programming-Distributed-Programming-Visual-Programming.html)

I would like HTTPS://webcode.run to be the running, but it's true ambitions are not obvious yet, but the point is a federated inside-out compute platform. Bring the compute to the data type thing using the portability of the web.

Does Ethereum qualify? There was also a cool demo posted here about a year ago that was a programming model for the future era of computers that are like a swarm/grains of sand. I thought it was called something like Horde Computing but I can't find it now 😕

ethereum runs the same computation in many nodes for security/consistency, I'm looking for languages that make it easy to distribute and scale computation

Ethereum: Enabling massively synchronous computing!

Mech!

Thank you @Mariano Guerra for tapping into that context and bringing up the question. @wtaysom the blockchain people are actually coming around, acknowledging the poor idea of 1 global blockchain/sync computer for all things for all human beings. In recent years more and more sharding solutions are implemented you can see that with polkadots parachain model, Cosmos, RChain , Cardano, even in the Ethereum Ecosystem there are are many "satelite" Efforts like Gnosis Chain. These Efforts point not only to technical difficulties but in my opinion its a cultural thing. Human beings are not like a global bee hive cluster, or bork cluster for that matter. We have distinct cultural and local history backgrounds. We are still looking for ways to express this with technology and its accompanying patterns of behaviour ( what seymour papert called computing cultures)

Apologies for just dropping yet another perspective and self-promo in here without reference to what's already been written, but... 😄 ... my own project (the http://Object.Network ) has two core attributes: Declarativeness and Decentralisation which I think correspond to these two elements in the OP (FoC and Distributed). Both capital-"D"s derive from a single deeper concept: the Big Inversion 😮 That basically entails turning the current, pervasive "code-on-the-outside-data-on-the-inside" programming model inside out: thus "data-on-the-outside-code-on-the-inside". This means data is freed from the traps of Imperative, Service-Oriented architectures. And the opposite of an Imperative, Service architecture? A Declarative, Decentralised architecture, of course! In this programming model, you see and interact with data first - before functions, like in a spreadsheet; it has "internal behaviour" (Declarative). Imperative is "how over what"; Declarative is "what over how" - the detailed mechanisms of behaviour are hidden behind a declaration - i.e., more data - of the required behaviour. It's basically like a virtual world of data - if you enter Minecraft, you see stuff before you see its behaviour - things are internally-animated. In the Object Network, all our stuff is sewn together into a kind of Metaverse, using links between data chunks. Data is held locally (Decentralised), so that we have full control over it, instead of imperative data-wrapping, techie programs and Big Tech services.

Nice 👍 looks quite in line with https://twitter.com/Gilad_Bracha/status/1516531127405584391