Re: why not enough lisp libraries?

From: David Steuber (david_at_david-steuber.com)
Date: 02/25/05 

Date: 24 Feb 2005 18:02:39 -0500

"lisplover" <lisplover@hotmail.com> writes:

> But what happends if I want to communicate with the outside world
> for, say, TCP/IP, Multimedia, GUI, ,OpenGL, etc? I have to use
> layers, such as uffi, to call functions writtend in other
> languages. I feel this kind of unsmoothness is ugly, given such a
> elegant idear originated in John McCarthy's LISP.

What do the Perl, Python, Tcl, etc programmers do? I suspect they
have to link to code written in other languages. Ok, Perl has TCP/IP
built in. But that is built directly on C code.

I'm sure things have improved, but the last time I saw Java doing 3D
graphics, it was slooooooooow. Using FFI to access OpenGL does work,
can be abstracted to look smooth, and can be fast.

As for GUI, I am not too displeased with the code I have to access
Carbon's API. It certainly isn't as ugly as C++ code would be. 

-- 
An ideal world is left as an excercise to the reader.
   --- Paul Graham, On Lisp 8.1

Relevant Pages

  • Re: Is GLUT outdated?
    ... Are GLUT even used anymore? ... If all you want to do is display something in OpenGL ... with the most minimal of GUI, ... There are lots of other GUI systems either built for, ...
    (comp.graphics.api.opengl)
  • Re: wxWidgets
    ... Look at OpenGL, glut and SDL for ... GUI work with it and find it to be ... I tried wxWidgets and it just kept crashing on its own GUI code so I gave up ... > but an OpenGL extension is available for it, ...
    (comp.programming)
  • Re: GUI toolkits
    ... There is a quite powerful gui ... - Qt is slow if you excesively use lots of widgets. ... Going back on topic - some pure OpenGL GUI libs: ...
    (comp.graphics.api.opengl)
  • Re: Macro lambda list
    ... > GUI on OpenGL and OpenAL and you didn't. ... Or is it because you do Java ... The kind of meds *I* prefer come from dubious people with large shiny ...
    (comp.lang.lisp)
  • Re: Connect Windows Forms GUI to a C code which is serving as a back end
    ... Do you mean you're using TCP/IP to literally communicate between two components on the same computer or is there a chance that the GUI and C code are going to be on different computers? ... It sounds like a C++/CLI project is what you need to perform the bridging, if you do actually need the TCP/IP connection then there are plenty of networking classes in the System.Net namespace that will make your life a lot easier. ... In this the C code is going to act as a server and the GUI the client ...
    (microsoft.public.dotnet.framework.windowsforms.controls)