4 ms·
Got a better suggestion for writing I/O heavy Unix applications? I'd like to hear it.
by exDM69 15y ago
Got a better suggestion for writing I/O heavy Unix applications? I'd like to hear it.
- gouranga 15y agoLisp
- xyzzyz 15y agoSpeaking as a (Common) Lisp fan, Lisp is obviously hardly a good choice for Unix application -- it's completely orthogonal to Unix philosophy, and major modern free CL environments integrate pretty bad with Unix (I'm talking about SBCL and Clozure). It's especially bad for console tools like git, where loading multi megabyte core image every time is unacceptable.
- gouranga 15y agoOh I agree entirely. The real problem lies further up the stack - is UNIX the right solution?
- moonchrome 15y agoAnother irony in his statement that I didn't want to comment on seeing how the C one got most people pissed off enough.
- eru 15y agoOCaml would also work, if you can find the libraries. Or Haskell, if you can wrap your head around enumerator and iteratee IO. (Not saying that those are the best choices.) By the way, git was originally written in a mixture of C and shell-code. They replaced most of the shell code.