Skip to content

Instantly share code, notes, and snippets.

@Ueaj-Kerman
Last active July 25, 2021 17:43
Show Gist options
  • Select an option

  • Save Ueaj-Kerman/64805e53735c31df2ab3827a1a77214c to your computer and use it in GitHub Desktop.

Select an option

Save Ueaj-Kerman/64805e53735c31df2ab3827a1a77214c to your computer and use it in GitHub Desktop.

Revisions

  1. Ueaj-Kerman revised this gist Jul 25, 2021. 1 changed file with 38 additions and 32 deletions.
    70 changes: 38 additions & 32 deletions thing.md
    Original file line number Diff line number Diff line change
    @@ -1,39 +1,45 @@
    **Sandboxed Java Bytecode**\
    pros:\
    easy to use, can write in the same language the rest of the code is in\
    performant, no extra runtime needed\
    smol, no need to package a runtime\
    cons:\
    possibility of sandbox escape (unlikely, but it might happen)\
    **Sandboxed Java Bytecode**
    ```
    pros:
    easy to use, can write in the same language the rest of the code is in
    performant, no extra runtime needed
    smol, no need to package a runtime
    cons:
    possibility of sandbox escape (unlikely, but it might happen)
    may allow OEEL to be used as a DRM

    **Compiled Java Code**\
    pros:\
    cursed\
    easy to use, no one likes kotlin anyways\
    performant\
    smol\
    slightly lower possibility of sandbox escape\
    cons:\
    ```
    **Compiled Java Code**
    ```
    pros:
    cursed
    easy to use, no one likes kotlin anyways
    performant
    smol
    slightly lower possibility of sandbox escape
    cons:
    can still be used as DRM
    ```

    **Sandboxed Scripting Language**\
    pros:\
    low possibility of sandbox escape\
    harder to use as a DRM\
    cons:\
    harder to use, need to learn a seperate language\
    slower\
    **Sandboxed Scripting Language**
    ```
    pros:
    low possibility of sandbox escape
    harder to use as a DRM
    cons:
    harder to use, need to learn a seperate language
    slower
    need to package a runtime
    ```

    **Data Code**\
    pros:\
    very low possibility of sandbox escape\
    can't really be used as DRM\
    cons:\
    slow\
    need to write a full on api\
    most of the code will still probably have to exist in unencrypted code\
    **Data Code**
    ```
    pros:
    very low possibility of sandbox escape
    can't really be used as DRM
    cons:
    slow
    need to write a full on api
    most of the code will still probably have to exist in unencrypted code
    painful to use

    ```
    https://www.strawpoll.me/45520526
  2. Ueaj-Kerman revised this gist Jul 25, 2021. 1 changed file with 30 additions and 30 deletions.
    60 changes: 30 additions & 30 deletions thing.md
    Original file line number Diff line number Diff line change
    @@ -1,39 +1,39 @@
    **Sandboxed Java Bytecode**
    pros:
    easy to use, can write in the same language the rest of the code is in
    performant, no extra runtime needed
    smol, no need to package a runtime
    cons:
    possibility of sandbox escape (unlikely, but it might happen)
    **Sandboxed Java Bytecode**\
    pros:\
    easy to use, can write in the same language the rest of the code is in\
    performant, no extra runtime needed\
    smol, no need to package a runtime\
    cons:\
    possibility of sandbox escape (unlikely, but it might happen)\
    may allow OEEL to be used as a DRM

    **Compiled Java Code**
    pros:
    cursed
    easy to use, no one likes kotlin anyways
    performant
    smol
    slightly lower possibility of sandbox escape
    cons:
    **Compiled Java Code**\
    pros:\
    cursed\
    easy to use, no one likes kotlin anyways\
    performant\
    smol\
    slightly lower possibility of sandbox escape\
    cons:\
    can still be used as DRM

    **Sandboxed Scripting Language**
    pros:
    low possibility of sandbox escape
    harder to use as a DRM
    cons:
    harder to use, need to learn a seperate language
    slower
    **Sandboxed Scripting Language**\
    pros:\
    low possibility of sandbox escape\
    harder to use as a DRM\
    cons:\
    harder to use, need to learn a seperate language\
    slower\
    need to package a runtime

    **Data Code**
    pros:
    very low possibility of sandbox escape
    can't really be used as DRM
    cons:
    slow
    need to write a full on api
    most of the code will still probably have to exist in unencrypted code
    **Data Code**\
    pros:\
    very low possibility of sandbox escape\
    can't really be used as DRM\
    cons:\
    slow\
    need to write a full on api\
    most of the code will still probably have to exist in unencrypted code\
    painful to use

    https://www.strawpoll.me/45520526
  3. Ueaj-Kerman created this gist Jul 25, 2021.
    39 changes: 39 additions & 0 deletions thing.md
    Original file line number Diff line number Diff line change
    @@ -0,0 +1,39 @@
    **Sandboxed Java Bytecode**
    pros:
    easy to use, can write in the same language the rest of the code is in
    performant, no extra runtime needed
    smol, no need to package a runtime
    cons:
    possibility of sandbox escape (unlikely, but it might happen)
    may allow OEEL to be used as a DRM

    **Compiled Java Code**
    pros:
    cursed
    easy to use, no one likes kotlin anyways
    performant
    smol
    slightly lower possibility of sandbox escape
    cons:
    can still be used as DRM

    **Sandboxed Scripting Language**
    pros:
    low possibility of sandbox escape
    harder to use as a DRM
    cons:
    harder to use, need to learn a seperate language
    slower
    need to package a runtime

    **Data Code**
    pros:
    very low possibility of sandbox escape
    can't really be used as DRM
    cons:
    slow
    need to write a full on api
    most of the code will still probably have to exist in unencrypted code
    painful to use

    https://www.strawpoll.me/45520526