bangle-io VS quickjs-emscripten

Another similar tool that is open sourced and allows you to sync with GitHub [1] .

It differs by providing a WYSIWYG interface while saving content in Markdown.

[1] https://github.com/bangle-io/bangle-io

Hello other text based beings!

I am very passionate about journaling/collecting one’s thoughts. In a typical HN fashion, I decided to make a tool that scratches my itch [1].

Having spent majority of my life with portable computers around, I feel we as humans are losing the joy of writing one’s thoughts out. Sometimes the best thing is to write your thought and establish this one way temporal connection to your future self. This is so beautiful because it crosses the barriers of time, culture and location. An alien human descendant billions of years in future might be able to connect with me by reading my thoughts. Writing is an intellectual marvel that has no other equivalent

[1] https://bangle.io

What is the pain you are looking to alleviate? YMMV with notion. I think your personal reflections are probably the most important part of this because personal productivity and organization are so personal.

Single app has worked better for me. I am at 4 months of journaling and planning every day (I have used notion for a few years). When I was using desecrate apps I would go 1-3 weeks before system would fall apart.

For me the main pros are: Ability to move and copy elements from tickler to daily plan so easily. Ability to link todo's to documentation. Ability to take notes in a way that works with how I think, and ability to take handle incoming thoughts as fast as they need to be documented.

Main cons are: only "date time" construct in databases, I would prefer a "time" construct. Offline. Data portability.

> I feel like maybe this is the heart of it, having a personal cache to make a temporary mess in until you have time to clean it up later. I could see that being useful - though id want to move everything out of that place and not organize things within it

Cal Newport has a `working_memory.txt` file on every one of his desktops that he chucks random information into and then processes it at the end of the day. Maybe a system like that could be more your jam.

I might one day work up the courage to use [https://bangle.io/](https://bangle.io/) + github. Feels like owning my data + a bit more flexibility could be nice, but that seems like a lot of work.

I would suggest trying out bangle.io [1] - an opens source markdown web app that is completely local and will support GitHub based syncing.

[1] https://bangle.io

There is also https://bangle.io - an open source web app for taking markdown notes and saving them in your computer.

Note: I’m the author of the project.

I have been using it to provide ability to read existing markdown notes in a users directory see [1]. So far it works great but browser support is limited to chrome and edge.

[1] https://bangle.io

I have to say, this is a very well designed app.

Since you talk about local only app , I can suggest bangle.io [1] - a local only operative note taking app.

[1] https://github.com/bangle-io/bangle-io

Based on your comment below I think you figured out the difference - but if you're looking to execute JS, you can pick between ShadowRealm (where available, or using a polyfill) or my library quickjs-emscripten.

Pros of quickjs-emscripten over ShadowRealm:

- You can use quickjs today in any browser with WASM. ShadowRealm isn't available yet, and polyfills have had security issues in the past. See https://www.figma.com/blog/an-update-on-plugin-security/

- In ShadowRealm eval, untrusted code can consume arbitrary CPU cycles. With QuickJS, you can control the CPU time used during an `eval` using an [interrupt handler] that's called periodically during the eval.

- In ShadowRealm eval, untrusted code can allocate arbitrary amounts of memory. With QuickJS, you can control both the [stack size] and the [heap size] available inside the runtime.

- quickjs-emscripten can do interesting things with custom module loaders and facades that allow synchronous code inside the runtime to call async code on the host.

Pros of ShadowRealm over QuickJS:

- ShadowRealm will (presumably?) execute code using your native runtime, probably v8, JavaScriptCore, or SpiderMonkey. Quickjs is orders of magnitude slower than JIT'd javascript performance of v8 etc. It's also slower than v8/JSC's interpreters, although not by a huge amount. See [benchmarks] from 2019.

- You can easily call and pass values to ShadowRealm imported functions. Talking to quickjs-emscripten guest code requires a lot of fiddly and manual object building.

- Overall the quickjs(-emscripten) API is verbose, and requires manual memory management of references to values inside the quickjs runtime.

[interrupt handler]: https://github.com/justjake/quickjs-emscripten/blob/main/doc...

[stack size]: https://github.com/justjake/quickjs-emscripten/blob/main/doc...

[heap size]: https://github.com/justjake/quickjs-emscripten/blob/main/doc...

[benchmarks]: https://bellard.org/quickjs/bench.html

The thing I want to achieve with WebAssembly is still proving a lot harder than I had anticipated.

I want to be able to take strings of untrusted code provided by users and execute them in a safe sandbox.

I have all sorts of things I want this for - think custom templates for a web application, custom workflow automation scripts (Zapier-style), running transformations against JSON data.

When you're dealing with untrusted code you need a really robust sandbox. WebAssembly really should be that sandbox.

I'd like to support Python, JavaScript and maybe other languages too. I want to take a user-provided string of code in one of those languages and execute that in a sandbox with a strict limit on both memory usage and time taken (so I can't be crashed by a "while True" loop). If memory or time limit are exceeded, I want to get an exception which I can catch and return an error message to the user.

I've been exploring options for this for quite a while now. The furthest I've got was running Pyodide inside of Deno: https://til.simonwillison.net/deno/pyodide-sandbox

Surprisingly I've not found a good pattern for running a JavaScript interpreter in a WASM sandbox yet. https://github.com/justjake/quickjs-emscripten looks promising but I've not found the right recipe to call it from server-side Python or Deno yet.

Can Extism help with this? I'm confident I'm not the only person who's looking for a solution here!

"Safely execute untrusted Javascript in your Javascript, and execute synchronous code that uses async functions" quickjs-emscripten, NPM

This maybe, as a start?

https://github.com/justjake/quickjs-emscripten

QuickJS Running in WebAssembly\ (17 comments)

The library was inspired by Figma’s blog posts about their plug-in system: https://github.com/justjake/quickjs-emscripten#background

If you need to call into user-generated Javascript synchronously or have greater control over the sandbox environment, you can use WebAssembly to run a Javascript interpreter: https://github.com/justjake/quickjs-emscripten#quickjs-emscr...

QuickJS in WebAssembly is much slower than your browser's native Javascript runtime, but possibly faster than async calls using postMessage. As an added bonus, it can make async functions in the host appear to be synchronous inside the sandbox using asyncify: https://emscripten.org/docs/porting/asyncify.html.

You can use One Weird Trick with generator functions to make your code "generic" over synchronicity. I use this technique to avoid needing to implement both sync and async versions of some functions in my quickjs-emscripten library.

The great part about this technique as a library author is that unlike choosing to use a Promise return type, this technique is invisible in my public API. I can write a function like `export function coolAlgorithm(getData: (request: I) => O | Promise): R | Promise`, and we get automatic performance improvement if the user's function happens to return synchronously, without mystery generator stuff showing up in the function signature.

Helper to make a function that can be either sync or async: https://github.com/justjake/quickjs-emscripten/blob/ff211447...

Uses: https://cs.github.com/justjake/quickjs-emscripten?q=yield*+l...

This seems like a pretty nice, recently enabled way of getting a sandboxed js environment: QuickJS compiled to WASM: https://github.com/justjake/quickjs-emscripten.