What brought me to the future of programming space ... Hi, I am Lukas M Süss (aka mechadense) I guess for me my path to "future of coding" relevant topics was initially kicked off many years ago (2005 maybe?) when stumbling across a german website with name "C-hater in 10 days". Before I already had banged my head into the limitations of current day programing languages again and again. • First in the context of game programming, • and later in the context of 3D modelling. That was revelation one. Here the (german) page in the internetarchive: https://web.archive.org/web/20080612103719/http://www.math.uni-bremen.de:80/~thielema/CHater.html ) This eventually led me to taking a course about the haskell programming language and the theory behind it. What I learnd there was quite eye opening and my second revelation. _The (german) course: http://www.complang.tuwien.ac.at/knoop/fp185A03_ws2122.html — by Jens Knoop — at TU Vienna_ At some point when I came across diagramming sofware (then I used yEd) I sketched out all of what I've learned so far. Thereby realizing … • (A) … how far even Haskell is still improvable. — Revelation three. • (B) … how much can be learned by high level diagramming and how awesome it would be if that would fall out of a programming language I was starting to desire autopropagarion of renaiming, automatic code substitutions, and more … Desiring structured editing — basically. My fourth revelation was making the connection between John Tromps Lambda diagrams and textual code, leading to my work on "Annotated Lambda Diagrams (ALDs)". -- _http://apm.bplaced.net/w/index.php?title=Annotated_lambda_diagram_ I found that translating existing ideas into these diagrams greatly helps me in understanding them. Which makes me think that this may be a good "semitextual" programming interface. Now I'm in the process of investigating ideas-and-work of some great people in the context of ALDs ( Looking at ideas from: Conal Elliott, Jonathan Edwards, Cryus Omar et.al. , Daniel P. Friedman, ... ) All this as spare time efforts. My fifth and so far final revelation (during 2018) emergerd probably mostly from my frustration with nonexistence … • … of local-first selfhosting options. • … of personal local-first self-owned content curation assistents. I realized that in order for good novel technical solutions of core problems to thrive sociotechnical problems need to be solved in unison (unison the word not unison the proglang here). Code just cannot be borderlessly shared if there are no well designed means that allow for judement of its trustworthyness. What I want to see eventually are distributed ledgers that: • do not insist on maximally global public consensus for everything and • are nonmonetary at their core. Very few projects aim for that. In fact I only know one so far. — — — Regarding the "future of coding" side of my interests I'm into: • denotative core language design • content adressed design (datastorage and versioning) • dependent typing • agent centric design (sociotechnical aspect) • and what I missed here ... My core interest though is actually advanced atomically precise manufacturing (APM). Aimed at future gemstome-metamaterial-on-chip-factories. But if software does not get fixed I see a dark future ahead. Both for the path there and the eventual result.

I only know one so far.

Unison by any chance?

No … Well … I see the unison programming language as one of the most promising (if not THE most promising in it's core idea) approach on the non-social technical side. ~ What I'am eying on the sociotechnical side (and what I was referring to) is something like holochain. I think that holochain or something similar needs to be developed in unison (unison the word not unison the language) with good technical solutions including the ideas of unison (unison the language not the word). –– Sorry this got confusing. ~ If something like holochain would eventually somewhen be developed in unison (the language) that would be terrific. But that's decades away. ~ The other way around: Running unison code (or similar) on holochain (or similar) is also interesting, likely also quite far into the future, but still might happen sooner.

Hi @Miles Sabin nice to read from you here 🙂

@curious_reader I've read about radicle as a project aiming at a decentralizedly governed alternative to Microsoft github. This got me quite excited. But looking into it (I actually tried it out quite a while ago) I found that this still has ways to go for being a well usable alternative. I was not (or no longer?) aware of the relation between radicle and Gnosis Guild. I had a look at pi-calculus once. Seems rho-calculus builds onto that ... No clue about RChain though - might wanna look into that somewhen. What I'd like to see being built (and what I mostly was referring to with "sociotechnical") is fundamental core protocols for rule-carrying tamper-proof virtual distibuted "graph-database-like-filesystems" that at core are non-monetary and that can store large amounts of data (including video and such). Holochains distributed hash tables e.g. seem to promise that. Or something equivalent from an other project that too is not insisting on glogal consensus for everything. As of yet I don't know any such projects though … Without such protocols soon enough in place, when it comes to great projects on the futureOfCoding-technical side, like e.g. the unison programming language, I see issues coming up with spamming, malware, and the like. ( Especially once closed source SW gets supported and allowed in. Which is a when not a whether. ) The result being that artificial sandboxing "solutions" will need to be errected (again). And the necessity to (legitimately) get though these ad-hoc errected emergency walls may well introduce soul-crushing code-plumbing yet again. And that despite the situation that the language finally would actually be technically capable to allow for averting all these horrible code-plumbing efforts. As the vision goes: https://pchiusano.github.io/2013-05-22/future-of-software.html