An idea that may or may not be terrible, written down so I can get it out of my head and into someone who can do something about it.
What if we started from scratch with code represented as graphs, not text?
An idea that may or may not be terrible, written down so I can get it out of my head and into someone who can do something about it.
What if we started from scratch with code represented as graphs, not text?
@samir it wouldn't surprise me if #unisonLang represents code that way internally. It's certainly wrestling with escaping the same local optimum problem.
Logging has some interesting parallels. #DBus famously discarded text for its own proprietary binary format and now you can't read #Linux logs without using its tools.
@caoilte Oh, that’s interesting, I expect it’s very important to be able to convert to text to be able to use text-based tools such as grep.
I’m sure the Unison folk have thought really hard about this, and honestly, I hope they do it. They’re probably the most qualified people to tackle these kinds of problems.