Live data from Hacker News

Fabrice Bellard Releases MicroQuickJS

github.com

531–540 of 594 posts

Re: Fabrice Bellard Releases MicroQuickJS

#531
post #81

Well, as Jeff Atwood famously said [0], "any application that can be written in JavaScript, will eventually be written in JavaScript". I guess that applies to embedded systems too [0] https://en.wikipedia.org/wiki/Jeff_Atwood

Please don't use js in medical devices.

Re: Fabrice Bellard Releases MicroQuickJS

#533

Earlier quoted context omitted.

I’m always surprised people pick Lua when Pawn exists. I think I’d even still choose it over MicroQuickJS https://www.compuphase.com/pawn/pawn.htm

I remember seeing this a long time ago and liking it, I just didn't have a use for it at the time. How does it stack up against luahit for perf and memory, and threading? It also looks like it could be worth looking at porting the compiler to zig which excels at both compiler writing and cross platform tooling.

LuaJIT is best in class performance for a scripting language -by a huge margin. In very specific problems, it can outperform C. Surely anything else is going to come up lacking if you are only considering raw benchmarks.

Re: Fabrice Bellard Releases MicroQuickJS

#534

I'm not an embedded systems guy (besides using esp32 boards) so this might be a dumb question but does something like this open up the possibility of programming an esp32/arduino board with Javascript, like Micro/Circuit Python?

It's a good _start_; much more code needs to be written to allow control of the hardware of those devices (GPIO, I2C etc).

Re: Fabrice Bellard Releases MicroQuickJS

#535
post #81

Well, as Jeff Atwood famously said [0], "any application that can be written in JavaScript, will eventually be written in JavaScript". I guess that applies to embedded systems too [0] https://en.wikipedia.org/wiki/Jeff_Atwood

Please don't use js in medical devices.

attempt at humor:Okay so, would you rather your beloved great aunt's pacemaker fail because the software in it was written in C, and there's a use-after-free memory error, or because the software in it was written in JavaScript, and because someone used `==` instead of `===` a boolean that should have been `false` is `true`?

Re: Fabrice Bellard Releases MicroQuickJS

#536
post #17

Clarification added later : One of my key interests at the moment is finding ways to run untrusted code from users (or generated by LLMs) in a robust sandbox from a Python application. MicroQuickJS looked like a very strong contender on that front, so I fired up Claude Code to try that out and build some prototypes. I had Claude Code for web figure out how to run this in a bunch of different ways this morning - I hav…

What is the purpose of compiling this to web assembly? What web assembly runtimes are there where there is not already an easily accessible (substantially faster) js execution environment? I know wasmtime exists and is not tied to a js execution engine like basically every other web assembly implementation, but the uses of wasmtime are not restricted from dependencies like v8 or jsc. Usually web assembly is used for…

[deleted]

Re: Fabrice Bellard Releases MicroQuickJS

#539
post #17

Clarification added later : One of my key interests at the moment is finding ways to run untrusted code from users (or generated by LLMs) in a robust sandbox from a Python application. MicroQuickJS looked like a very strong contender on that front, so I fired up Claude Code to try that out and build some prototypes. I had Claude Code for web figure out how to run this in a bunch of different ways this morning - I hav…

Check out this sample of using gVisor to spin up code sandboxes (potentially running on Cloud Run): https://github.com/GoogleCloudPlatform/cloud-run-sandbox

Re: Fabrice Bellard Releases MicroQuickJS

#540

Earlier quoted context omitted.

As I understand it Julia changed course and is attempting to support arbitrary index ranges, a feature which Fortran enjoys. (I'm not clear on the details as I don't use either of them.)

Let’s hope that they don’t also replicate ISO Fortran’s design flaws with lower array bounds, which contain enough pitfalls and portability problems that I don’t recommend their use.

I haven't used either language much myself and I thought the feature looked brilliant so I'd be very curious to know what sort of issues you ran into in practice.
Post reply on HN