Hi Alex,
>> It appears to me that it's significantly more relevant then any bsd
>> or sparc ports.
Funny, yeasterday I hit upon the dietlibc:
Why not port the diet libc to *BSD?
- The BSD people are responsible for three thirds of the broken APIs
that plague Unix today. The rest can be blamed on Sun.
> When talking about "interesting segments", I meant that the major
> battlefields these days are either in the smartphones and tablet area,
> with server (cloud) systems, or - traditionally (also in terms of
> sheer numbers), but largely unnoticed by the consumer - embedded
> systems. The desktop is losing importance.
Maybe but I am not sure.
> Especially for embedded systems PicoLisp might still have unexplored
> potential (right, Jakob?), but also for distributed databases.
Speaking of embedded systems, have you though about linking picolisp
statically and maybe with dietlibc? That might make picolisp even more
pico. I tried dietlibc yesterday with one of my utility programs and
the result is beautifully minimal.
Cheers,
Tomas
--
UNSUBSCRIBE: mailto:[email protected]?subject=Unsubscribe
