> Yeah, that is the spirit I would like to give to my scheme
> implementations comparator.
Anything to help users better understand the differences between the
implementations is great! I would also like to have some kind of
comparison widget.
We have to try carefully not to be biased against any implementations,
but at the same time recommendations need to be given in some place.
It's worth putting some time into thinking where to make recommendations
(on which sites).
That is basically what took me much time of thinking. How to make the data
realistic or at least based on user feedback, somehow the community would
serve as quality control but that works only in some extend, bad actors always
exists. Right now, I have no solution. To take an example: X Scheme Implementations
maintainers might say that there is step debugger, profiler and test runner when
in fact all of those are far from good enough IMHO. YMMV. At some point, we need
to be able to add confidence value to each "facts".
With the API it's even more difficult - since it has to serve the whole
Scheme community, we probably can't put statements like "Chez is the
fastest Scheme" in the API data. (Even though that's the consensus,
there are probably some tasks or platforms for which it is not fastest.)
At the same time, that's a useful way to explain it to newbies.
I was wondering if Ecraven's benchmark could be re-used in schemedoc?!
In the BSD world, there was a similar way to explain it: "FreeBSD =
performance, NetBSD = portability, OpenBSD = security". The developers
from each BSD would sometimes say, "hey, there's more to it than that!"
:) But it was the most useful summary for newbies. We are in a similar
situation with Scheme.
Yes, I agree. Similarly to the beginner friendly thing. I used the "fastest scheme"
because chez doesn't have a proper tag line / synopsis, except "R6RS implementation"
which is boring and doesn't say really what it is.
> Spoiler: the database is incomplete, it is just a demo but you can try
> it at https://scheme-live.github.io/ff.scm/
>
> The code is at https://github.com/scheme-live/ff.scm
>
> The code is not very good, I need to take a step back and think on how
> I will proceed with (all) the work I have.
This is really nice progress. Demos are the best way to boost morale.
I spied the Network tab in the Firefox dev console, and it downloads
"chibi.data" which looks like the Chibi standard library,
Yeah, chibi.data contains the libraries shipped with chibi that I forked
where we can save a few KB because right now it is 2.4Mb. The bad
thing is that I need to fork chibi-scheme repo to be able to add libraries
to the build...
and "main.scm" which is the application and support lib.
This is still a work in progress, I will ship the "framework-ish" stuff
in a library and clean that file to only have the application code.
Are chibi.wasm and chibi.js
alternative compiled/transpiled versions of the Chibi VM itself?
Yes those are compiled with emscripten (so does chibi.data). I don't want to touch that for the time being.
> Have a good day all!
You too!