Turbocall – the just-in-time compiler for Deno FFI

Re:Turbocall – the just-in-time compiler for Deno FFI by diath on Monday March 25, 2024 @12:37PM (#39818393)

Honestly I feel like they should work first on API compatibility with NodeJS just so that it can be easier to adopt/migrate seamlessly, then try more improvements in the runtime. It's nice that they have performance optimizations but what are they good for when I can't use Deno because it's not compatible/missing APIs?

[ Parent | on HN ]

Re:Turbocall – the just-in-time compiler for Deno FFI by aapoalas on Monday March 25, 2024 @01:43PM (#39819242)

This feature and these APIs have been in Demo for a few years at this point.

[ Parent | on HN ]

Re:Turbocall – the just-in-time compiler for Deno FFI by Kamq on Monday March 25, 2024 @06:18PM (#39821857)

This is only one strategy to get adoption. The other is to have better apis/more features so that new projects gradually move to your runtime.

In this hypothetical, eventually being on node would become like still being on java 8 is today.

[ Parent | on HN ]

Re:Turbocall – the just-in-time compiler for Deno FFI by pjmlp on Tuesday March 26, 2024 @02:06AM (#39824673)

Except node, like Java, moves along, making those that made a bet being a better Java 8, seem irrelevant with time, unless they happened to have a platform holder sponsoring their existence.

Deno needs a bit more than that for adoption.

[ Parent | on HN ]

Re:Turbocall – the just-in-time compiler for Deno FFI by notnullorvoid on Monday March 25, 2024 @08:30PM (#39822960)

As a heavy Node user, I think it was a mistake for Deno to try to bake in a compatibility layer with Node. It's a moving target, and will detract from other valuable work.

Node compatibility is not something that will get me to switch to Deno. I will switch once I'm not restricted to the bundled TSC version, and there is a well supported bundler for client code.

[ Parent | on HN ]