luajit-remake VS ish

It's really cool that Haoran Xu copy-and-patch technique is catching on, I remember discovering it through his blog posts on applying these techniques to his own LuaJIT remake project[0][1] (and I probably found those through a post here). I highly recommend them if you're into that sort of thing, BTW. They're incredible deep dives, but he uses the details-element to keep the metaphorical descents into Mariana Trench optional so it doesn't get too overwhelming.

I even had the privilege of congratulating him the 1000th star of the GH repo[2], where he reassured me and others that he's still working on it despite the long pause after the last blog post, and that this mainly has to do with behind-the-scenes rewrites that make no sense to publish in part.

[0] https://sillycross.github.io/2022/11/22/2022-11-22/

[1] https://sillycross.github.io/2023/05/12/2023-05-12/

[2] https://github.com/luajit-remake/luajit-remake/issues/11

This seems like an awesome way of writing faster interpreters – i.e. not in assembly, but in C++ snippets you stitch together with a tool.

I did peek at the deegen tool a bit, and it seems quite large? https://github.com/luajit-remake/luajit-remake/tree/master/d...

I would be interested in an overview of all the analysis it has to do, which as I understand is basically “automated Mike Pall”

FWIW I think this is the hand-written equivalent with LuaJIT’s dynasm tool: https://github.com/LuaJIT/LuaJIT/blob/v2.1/src/vm_x64.dasc (just under 5000 lines)

Also there are several of these files with no apparent sharing, as you would get with deegen:

https://github.com/LuaJIT/LuaJIT/blob/v2.1/src/vm_x86.dasc

https://github.com/LuaJIT/LuaJIT/blob/v2.1/src/vm_ppc.dasc

> Just imagine how much more versatile the iPad Pro would be if only you could run Linux VMs on it

After installing https://ish.app for Alpine Linux emulation on iPad, one immediately comes up with use cases, even though it's excruciatingly slow.

Hopefully Apple opens up the imminent M3 iPad Pros to run macOS and Linux VMs.

iSH

They don't "allow" it, but most apps that need background execution just ask permission for geolocation tracking and pretend to use it, for example iSH[1]. There are a few activities that the app can do to prevent itself from being suspended when it goes out of focus, like playing sound, geolocation etc.

[1] https://github.com/ish-app/ish/issues/249#issuecomment-54433...

Android: install termux, `pkg install openssh`, and preferably run `termux-setup-storage` to give it access to storage folders.

iOS: I think https://ish.app/ ?

This of course hasn't been true for years, eg: http://omz-software.com/pythonista/index.html

And you can run a C compiler (or anything) inside https://ish.app/ too.

False. iSH is an x86 "bytecode" emulator.

"Possibly the most interesting thing I wrote as part of iSH is the JIT. It's not actually a JIT since it doesn't target machine code. Instead it generates an array of pointers to functions called gadgets, and each gadget ends with a tailcall to the next function; like the threaded code technique used by some Forth interpreters."

https://github.com/ish-app/ish

There is an x86 virtual machkne running Linux available on the App Store now.

https://ish.app/

Now would Apple allow a full blown Windows VM is a different question

There are plenty of solutions for running Python in an IDE on the iPad. There is an even an x86 emulator and a Linux terminal built on top of it in the App Store.

https://ish.app/

It can run anything that you can run on an x86 in user mode. I downloaded the AWS CLI (which requires Python) to run some tests

By the way, you were completely wrong about VSCode being written in .Net.

> That's just compiling the code to a native binary, which you would then have to go submit through Apple's store. How does that help for an IDE expected to allow you to test (i.e. execute) and debug the code you've just written ten seconds ago?

There is an existence proof that it could be done. If you ran iSH with remote VNC you could have a full IDE on a Mac.

> We can see right there some examples of what isn't allowed: