This blog post walks through a substantial coding example in DAML, and draws some parallels to how the use case might need to be coded if using more traditional technologies (such as SQL). A really good read for anyone wanting to understand some of the rationale behind DAML. Get the code, download the SDK, and give it a whirl yourself. Would love your feedback!
Yes Edward was a big contributor here (full disclosure - I work at DA). A lot of our engineers, like Edward, come from the Haskell community. DAML uses the GHC compiler under the covers. One way to think of is is a GHC frontend that adds the extra bits required to streamline the task of writing multipartry contracts.
At this very moment, DAML applications run on the DA ledger. Open sourcing the language is the first step in expanding that base. We (yes, I work at DA!) have been working with key ledger providers and will be making additional announcements over time - perhaps starting within the month if all goes well.
So is the idea that it's abstracted from the ledger, basically meaning you have your choice of whether you would run it in some centralized ledger secured within your company or on a more blockchainey distributed ledger on the public internet?
I worked remotely for IBM for somewhere in the neighborhood of 15-20 years. Although I was effective and consistently a top performer, that's mainly because I could do a lot of my work autonomously. IBM's conference call mentality made meetings truly unproductive. Teaming on the phone is very hard.
I'm now with a startup and we use Zoom all the time, around the globe. Almost like being there.
Flying for meetings? fuggedaboutit! Totally unnecessary in my opinion.
