Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

I'm thinking of something a bit lower level than app packaging. But yeah think something like "jar for native code" but with the ability to directly dlopen() and dlsym() from it. So the file could contain native code that's OS or CPU specific and the dynamic linker (bundled with your app) would be able to successfully load the right one and get symbols from it. It'd just be a more convenient way to ship code that can fully utilize the CPU and OS, without excessive duplication (e.g. think about merging the text sections and symbol tables together but using something a bit like symbol versioning to keep the code for each OS separated).


The new foreign function & memory interface is sort of like that, given a shared library that runs on multiple OSs you can use it as is with Java.


Almost sounds like wine or similar then, but you only need to simulate what's not directly available.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: