Hi,
I would actually prefer to attend in person, but given the circumstances, +1
for an online event.
Best Regards,
-- Alexander
Am 22. April 2020 22:44:35 MESZ schrieb Brian Cleary :
>+1 for online lurker. I'd also be happy to participate any load tests
>before hand.
>
>On Wed, Apr 22, 2020
+1 for online lurker. I'd also be happy to participate any load tests
before hand.
On Wed, Apr 22, 2020 at 1:37 PM r cs wrote:
> +1 for online too 8-)
>
> On Wed, Apr 22, 2020 at 12:33 PM C K Kashyap wrote:
>
>> +1 for online :)
>>
>> On Wed, Apr 22, 2020 at 4:48 AM David Bloom wrote:
>>
>>>
+1 for online too 8-)
On Wed, Apr 22, 2020 at 12:33 PM C K Kashyap wrote:
> +1 for online :)
>
> On Wed, Apr 22, 2020 at 4:48 AM David Bloom wrote:
>
>> +1 lurker interested in an online conference. While it is disappointing
>> to not be able to meet people in person it seems that attendance
+1 for online :)
On Wed, Apr 22, 2020 at 4:48 AM David Bloom wrote:
> +1 lurker interested in an online conference. While it is disappointing to
> not be able to meet people in person it seems that attendance will be
> dramatically increased. Happy to help with testing online tools if needed.
oops .. hit send too early -
Got it. The idea was not to encode more types - just reduce the
"complexity" of tagged pointers and remove the word aligned function
address restriction. Yes, a separate byte heap would totally be much more
complex. One of the reasons of this desire was to build
Got it. The idea was not to encode more types - just reduce the
"complexity" of tagged pointers and impose the word aligned function
address restriction but from what I gather. Yes, a separate byte heap would
totally be much ore complex. One of the reasons of this desire was to build
miniPicoLis
Nope. Polymorphic Inline Caching. And why shouldn't JIT compilers use MMU
"memory address violation exception" to check for end of range? Same for
TLB.
I could flood you with hundreds of papers about that. I am using that all
time.
Of you were right and such knowledgeable, PicoLisp would run
Hi Kashyap,
> Quick question - when you mentioned "doubling of space" - perhaps you were
> talking about systems that can only have WORD aligned pointers - is that
> correct?
Not only. Also on a byte-addressed machine, imagine if you make a cell of two
9-byte words, you get every cell aligned at
Hi Alex,
Quick question - when you mentioned "doubling of space" - perhaps you were
talking about systems that can only have WORD aligned pointers - is that
correct?
Regards,
Kashyap
On Wed, Apr 22, 2020 at 6:56 AM Guido Stepken wrote:
> Well, we have year 2020, not Dijksra 1978. Even embedded
On Wed, Apr 22, 2020 at 03:49:41PM +0200, Guido Stepken wrote:
> Well, we have year 2020, not Dijksra 1978. Even embedded systems have a MMU
> and you get "Memory Access Violation", so no pointer rage checks needed to
> be handled by CPU any longer.
Sigh, you don't understand at all how a Lisp
Well, we have year 2020, not Dijksra 1978. Even embedded systems have a MMU
and you get "Memory Access Violation", so no pointer rage checks needed to
be handled by CPU any longer. Those formerly needed range checks, eating up
clock cycles, now are deeply sticking in MMU and IOMMU ... Bang! -
Hi Alex,
> Yes, what Guido writes is nonsense. Fixed-sized address spaces are a
terrible
> solution. Doesn't scale, and is extremely inefficient due to the necessary
> pointer range checks.
>
> PicoLisp's way is far superior, because the tag bits come "free", they are
> implicit by the natural
I meat: "0xE000 for everything, that must be persisted to disk". There, of
course, you can also reserve three slots for float, integer, string ...
Best regards, Guido
Am Mittwoch, 22. April 2020 schrieb George-Phillip Orais <
orais.georgephil...@gmail.com>:
> Hi Guido,
> I think you mean 0xF000
Hi Geo,
> I think you mean 0xF000 for everything? This is indeed cool! but hmm does
> it limit the memory for each data type?
Yes, what Guido writes is nonsense. Fixed-sized address spaces are a terrible
solution. Doesn't scale, and is extremely inefficient due to the necessary
pointer range
Hi Guido,
I think you mean 0xF000 for everything? This is indeed cool! but hmm does
it limit the memory for each data type? Like what if the application uses
only integers so does it mean it cannot use the memory location for float
and strings?
BR,
Geo
On Wed, Apr 22, 2020 at 8:44 PM Guido
+1 lurker interested in an online conference. While it is disappointing to
not be able to meet people in person it seems that attendance will be
dramatically increased. Happy to help with testing online tools if needed.
On Wed, Apr 22, 2020, 1:35 AM Jean-Christophe Helary <
Hi Kashyap!
Reserving 1-3 bit from 32 or 64 bit register for special purposes, e.g.
indicating type or as persistence flag (ORM-wrapper) is the old fashioned
way. It unnecessarily costs cycles, reduces precision ...
The modern, "fully functional" (no state bits anywhere!) - and correct -
way
Hello,
This is sad, but I think it is the most realistic decision under the
circumstances. Let's hope we can arrange something in the future.
I too would be interested in an online conference.
/ Mattias
On Wed, Apr 22, 2020 at 07:00:21AM +0200, Alexander Burger wrote:
> Hi all,
>
> yesterday
Hello guys,
I too would be happy to "attend" such a virtual meeting ;-)
Take care, best
Eric
Le 22/04/2020 à 08:13, George-Phillip Orais a écrit :
Same here, as lurker and amateur PicoLisper, I love to join and the
attend this online PilCon 2020, thank you Alex!
BR,
Geo
--
Having started my adventure with Lisp conferences in 2018 (ELS 2018 in
Marbella, Spain) I got completely hooked up on the idea of meeting
super-interesting people and listening about stuff they're working
on. I'd be excited to join you guys. Of course, being able to meet in
person beats anything,
Hi Jean-Christophe Helary
> There is a thread on hacknews about jisti vs mumble where they mention issues
> with a large number of people.
>
> https://news.ycombinator.com/item?id=22477785
Thanks for the link. Yeah I think people tested my current instance with
up to 5 people for several hours.
I'll add my voice as being another who would be interested in an online
convention.
-Wilhelm
On 4/21/20 11:13 PM, George-Phillip Orais wrote:
Same here, as lurker and amateur PicoLisper, I love to join and the
attend this online PilCon 2020, thank you Alex!
--
UNSUBSCRIBE:
Super lurker here, who just deployed (self hosted) jitsi as part of product
we sell. IMO jitsi is quite good, and if self hosting I would have little
concerns. Also it is not hard to self host with esp with their docker
version, though it currently has a bug with streaming (well due to chrome
Same here, as lurker and amateur PicoLisper, I love to join and the attend
this online PilCon 2020, thank you Alex!
BR,
Geo
On Wed, Apr 22, 2020 at 2:47 PM Jean-Christophe Helary <
jean.christophe.hel...@traduction-libre.org> wrote:
>
>
> > On Apr 22, 2020, at 14:00, Alexander Burger wrote:
>
24 matches
Mail list logo
