Re: State of Scheme in the Browser Lassi Kortela (31 Jul 2019 16:36 UTC)
Re: State of Scheme in the Browser John Cowan (31 Jul 2019 18:46 UTC)
Re: State of Scheme in the Browser Lassi Kortela (31 Jul 2019 18:55 UTC)
Re: State of Scheme in the Browser John Cowan (31 Jul 2019 19:20 UTC)
Re: State of Scheme in the Browser Lassi Kortela (31 Jul 2019 20:14 UTC)
Re: State of Scheme in the Browser Amirouche Boubekki (31 Jul 2019 20:49 UTC)
Re: State of Scheme in the Browser John Cowan (31 Jul 2019 20:51 UTC)
Re: State of Scheme in the Browser Lassi Kortela (31 Jul 2019 20:55 UTC)
Re: State of Scheme in the Browser John Cowan (31 Jul 2019 21:00 UTC)
Re: State of Scheme in the Browser Lassi Kortela (31 Jul 2019 21:21 UTC)
Re: State of Scheme in the Browser John Cowan (31 Jul 2019 22:03 UTC)
Re: State of Scheme in the Browser Lassi Kortela (01 Aug 2019 09:40 UTC)
Re: State of Scheme in the Browser Amirouche Boubekki (01 Aug 2019 11:25 UTC)
Re: State of Scheme in the Browser John Cowan (01 Aug 2019 14:18 UTC)
Re: State of Scheme in the Browser Lassi Kortela (02 Aug 2019 10:24 UTC)
Re: State of Scheme in the Browser Amirouche Boubekki (02 Aug 2019 19:19 UTC)
Re: State of Scheme in the Browser Lassi Kortela (02 Aug 2019 20:42 UTC)
Re: State of Scheme in the Browser Arthur A. Gleckler (02 Aug 2019 00:55 UTC)
Re: State of Scheme in the Browser John Cowan (02 Aug 2019 01:17 UTC)
Re: State of Scheme in the Browser Arthur A. Gleckler (02 Aug 2019 01:28 UTC)
Re: State of Scheme in the Browser John Cowan (02 Aug 2019 02:28 UTC)
Re: State of Scheme in the Browser Lassi Kortela (01 Aug 2019 09:48 UTC)

Re: State of Scheme in the Browser Amirouche Boubekki 02 Aug 2019 19:19 UTC

Le ven. 2 août 2019 à 12:24, Lassi Kortela <xxxxxx@lassi.io> a écrit :
>
> > WebAssembly will have tail-calls, it is already present in nodejs v12.
> > See Schism issues and recent PRs.
>
> Great! Huh, I had no idea something like Schism existed :)
>
> Does WebAssembly give access to the same DOM (Document Object Model) as
> JavaScript? What about Ajax requests?

Indirectly yes, there is still no native access to the DOM.

> What are the pros and cons of WebAssembly as a compilation target compared to JavaScript?

The pro is that it is much faster, the cons is that it doesn't allow
to access the dom and do ajax request for the time being.

See https://github.com/scheme-live/ruse-scheme/issues/3

>
> > Speaking of demo, I am wondering what kind of demo could I create to
> > make it more obvious that this really works, and that performance is
> > not a problem?
>
> One idea is some kind of search that reacts whenever the user types a
> character into an input field, and does HTTP requests in the backgrounds
> (perhaps caching some of the results) is a good approximation of what
> many real web apps do. For example, something like Chicken's Chickadee
> (<https://api.call-cc.org/5/doc/>). We could use that kind of search
> field for <docs.schemers.org> also.

To the point. That is what I was looking for. But I am not sure when I
will be able to do it.