Not sure if this counts as a Show HN or not, but I've been working on Go bindings for the Luau programming language. Luau is a programming language made by Roblox and is useful for non-Roblox as well thanks to its heavy sandboxing/hardening and lack of dangerous features/primitives out of the box.
Prior attempts at providing Lua bindings for Go (like golua) have heavy restrictions (like non-working exception handling/pcall/xpcall due to incompatiblities in exception handling) or are pure go ports of Lua (which is great if you're OK with a port but no one has ported Luau to pure Go yet and many times, you want the real thing).
To get around issue 1, gluau makes use of a rust proxy based on the mluau (fork of mlua) crate with errors caught by rust and translated to Result types for Go to then translate to idiomatic Go types. To quote a reddit user, its a "programming language centipede" but it works well and has support for a large part of the Luau language (including interrupts, memory limits, thread resume/yield and userdata) without any big limitations besides potential bugs here/there.
You joke but there actually may be merit to it. Of course, you'd still need a GUI on top but you technically could put a full command-line interface with limited commands and actually sell it as a differentiating feature at this point.
For a time there were automatic transmission cars with push buttons. I think it was a 1950s/60s Great Idea. If I remember you had to reach around the steering wheel to access them.
> When you say "GitHub's AI", you have to be absolutely crystal clear whether you mean an automated process or an AI-powered system that has gone rogue. The difference in implications is significant and conflating the two isn't likely to help your case.
Its clearly some sort of automated process (the security logs mention a process called `spamurai` which I assume means Spam User Removal AI) that one day decided that I was 'spammy' and hence flagged me down.
For many people, the Apple Silicon GPU is an interesting problem to solve given that the firmware is loaded by the bootloader and all and its actually generally easier to interact with than say NVIDIA while having decent perf. Also GPUs in general are really complex beasts involving IP from tons of companies in general. Would not be surprised if even Apple doesn't have the full schematics...
> and its actually generally easier to interact with than say NVIDIA while having decent perf
I’m pretty sure that Turing and newer work the same way. The drivers basically do nothing but load the firmware & do some basic memory management if I recall correctly.
Prior attempts at providing Lua bindings for Go (like golua) have heavy restrictions (like non-working exception handling/pcall/xpcall due to incompatiblities in exception handling) or are pure go ports of Lua (which is great if you're OK with a port but no one has ported Luau to pure Go yet and many times, you want the real thing).
To get around issue 1, gluau makes use of a rust proxy based on the mluau (fork of mlua) crate with errors caught by rust and translated to Result types for Go to then translate to idiomatic Go types. To quote a reddit user, its a "programming language centipede" but it works well and has support for a large part of the Luau language (including interrupts, memory limits, thread resume/yield and userdata) without any big limitations besides potential bugs here/there.