Looking for some consultants for a possible PicoLisp prototype of a blockchain. 
It’ a collaboration between  a Swiss cantons and one of the large US States. 
Think cowboys… lol. 

At this point I’m checking bill rates and availability. Anyone on the GSA 
pre-clear list by chance?

Cheers,
Alex Ross
PMO Lead
us.new
+1.213.500.5925


> On May 7, 2021, at 10:02, A. Laszlo Ross <m...@laszlo.xyz> wrote:
> 
> Oh, wow, I didn’t know there was a PilOS. I’m a picolisp noob but that might 
> be perfect for an upcoming IoT type project.
> 
> The web page said there’s no network stack so I’d have to add that. 
> 
> Is it written in C? Assembly? Something else?
> 
> 
> 
>> On May 7, 2021, at 09:52, Daniel Perron <61du...@gmail.com> wrote:
>> 
>> 
>> Thank you for the precisions and Picolisp, it is a very nice system.
>> 
>> On Fri, May 7, 2021, 12:11 AM Alexander Burger <a...@software-lab.de 
>> <mailto:abu@software-labde>> wrote:
>> Hi Daniel,
>> 
>> > In that case, what is the status of Picolisp 32-bit?
>> > I read in the doc in many places "64-bit version only". Is Picolisp 32-bit
>> > deprecated?
>> 
>> All PicoLisp versions except pil21 (e.g. pil32, pil64, miniPicoLisp, 
>> ErsatzLisp,
>> PilMCU and PilOS) are still around, but I don't actively maintain them any 
>> more.
>> 
>> 
>> > If so, it creates a cognitive dissonance in my mind. A system
>> > created to be small and fast runs only on 64-bit?
>> 
>> I believe this is no contradiction. The system is still small and fast, just 
>> the
>> pointer size is 64 instead of 32 bits.
>> 
>> The trend is towards 64 bits, in servers, desktops, notebooks, smartphones 
>> and
>> even single-board computers (RasPi). Only small embedded systems remain, and
>> there just miniPicoLisp makes sense.
>> 
>> BTW, the "pico" in the name never meant the system size (you can build large
>> applications with PicoLisp), but the small number of basic concepts.
>> 
>> ☺/ A!ex
>> 
>> -- 
>> UNSUBSCRIBE: mailto:picolisp@software-lab.de 
>> <mailto:picolisp@software-lab.de>?subject=Unsubscribe

Reply via email to