Has anyone toyed with distributing “closed source” #JavaScript modules as V8 bytecode? I know you can pre-compile and load bytecode just fine. I also know that to some degree you can turn bytecode back into JS, but is that result useful enough to make the shipping as bytecode a moot point? And are there other options? Can WASM help?
@postmodern I mean: I can do it with v8 bytecode, but is that annoying enough to reconstitute into usable JS, so it is effectively closed source? The same answer should be true for wasm.
@janl@postmodern if someone finds what you are doing interesting enough, then they WILL decompile it. You can make it a bit inconvenient, but not much more.
@WarrenGallagher@postmodern yeah the bytecode package makes this very easy. And yes, that’s how all computers work, so I’m less worried about that. I’m interested to hear from folks who have used this for distribution.
@WarrenGallagher@postmodern e.g. I’ve only found one piece of software that can actually do the v8 bytecode to ja thing and it is super cumbersome to set up, and IIRC has a proprietary component or something.
Add comment