freenode/#clim - IRC Chatlog
Search
9:32:26
beach
Only possibility is to write your own parser for this (largely undocumented) markup language, re-create the structure that the standard processor uses, but differently and in a different language, and then write some output bytes.
9:33:15
beach
Imagine the kind of interesting documentation processor we could create if we had an internal protocol for that kind of stuff. A few lines of Common Lisp code could do interesting things to the document.
9:34:46
loke
I'm not sure the developer community as a whole would see the benefits of structured information.
9:35:16
beach
Now, if the #clim channel were logged in a useful way (i.e. not click on an arror for every 12 hours) I could figure out who wanted to work on this.
9:36:36
loke
jackdaniel: That's part of it. The problem was that the library in itself replicates a few characters of native javascript code. It's lik eme looking for a library on QL in order to convert a string to a symbol.
9:37:04
loke
jackdaniel: The problem with the removal was one aspect, but it was just highlighting the utterly dysfunctional NPM community as a whole.
9:37:27
loke
You are aware, I presume, of the existant of a library in NPM called isArray. Which does exactly what you think it does.
9:38:42
jackdaniel
and as far as I can tell, there is quite a lot of such systems (serapeum, clack - just grepped through my quicklisp/dists/quicklisp/software)
17:18:30
jackdaniel
some wise words about our reference backend :-) http://www.art.net/~hopkins/Don/unix-haters/x-windows/disaster.html
18:01:47
beach
jackdaniel: Heh! Be careful, you may get attacked the way I was in #lisp the other day. I guess maybe #clim is safer.
18:09:04
jackdaniel
I'm attacked every here and then (what's understandable in most cases, since I throw opinions sometimes above my background), but I learn to forget about them fast ;-)