4 ms·
Yeah, that's why it's debatable.. Some maintainers do a better job than others, or only with a subset of the libraries they've made. I found your bug (and the g
by Jach 5y ago
Yeah, that's why it's debatable.. Some maintainers do a better job than others, or only with a subset of the libraries they've made. I found your bug (and the go-file-it-in-the-other-project non-response); in Shinmera's defense I'd want to be charitable and attribute most shortcomings to him devoting all his time to his video game.
One interesting advantage of Lisp (and dynamic languages in general, though Lisp's nicer) in cases like these is that if you can fix it yourself, it's easy to load the fix in. By that I mean, for example, suppose (I have no idea how this lib works) the lookup function has a pre-check on the string for invalid search characters before searching, but after inspecting the code you see no reason why it shouldn't work anyway. You can just jump to the code and edit the pattern or remove the error entirely, send the function to the REPL, and you're good to go. Save a copy in your own code if you need to persist your change. You could even do this while the debugger is active and not have to re-request the web page or lose whatever other state you'd built up until that point...
- robertlagrant 5y agoThat's extremely cool, but if Lisp is more like Putty than Lego, and you sort of have to mould all features for yourself rather than plugging in some blocks, then it will struggle in this area, I think. Having said that, I would love to use it more.