Re: back to the future in bench game

2017-01-17 Thread Jakob Eriksson
This was interesting! Just saw pixielang on HN. > 17 jan. 2017 kl. 22:28 skrev Mike Pechkin : > > Author of http://pixielang.org/ in the city. > Welcome to community > >> On Tue, Jan 17, 2017 at 7:10 PM, Timothy Baldridge >> wrote: >> > Check link in archive: >> >https://web.archive.org/web/20

Re: back to the future in bench game

2017-01-17 Thread Mike Pechkin
Author of http://pixielang.org/ in the city. Welcome to community On Tue, Jan 17, 2017 at 7:10 PM, Timothy Baldridge wrote: > > Check link in archive: > >https://web.archive.org/web/20150308140349/http:// > kazimirmajorinc.com/Documents/The-speed-of-eval-in-some- > Lisp-implementations/index.htm

Re: back to the future in bench game

2017-01-17 Thread Alexander Burger
Hi Mike, > Check link in archive: > https://web.archive.org/web/20150308140349/http://kazimirmajorinc.com/Documents/The-speed-of-eval-in-some-Lisp-implementations/index.html > > Lets update PicoLisp (17.1.7) times and compare with other dialects. > Demo code for time3 by @taij33n: > (bench >(

back to the future in bench game

2017-01-17 Thread Timothy Baldridge
> Check link in archive: > https://web.archive.org/web/20150308140349/http://kazimirmajorinc.com/Documents/The-speed-of-eval-in-some-Lisp-implementations/index.html As a Clojure programmer, I find that Clojure code rather...gross. Of course it's slow, Clojure is optimized completely differently fr

back to the future in bench game

2017-01-17 Thread Mike Pechkin
hi, Check link in archive: https://web.archive.org/web/20150308140349/http://kazimirmajorinc.com/Documents/The-speed-of-eval-in-some-Lisp-implementations/index.html Lets update PicoLisp (17.1.7) times and compare with other dialects. Demo code for time3 by @taij33n: (bench (let N 100