> > Third, we have people who are experienced programmers who want to learn
> > Squeak at what I'll call the 'system level'. Typically these people arrive
> > on the list and have very specific questions about issues that are very
> > closely related to programming the metal, such as how to control sockets and
> > filestreams, different stack protocols, compiling the VM, etc. (As an aside,
> > it seems to me that a lot of the questions have to do with how to do this or
> > that under Linux. It's a shame that these technically savvy users are having
> > such a hard time just getting Squeak to run properly on their machines, more
> > or less actually program with Squeak. This is something that seriously needs
> > to be addressed).
> Sadly this problem is pretty endemic to anything to do with *nix and
> especially linux. There are so many configurations to cope with that it
> is amazing anything ever works. Even Mike Cowlishaw (probably one of the
> smartest software people there has ever been) has pretty much given up
> trying to get his software to work well on linux because of this. It's
> no reflection on the people that are trying to help either; there are
> just too many variables to cope with.
> 

Please, no excuses.  Lokisoft and Id are putting out plenty of software
on Linux despite all these variables.  Most open-source software
compiles and runs very easily on Linux, if it runs anywhere at all.

Squeak is below par on Linux.


-Lex