I just subscribed this minute...
> >There's embedding and there's embedding. Embedding in an UNIX server
> >is different than from embedding in a RTOS microcontroller.
We're getting very close to blurring the line between microcontrollers and servers.
In the next few years the palm tops will have the processing power you have right now,
if the tech stocks fly again it will be the wearables.
Over the past year I have developed a very firm model where the client loads a data
set, and then brings the tools to the data.
The tools are all in CPAN but I now see the packages coming to these small clients
from a controlled server as subsets of its modules as frozen
classes, evaled and then evolked when the data is comes or later when it suddenly
becomes needed.
Java already does some stuff like this, but perl is a better fit for these new
clients.
Since perl is a publically owned product, it is vastly more suited to the big chunk of
the world that is yet un-networked. It is much smaller,
flexible and lends to quick development and production. Unlike java.
My model calls for a close relationship between the OS and Perl.
Carrying this particular tourch has been painful, I must admit.
This wont be an either/or situation because of the modular structure.
http://puny.vm.com/cgi-bin/Depth/?depth=PerlOS
