HaroldCindy

6 ms·

1.
by HaroldCindy 10mo ago
Oof. My general principle is "sending AI-authored prose to another human without at least editing it is rude". Getting an AI-generated message from someone at all feels rude to me, kind of like an extreme version of "dictated
2.
by HaroldCindy 10mo ago
We need to develop new etiquette around submitting AI-generated code for review. Using AI for code generation is one thing, but asking other people review something that you neither wrote nor read is inconsiderate of their time.
3.
by HaroldCindy 10mo ago
I expect this is / was a very common problem for people porting 32-bit game code to newer compilers. I work on a fairly old codebase that forces use of x87 for a handful of code paths that don't work correctly otherwise. GCC will
4.
by HaroldCindy 1y ago
> Speaking of script state serialisation, is there any improvement to the size of those when being stored/transferred. They're about the same as before, they weren't terribly large to begin with though. From what I've
5.
by HaroldCindy 1y ago
>How do you plan on migrating data from Mono's VM to Luau? It helps a lot that you're only dealing with LSL that was compiled to .NET CIL by a single compiler and transformed into a state machine via an internal tool that preda
6.
by HaroldCindy 1y ago
I'm the contractor responsible for SL's Luau VM integration, appreciate the kind words about the Luau integration! We're still in figuring out our async strategy for user-facing APIs to be honest, so these references are supe
7.
by HaroldCindy 1y ago
One thing that was immediately apparent upon switching VMs was that a lot of the existing overhead was in scheduling, context switching and the implementation of the actual library functions like `llDoWhatever()`. We haven't even used
8.
by HaroldCindy 1y ago
Agreed. I think an underappreciated aspect of choosing a script VM in the space Roblox is in (user-generated content where scripts are content) your product is at the mercy of whoever controls your scripting implementation. The scripting en
9.
by HaroldCindy 1y ago
To be fair, both `Analysis` (the type-checker, not necessary at runtime or compile time) and `CodeGen` (the optional JIT engine) have no equivalent in PUC-Rio Lua. If you look purely at the VM and things necessary to compile bytecode (AST,
10.
by HaroldCindy 2y ago
I wasn't aware that single-file Java without a top-level static class was possible now, that + JBang seems quite useful for small tasks. One nit: > Python programmers often use ad-hoc dictionaries (i.e. maps) to aggregate related in
11.
by HaroldCindy 2y ago
There's at least one more to add to the pile, Google's Fuchsia is primarily written in Rust and aims to support the Linux ABI through "starnix". See https://fuchsia.dev/fuchsia-src/concepts/comp
12.
by HaroldCindy 2y ago
>> the VM assumes that the bytecode was generated by the Luau compiler (which never produces invalid/unsafe bytecode) Yep, to that end they also have a basic bytecode verifier (only used in debug mode / when asserts are enab
13.
by HaroldCindy 2y ago
Any upstreaming was unlikely to ever be acceptable to the PUC-Rio folks. PUC-Rio Lua uses C (with a tiny bit of C++ for stack unwinding on errors if folks don't want to use `longjmp()`,) Luau is strictly C++. Luau rewrites quite a lot