On 16.05.20 12:42, Alexander Burger wrote:
> I can't help him ...
No, of course you can't, neither the community.
There were many posts here of the community which argued in a fair
manner to him,
but I think, one can't stop a sender like him. He was not able to
receive any more.
So don't worry,
On Sat, May 16, 2020 at 05:06:31PM +0200, Alexander Shendi (Web.DE) wrote:
> Can't you simply bounce his mails? I'm afraid handing matters over to the
> police isn't going to be effective.
It is all not effective I believe. I just ignore it ...
☺/ A!ex
--
UNSUBSCRIBE: mailto:picolisp@software
Can't you simply bounce his mails? I'm afraid handing matters over to the
police isn't going to be effective.
Am 16. Mai 2020 12:42:17 MESZ schrieb Alexander Burger :
>On Sun, May 10, 2020 at 04:06:47PM +0200, pd wrote:
>> Thanks Alex for your absolute amazing and beautiful work and
>dedication.
Nice to hear is fun for you, for me is fun to use picolisp and also this
list where you are do accesible and kind, it's a real privilege!
Sad to know of that bulling, usually the better is simply ignore him but
sometimes it's not enough. Hope this stop quickly
Regards
El sáb., 16 may. 2020 12:47
Wow that guy is really pain in the ass.. sorry about that Alex, is it
possible to report him to the authorities for cyber-bullying? not sure of
the right term..
On Sat, May 16, 2020 at 7:47 PM Alexander Burger
wrote:
> On Sun, May 10, 2020 at 04:06:47PM +0200, pd wrote:
> > Thanks Alex for your
On Sun, May 10, 2020 at 04:06:47PM +0200, pd wrote:
> Thanks Alex for your absolute amazing and beautiful work and dedication.
Thank you all too! For me it is a lot of fun :)
> Fortunately noise is over and list returns to pure signal.
Yes indeed!
Unfortunately for me it is not over. Guido kee
Thanks Alex for your absolute amazing and beautiful work and dedication.
Fortunately noise is over and list returns to pure signal.
El vie., 8 may. 2020 0:15, David Bloom escribió:
> FWIW I have been enjoying a fantastic feature of e-mail, FILTERS!
>
> Thanks Alex and community for your work, y
FWIW I have been enjoying a fantastic feature of e-mail, FILTERS!
Thanks Alex and community for your work, your examples, your help when
someone posts to the list, and most of all for being sane voices in a less
than sane world.
On Thu, May 7, 2020 at 3:52 PM wrote:
> On Wed, 06 May 2020 17:02
On Wed, 06 May 2020 17:02 -04:00, Brian Cleary wrote:
> It's the end of an error.
This was my favorite. hehe.
--
UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
Alex (and friends):
Thank you for the truly beautiful work that you share with us!
8-)
rcs
On Wed, May 6, 2020 at 3:41 PM Alexander Burger wrote:
> Hi Guido,
>
> On Wed, May 06, 2020 at 08:35:33PM +0200, Guido Stepken wrote:
> > Perhaps you *all* learn, what a JIT compiler really is, in differ
It's the end of an error.
On Wed, May 6, 2020 at 1:13 PM Karol Drożak wrote:
> Thank God!...
>
> śr., 6 maj 2020, 21:53 użytkownik Wojciech Gac > napisał:
>
>> That's all folks. ;)
>>
>> On Wed, May 6, 2020 at 9:41 PM Alexander Burger
>> wrote:
>>
>>> Hi Guido,
>>>
>>> On Wed, May 06, 2020 at
Thank God!...
śr., 6 maj 2020, 21:53 użytkownik Wojciech Gac
napisał:
> That's all folks. ;)
>
> On Wed, May 6, 2020 at 9:41 PM Alexander Burger
> wrote:
>
>> Hi Guido,
>>
>> On Wed, May 06, 2020 at 08:35:33PM +0200, Guido Stepken wrote:
>> > Perhaps you *all* learn, what a JIT compiler really
That's all folks. ;)
On Wed, May 6, 2020 at 9:41 PM Alexander Burger wrote:
> Hi Guido,
>
> On Wed, May 06, 2020 at 08:35:33PM +0200, Guido Stepken wrote:
> > Perhaps you *all* learn, what a JIT compiler really is, in difference
> > to a AOT Ahead of Time Compiler.
> >
> > https://en.wikipedia.o
Hi Guido,
On Wed, May 06, 2020 at 08:35:33PM +0200, Guido Stepken wrote:
> Perhaps you *all* learn, what a JIT compiler really is, in difference
> to a AOT Ahead of Time Compiler.
>
> https://en.wikipedia.org/wiki/Just-in-time_compilation
>
> Make ZEROpointZERO sense then to let Picolisp do, wha
On 5/6/20 11:35 AM, Guido Stepken wrote:
If this is really the case, it promise, i say 'goodbye' from PicoLisp
mailing list!!! I promise!
Oh, Guido, please don't make promises you can't keep 🤣
--
UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
On Wed, May 6, 2020 at 3:11 PM John Duncan wrote:
>
> Just wanted to tell you how much I appreciate your work. I hope you find a
> blowhard like Guido amusing and not too irritating. I get the impression he’s
> hardly written a line of code in his life, and that was probably in Java.
Just wante
Perhaps you *all* learn, what a JIT compiler really is, in difference
to a AOT Ahead of Time Compiler.
https://en.wikipedia.org/wiki/Just-in-time_compilation
Make ZEROpointZERO sense then to let Picolisp do, what Clang (the C to
LLVM IR translator) does.
If this is really the case, it promise, i
Another benefit of llvm is you get their dataflow analysis and optimization
for free, on the myriad ARM and x64 microarchitectures as optimized as you
like. That is harder to do in custom abstract assembly, as you’d have to
maintain a little zoo of targets.
On Wed, May 6, 2020 at 13:08 wrote:
>
> On 06.05.20 18:42, John Duncan wrote:
> Picolisp is interpreted. Even the llvm version is just creating an
> interpreter. There is no JIT.
Exactly!
Guido, you should really stop talking about things you so obviously have
no understanding of.
There is NO COMPILING when executing program written i
Ursprüngliche Nachricht
Von: gstep...@gmail.com
Gesendet: 6. Mai 2020 17:36
An: picolisp@software-lab.de
Antworten: picolisp@software-lab.de
Betreff: Re: Do free Open Source Foundation's Software Stacks fall under US
Export Law?
Am Mittwoch, 6. Mai 2020 schrieb Joh-Tob Schäg :
>
Picolisp is interpreted. Even the llvm version is just creating an
interpreter. There is no JIT.
On Wed, May 6, 2020 at 12:36 Guido Stepken wrote:
> Am Mittwoch, 6. Mai 2020 schrieb :
>
> > Read Wikipedia:
> >
> > LLVM allows code to be compiled statically, as it is under the
> traditional GCC s
Am Mittwoch, 6. Mai 2020 schrieb :
> Read Wikipedia:
>
> LLVM allows code to be compiled statically, as it is under the
traditional GCC system, or left for late-compiling from the IR to machine
code via just-in-time compilation (JIT)
Wikipedia might have missed the chapter: "Extreme Laziness - Us
On 06.05.20 17:29, Guido Stepken wrote:
> > Also the size of LLVM doesn't matter since it is only necessary when
> compiling the binary. You can likely download binaries Alex built just
> as you can do.
>
> "Compiling the binary" is funny pil21, sitting on top of LLVM JIT
> engine is post JIT
Am Mittwoch, 6. Mai 2020 schrieb Joh-Tob Schäg :
>
>> Sigh! How often have I told here that the main purpose of pil21 is
portability?
> Do you see any portablity problems:
> https://luajit.org/luajit.html
> iOS obviously *is* supported. Tons of games are using LuaJIT on all kinds
of platforms. Of c
Certainly Fennel only a proof of concept. But it's easy to understand, you
can add lists and other things within just a few lines by using Lua
primitives, which are Lisp like.
Same with Common Lisp and Scheme. When you read through Common Lisp
language definition, it's a huge book, language defini
My friend! The political wind has massively changed from US side. We cannot
go on doing business like 5 months and 6 days ago.
You brains simply haven't noticed yet ...
Am Mittwoch, 6. Mai 2020 schrieb Alfonso Villén :
> Hello Guido,
>
>> Alex, go on using LLVM. See you in Guantanamo. (Remember:
pplies to your "I did
some cool distributed pilog thing" if you write some cool software but can't
share it, don't talk about it on the mailing list.
Ursprüngliche Nachricht
Von: gstep...@gmail.com
Gesendet: 6. Mai 2020 14:51
An: picolisp@software-lab.de
Antworten: picol
I'll note that fennel seems like severely sub par lisp, not even really
supporting lists... Though there are others, lumen and urn for luaJIT. Not
sure why you keep mentioning fennel, while it seems most popular somehow,
but it is also most clojure like and with seemingly boneheaded list
handling.
Hello Guido,
> Alex, go on using LLVM. See you in Guantanamo. (Remember: Meng
Wanzhou > was caught in Canada with US warrant).
>
> Unbelievable ignorance
I don't understand what makes you think that Alex is an ignorant.
First of all, I want to thank Alex as John already did. I don't know
You're absolutely right. After having learned 24 languages in my life now,
i exclusively work with highly sophisticated code generators.
Much higher developed, that just the https://jasonelle.com/ example i
mentioned before. Purely functional, of course. But sometimes i return to C
and inline Asse
PilBox, yes. Also one of your brilliant ideas ...
Something similar already exists since a couple of years ...
https://jasonette.com/, renamed to https://jasonelle.com/
Some Google guys picked up the idea and made FLUTTER: One code, two
binaries for Android and iOS. Dart Programming Language. Btw
Also, I see no problem in, for example, Guido trying to prove the
point by making a PicoLisp clone in the runtime of his choice :) IIRC,
we already have the Ersatz (Java) port of picolisp.
On Wed, May 6, 2020 at 4:23 PM George-Phillip Orais
wrote:
>
> Hi Guido,
>
> Thank you for sharing your insi
I don't discourage him. I present facts. LLVM contains plenty of AI code,
especially for generating code for NVIDIA chips.
Since January 1st there are export restrictions for AI code to China now.
https://www.reuters.com/article/us-usa-artificial-intelligence/u-s-government-limits-exports-of-arti
Hi Guido,
Thank you for sharing your insights here, I have fun reading them.
But please respect Alex decision in using LLVM for pil21, its his choice
and its his programming language, so please stop discouraging him.
BR,
Geo
On Wed, May 6, 2020 at 10:12 PM John Duncan wrote:
> Hey Alex,
>
Hi John,
> Just wanted to tell you how much I appreciate your work. I hope you find a
> blowhard like Guido amusing and not too irritating. I get the impression
> he’s hardly written a line of code in his life, and that was probably in
> Java.
Thanks a lot John! :)
☺/ A!ex
--
UNSUBSCRIBE: mail
Hey Alex,
Just wanted to tell you how much I appreciate your work. I hope you find a
blowhard like Guido amusing and not too irritating. I get the impression
he’s hardly written a line of code in his life, and that was probably in
Java.
Take care!
John
On Wed, May 6, 2020 at 07:59 Alexander Bur
Am Mittwoch, 6. Mai 2020 schrieb Alexander Burger :
> On Wed, May 06, 2020 at 12:51:33PM +0200, Guido Stepken wrote:
>> Use Mike's DYNASM JIT Engine. Better, faster, smaller (tiny, in
comparison
>> to LLVM), more portable. He's from Munich.
>
> Useless.
Ah, really?
> Sigh! How often have I told h
On Wed, May 06, 2020 at 12:51:33PM +0200, Guido Stepken wrote:
> Use Mike's DYNASM JIT Engine. Better, faster, smaller (tiny, in comparison
> to LLVM), more portable. He's from Munich.
Useless.
Sigh! How often have I told here that the main purpose of pil21 is portability?
I need it to build PilB
Hi Alex!
Yes! -10 for using LLVM, that falls under US export restrictions (ECRA). AI
software is no longer allowed to export to e.g. China, since January 1st.
So if you have compiled-in a single line of LLVM code into pil21, you're in
real trouble now, because of pilog, which is certainly a kind
On Wed, May 06, 2020 at 09:55:08AM +0200, Guido Stepken wrote:
> Lisp, as functional language, should
> better be implemented in a functional language
Point for pil21 :)
--
UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
There are plenty of free implementations of Lisp language in Pascal, Modula
2/3, Oberon out there.
E.g. https://github.com/bobappleyard/pascal-lisp/blob/master/README
But all that makes no real sense. Lisp, as functional language, should
better be implemented in a functional language, such as Has
Well, can PicoLisp replace expensive "fully ACID" Datomic and Closure?
You mentioned that PicoLisp would be missing ACID feature. That's why we've
invented the "Event Sourcing Layer":
https://de.wikipedia.org/wiki/Event_Sourcing
Sorry, not available in other languages!
What's that? This is kind
Hi Guido,
Want to hear your thoughts about, what if PicoLisp is implemented in Pascal
or Modula or Oberon? Will it be cool or not?
BR,
Geo
On Wed, May 6, 2020 at 2:46 PM Guido Stepken wrote:
> In international law, signing such a contract, as Anaconda Eula is called
> "self binding". Those id
In international law, signing such a contract, as Anaconda Eula is called
"self binding". Those ideas in law go back to John Locke, Francis Bacon,
Thomas Hobbes.
British and American law differ between binding contracts and common law.
But in those countries, signing such a contract binds you to t
>From the philosphical point of view, 64 bit integer is the same as 64 bit
float, except for, that you give certain bits a different meaning.
Picolisp gives you total freedom, to decide, what to do with those 64 (or
even more!!!) bits. Either you can store 4x 16 bit as so called
"minifloat", even
Hi Guido
> Anaconda is a well known, free Software Installer for Python and R
> packages, mostly used under Windows, right?
>
> And you think, that "free software" packages cannot be restricted by
> US ministry of trade or U.S. president, such as happened in Huawei
> Google case, right? Plain wron
You being an interesting personality, I have just mildly related question.
What is your opinion on picolisp's floating point situation? (this is one
reason why I did not even attempt to delve too much into it apart from some
small experiments in REPL, though obviously I still find it and community
> Do you really think you would need such a feature often?
It would be useful sometimes, when debuging for example, I would not
have to change the code much, just stick I and print...
>(let I 0 (do 5 (print (inc 'I)) "finished"))
With this I would have to add parens and inc etc.
Not somethi
Hi Tomas,
> I see that you take big pain to optimize things a lot. I would
Not intentionally ;-)
I don't really mind so much about the actual performance, but more about
the underlying principles. And I feel that it is not the "right thing"
to waste a cell at each primitive iteration through a
Hi Alex,
> The current implementation of 'do' is not well suited to grant access to
> the internal counter to the application level.
>
> Because 32bit PicoLisp has no short numbers, incrementing a number
> always results in the allocation of a new cell (turning the old cell
> into garbage). To avo
Hi Tomas,
> : (do2 (I . 5) (print I) "finished")
The current implementation of 'do' is not well suited to grant access to
the internal counter to the application level.
Because 32bit PicoLisp has no short numbers, incrementing a number
always results in the allocation of a new cell (turning the
51 matches
Mail list logo