Just for fun: I cannot imagine Guido's email what if Alex will announce that he will stop pil21 and decide to port PicoLisp to WINDOWS and use .NET as official VM ^^
On Sun, Apr 19, 2020 at 7:24 AM <andr...@itship.ch> wrote: > Hey Guido! > > While I don't disagree with you in spirit (and I'm sure it's the same for > most of our community, we're a bunch of purist radicals), I have to > disagree with your tone. > > And i can assure you: My influence is **much bigger** than you might > think! Stop that, immediately! > > This is childish. You think we would part of this niche community (even > pico-tiny within the lisp culture) if such words would work on us? Think > again. > > We're not so much interested to convert anyone to our path by doing > missionary work - nice if it happens, we welcome it, but not for the price > of our principles. We foster the old programming hacker culture, only > practical results (be it elegant code, elegant designs or well-thought > arguments) count in this group. We don't give a damn about who you know or > what influence you have. Certainly we like interesting stories, and we're > open and welcoming to everyone - but for getting respected here you must > deliver us something we value according to our standards. > > You are invited to develop the pil stack further, hands on, what holds you > back? > The PicoLisp stack is simple enough that we surely could coordinate > multiple variants if people like to do the work. Less talking and more > doing, Guido! > Theorizing is nice and sometimes worthwile, but we're allergic to mental > masturbation, let's not mix up the map with the real territory. > > Kind regards and no offense, > beneroth > On 18.04.20 22:46, Guido Stepken wrote: > > Hi Alex! > > "completely replace it with pil21" ... (LLVM based) > > Using US software stacks, even if open source and under a free license are > not tolerable. For any nation, for any kind of project. > > US Cloud Act, Patriot Act, by law, force US companies as well US > organisations in general, such as Linux Foundation as well as Apache > Foundation and LLVM Foundation to comply with US law. > > Here's a possible outcome: > https://www.infoq.com/news/2016/06/visual-cpp-telemetry/ > > The compiler itself becomes a NSA/CIA spy tool. With (compressed) over 420 > megabytes of source code size for LLVM, world does not have the slightest > chance to do any security review on that software stack. > > And that's what stupid cowboys are hoping for: Not only creating Lock-In - > as well as legal problems - on APIs of all kinds (see Oracle-Google > lawsuit) with Apache/Linux/LLVM/... Foundations, stupid cowboys are also > injecting spy code into in all kinds of US controlled libraries (NPM now is > Microsoft/Github owned) and especially compilers, development tools. > > My urgent advice: Stay with your own x64 compiler, forget about everything > that is coming from or is directed by US companies, US foundations of any > kind. > > Switch to LLVM with pil21 and i cannot recommend you and your (until > today: trustworthy) software stack any longer for any kinds of projects. > > And i can assure you: My influence is **much bigger** than you might > think! Stop that, immediately! > > Use C99 compilers, that are small enough to be security reviewed, such as > TCC. > > Best regards, Guido Stepken > > Am Samstag, 18. April 2020 schrieb Alexander Burger <a...@software-lab.de>: > > Hi Andras, > > > >> If you are interested I have patched the 19.12 32bit sources to compile > without GCC. > >> I have attached the changed files: pico.h, main.c, apply.c and flow.c > > > > Thanks a lot! > > > > > >> Since clang does not support variable length array in structures I > allocate the bindFrame > >> with alloca() and provided a macro in pico.h to ease this: allocFrame(). > >> > >> I know that the 32bit version is not the mainstream version, but feel > free to > >> abuse the patches. > > > > Cool! > > > > As I'm concentrating on pil21, I'm glad if development and maintenance > of pil32, > > mini and/or ersatz is taken care of by others. Until it is replaced by > pil21 > > next year, I will do necessary fixes to pil64 and then - if all goes > well - > > completely replace it with pil21. > > > > Let's hope that no major problems pop up ... ;) > > > > ☺/ A!ex > > > > > > -- > > UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe > > > > > >
