I think it's pretty misleading to call it JavaScript, though.
My description would be: a subset of EcmaScript tailored for the TechEmpower benchmark environment (which I think is supposed to be disqualifying, but hasn't always been in practice -- see: Actix).
I think it's a cool project, but I have qualms about using TechEmpower as a way to boost experimental projects.
Thanks for the comment. I hadn't actually considered that i was "using techempower as a way to boost experimental projects" but i can understand you seeing it that way now that you have said it! =)
I've been working on this in my spare time for quite a while and one of the primary goals of the project is to be "fast" out of the box. I've been following and enjoying the Techempower reports since they started and set myself an initial goal of scoring well on it so I can use that as a performance baseline for further work. I've also seen a number of other experimental/early stage frameworks on there and didn't receive any pushback from the very kind folks at Techempower when I submitted it. I was clear with them about what it is: https://github.com/TechEmpower/FrameworkBenchmarks/pull/5969.
Re. calling it "JavaScript" - you do have a point as I am not keen on having to support the full API implemented in browsers. I see this very much as a server side only "toolkit" for folks who want to build fast network servers and other systems software and enjoy using Javascript and being able to take advantage of the amazing v8 engine and the huge base of existing JS code in the wild.
3 comments
[ 3.2 ms ] story [ 21.0 ms ] threadMy description would be: a subset of EcmaScript tailored for the TechEmpower benchmark environment (which I think is supposed to be disqualifying, but hasn't always been in practice -- see: Actix).
I think it's a cool project, but I have qualms about using TechEmpower as a way to boost experimental projects.
I've been working on this in my spare time for quite a while and one of the primary goals of the project is to be "fast" out of the box. I've been following and enjoying the Techempower reports since they started and set myself an initial goal of scoring well on it so I can use that as a performance baseline for further work. I've also seen a number of other experimental/early stage frameworks on there and didn't receive any pushback from the very kind folks at Techempower when I submitted it. I was clear with them about what it is: https://github.com/TechEmpower/FrameworkBenchmarks/pull/5969.
Re. calling it "JavaScript" - you do have a point as I am not keen on having to support the full API implemented in browsers. I see this very much as a server side only "toolkit" for folks who want to build fast network servers and other systems software and enjoy using Javascript and being able to take advantage of the amazing v8 engine and the huge base of existing JS code in the wild.
Thanks again.