Jint VS Netty

Jint https://github.com/sebastienros/jint

There are quite a lot of ways to run scripting languages in C#. I've no idea what JSR223 is but .NET has DLR for example. There are also multiple libraries: IronPython, NLua, Jint and Jurassic for Javascript. There's also older version of CS-Script working with .NET Framework.

You can. Embeding lua is a trivial task, and I'm reasonably sure there even are plug-and-play solutions for that, and for JS there's JINT.

I personally use Jint (a multi-platform Javascript interpreter) since Roslyn is not available on mobile. It basically has the same kind of functionality as Roslyn, but it's JS. JS is well-known and accessible to everybody, but Roslyn might be faster since there's no double indirection when interpreting the script. It also depends on what language your users are comfortable with or could learn easily.

Ah yeah, I looked into it more and decompiled the game to find that it appears they're using Jint to interpret the Javascript, and from testing with someone's REPL BBS server I can find that it's a pretty well isolated environment. Only ways around it I can think of are by exploiting some vulnerability in the sandbox to do external requests, modding the game itself to update the api, or running a parallel server to do some janky communication through the save state data.

We used https://github.com/sebastienros/jint for scripting, it's ES5 JS implementation.

Jint is a JS interpreter with an integrated engine built in C#, like V8, he is responsible for all the base code execution as well as EcmaScript implementations such as default constructors, syntax, Promises... I studied its features in depth to start and it was a bit hard (in the beginning).

MelonRuntime is based on Jint, a JavaScript interpreter created by Sébastien Ros, software developer in the ASP.NET team at Microsoft. Melon works from bindings and functionalities injected into this interpreter together with external typing (provided by another package that comes with the default project generated by the command npx melon new) and built-in tools.

Code of netty is here and using following library

We use Netty (https://netty.io/) as the source of the MQTT communication, and we build the MQTT features the MQTT broker should support ourselves on top of that.

In this space, we also have the somewhat related term blocking. Java's NIO library is one well-known non-blocking tool used for managing multiple tasks on a single Java thread. When listening to sockets, most of the time a thread is just blocked, doing nothing until it receives some data. So, it's efficient to use a single thread for monitoring many sockets, to increase the likelihood of the thread having some actual work to do. The Selector API does this but is notoriously challenging to program well. Instead, developers use frameworks like Netty which abstract some of NIO's complexity and layer on some best practices.

DirectByteBuffer exhibits an intriguing behavior: it deallocates its backing memory during the finalization process, which occurs after garbage collection (GC) cycles. This poses an issue if your system is conservative with on-heap allocations, leading to infrequent GC cycles. In such cases, there could be a significant delay between the time the memory becomes unreferenced and when it is actually deallocated. This behavior could, in some respects, mimic a memory leak.

This is why some libraries hacks into DirectByteBuffer to deallocate memory explicitly, bypassing the finalizer altogether. For instance, the Netty library has implemented such a workaround, see Netty as an [example](https://github.com/netty/netty/blob/795db4a866401aa172757b95...).

Apologies replying to myself, but Netty, which underpins many of the popular Java backend frameworks, see backward compatibility as more important than supporting green threads.

https://github.com/netty/netty/issues/12816

It'll be interesting to see who (if anyone) picks up Netty's mantle in the Project Loom world.

Looks fairly recent so I'm glad I had a pre oct22 build https://github.com/netty/netty/issues/12737

This is better? https://github.com/netty/netty/blob/4.1/pom.xml

Given the fact that Lettuce is built with Netty, we also immediately noticed quite an impact on the initialization time (cold start) of our lambda function. Netty is really fast while executing, but takes a bit of time to initialize. The new Lambda Snapstart functionality might help with that.