News for hackers. Stuff that matters.
Re:(Yet Another) Lisp in Go by sebastianconcpt on Sunday May 08, 2022 @11:27PM (#31310252)
86 microseconds is an order of magnitude better than what was benchmaked here but maybe other bechmarks aren't as good.

Said that, I do not want to sunk time into trying to improve something, only to find out tha it will perform worst.

Maybe the compromise is to try to do a minimal proof of concept only manually transpilig a couple of objects from Smaltalk to Go and measure that?

Re:(Yet Another) Lisp in Go by igouy on Monday May 09, 2022 @01:46PM (#31317307)
Well, we don't seem to have any information about the hardware used, so it's going to be a sketchy comparison.

In any case, shouldn't your measurement be made the same way John Jacobsen seems to have made measurements —

    $ time ./bin/visual ./image/visualnc64.im -nogui -doit "Stdout nextPutAll: 100 factorial printString; cr. ObjectMemory quit"
    93326215443944152681699238856266700490715968264381621468592963895217599993229915608941463976156518286253697920827223758251185210916864000000000000000000000000

    real 0m0.616s
    user 0m0.452s
    sys  0m0.161s
Re:(Yet Another) Lisp in Go by sebastianconcpt on Tuesday May 10, 2022 @08:42AM (#31326364)
I've ran that on 64bits Pharo 7 in a mid 2015 mac book pro and it measures only the time taken for the factorial (excluding system startup/shutdown).

By the way, I'm not recognizing that command, I'm curious, what smalltalk is that you're using there?

Re:(Yet Another) Lisp in Go by igouy on Wednesday May 11, 2022 @12:30PM (#31342254)

    $ cat fact.st
    Stdio stdout 
        nextPutAll: 100 factorial printString; 
        nextPut: Character lf.!
    SmalltalkImage current snapshot: false andQuit: true!

    $ time bin/pharo --headless Pharo10-SNAPSHOT-64bit-502addc.image fact.st
    93326215443944152681699238856266700490715968264381621468592963895217599993229915608941463976156518286253697920827223758251185210916864000000000000000000000000

    real 0m0.350s
    user 0m0.303s
    sys 0m0.049s
Re:(Yet Another) Lisp in Go by igouy on Tuesday May 10, 2022 @01:56PM (#31330183)
> I've ran that on…

I don't think we know about the hardware used for the other measurements — so sketchy comparison.

> … excluding system startup/shutdown…

Why would you do that when the other measurements included startup/shutdown?

https://github.com/eigenhombre/l1/

> … not recognizing that command…

Cincom Smalltalk, VisualWorks® 8.3 run with `time` from a terminal window command line, like the other measurements.