| ▲ | unified101 5 hours ago | |||||||
I don't think this goes far enough! Make the actually app store be the same file itself. so it's a living application and the file is constantly updated to how you use it. Copy it around, and you carry your data wiht you as well. Let's go deeper. it's a webserver app + the server code + application code + db, so pocketbase++ where it's also the deployment target. Then combine it with APE liek system, and the same file loads and stores things on every platform. evil laugh Very cool hacking! My hats off to the author. | ||||||||
| ▲ | arnsholt 5 hours ago | parent | next [-] | |||||||
The application writing its state to the executable is basically Smalltalk (or Lisp). It's an extremely powerful way of writing software, IMO. | ||||||||
| ||||||||
| ▲ | regularfry 4 hours ago | parent | prev | next [-] | |||||||
I didn't have this idea exactly but I did play around with sqlite as an embedded database for packing ruby apps into a single file a while ago. It was less direct than this: you basically compiled all the dependencies (including .so's) into a fake filesystem that an overridden `require` loaded from, which was unpacked to a `:memory:` database at runtime from a `.data` section that got bolted onto the interpreter. It died when 1.8->1 9 changed how the build system works and I never got round to updating. A version based on this which carries around an overlay filesystem would be comparatively straightforward, the hard work is already done. | ||||||||
| ▲ | pizzafeelsright an hour ago | parent | prev | next [-] | |||||||
This has been my hope. BIOS -> Database that has everything including OS. This way we get WORM and AI integration. | ||||||||
| ▲ | born-jre 5 hours ago | parent | prev | next [-] | |||||||
| ▲ | pstuart 2 hours ago | parent | prev [-] | |||||||
Doesn't redbean do this in a more portable way (not ELF dependent)? | ||||||||