3 ms·
focus on syntax / macros / CL packages - maybe make a 2-layer set of macros/functions to translate urls, deal with terminal IO (you can hook up a TTY to a web
by cat199 9y ago
focus on syntax / macros / CL packages -
maybe make a 2-layer set of macros/functions to translate urls, deal with terminal IO (you can hook up a TTY to a web server simply), and store the results to a simple assq-on-disk affair, the rest will come later. get this, then asdf and gen executable; you can run multiple lib copies in cl packages and don't need them in production anyway, so global folder isn't important; that said you can customize quicklisp install.. write a macro to do this for you for pratice lol :)
the power is in the lisp language & syntax extension, not reproducing 'npm install foo' using native calls and getting frustrated that the ecosystem is smaller
excuse snarky tone, simply typing quickly
- cat199 9y agoalso, if you aren't using commercial lisp, use emacs. really. though it's the editor war, lisp-based-emacsen were written simultaneously with the lisp machines by the same people .. lisp+emacs grew together like c+unix; which is also a good analogy since it is really another world, best to throw out all baggage if you can..