Discussion
As a visual language "Alonzo" will need its own version control, one that's guaranteed to not yield any syntax errors upon merge conflicts! Which would need to be fixed outside the editor, where it'd loose its usability benefits.
Thankfully modern compsci makes this fairly easy with CRDTs!
There'd still be merge conflicts, but it won't stop your Alonzo programs from rendering or even running!
Hmmm... Bespoke version control calls for bespoke codeforge. I'll leave it to others to design that!
Once I include exceptions in Alonzo (which I'd fold into my pattern-matching syntax) I suppose I could also use it for I/O errors, or build Functional-Reactive Programming upon it for richer interactivity. The issue with richer interactivity though is that it requires a larger vocabulary which cuts into the elegance I'm striving for.
---
Back to that version control... Once I have it, it'd be *easy* for me to apply it to any running Alonzo program. That could be extremely powerful!
3/3!
Install Fedizen
Get the full app experience
Also reading about this PHP vulnerability has me thinking about how my language would handle memory-allocation failures.
The trouble is that these errors hardly ever happen, so its a burden to ask even seasoned devs to constantly be wary of it.
I suppose I should incorporate exceptions?
A nice thing about this being a pure-functional language is that if you ignore the return value from a function, its errors are irrelevant...
2/3!