JS doesn't

so for JS contexts — 1 thread at a time can execute JavaScript

you can create multiple contexts and share code between them

они не хотят об этом написать блогпост?

node.js in GraalVM is a normal node with V8 replaced by the GraalVM JavaScript engine, so it just creates 1 context for JS execution, like V8.

I understand

does it pay off (replacing v8 by GraalVM)?

thanks for your answers

anytime! does it pay off — is a vague question :) can you please elaborate what you mean. Is GraalVM node faster than normal node? — no, V8 is really-really good :) I think we're very close to v8 at peak performance in Enterprise. But the warmup is way-way longer.
GraalVM can run with giant heaps though, because you can leverage the GCs from HotSpot (really-really good ones), and you can mix your js with for example Java — so in certan scenarios that can give you quite a bit of CPU back.

NextJournal for example is rendering their react on server-side with GraalVM: https://nextjournal.com/kommen/react-server-side-rendering-with-graalvm-for-clojure there are some very approximate numbers there

Odnoklassniki are using GraalVM for React SSR: https://www.youtube.com/watch?v=HtiWXkPxmXA (in Russian)

I know some other companies experimented with node.js / JVM interop for the reasons similar to what Alex mentioned above —- some folks write in JVM languages, some in JS — the results work together without figuring out how to build a fleet of microservices for every tiny function

one of my favorite examples is using the testcontainers library for managing docker containers programmatically (usually from integration tests) from your node.js tests

вери вэлл! бяк ту russian :D

estcontainers->Testcontainers ;-)

danke!

просто я сломался об это и только из контекста догадался о чём речь 😆

да ладно тебе там levenshtein distance 1 чар )

Но если не знать про тестконтейнеры, то можно и не догадаться. А у меня мозг заточен занижать уровень восприятия, чтобы с людми легче общаться было 🤣

Т.е. чтобы меня понимали

thanks dude