This article is not, in and of itself, particularly relevant to language documentation, as it deals with (a cool) programming language called Haskell. Haskell has the reputation of being a very cutting-edge, even difficult language.
There’s just one paragraph I’d like to draw your attention to (emphasis added):
In my opinion we should be making the same bet in language documentation. This is not to say that other programming languages — especially, for our community,
When the authors talk about “the massive investments in the language and platform,” the thing that stands out to me is the Document Object Model or
DOM. This is the thing that makes
This is a super weird idea, when you stop to think about it: web pages have
URLs, after all, and look like the they are “on” the server. But the code that makes a document interactive — that is, that turns it into something more like an application than a document — can run on your computer.
There are limits to this approach: a laptop is not a heavy-duty server with massive memory and disk space. So you wouldn’t want to try to distribute a massive database plus a program for accessing it directly to users’ browsers. But what I find interesting is that the definition of massive has been changing. It’s absolutely feasible to run medium-sized databases and accompanying code in this way. And in the early stages of language documentation of an undocumented or underdocumented language, every database is (by definition!) not massive. I believe we should keep exploring this programming environment in language documentation, it’s getting more powerful every day, not less powerful.