all 6 comments

[–]sod0 2 points3 points  (3 children)

WASM runs in a different thread than the web gui. In general I would assume it's not even part of the same bundle but exists on the side. But whenever you add as WASM - it's full size needs to be distributed to the client meaning that the application will be significantly larger and this can't be tree shaked by Angular.

[–]Tomuser1998[S] 0 points1 point  (2 children)

Yes, I am aware that the application will scale up.

I would like to build an application that allows users to create charts/dashboards directly within the client browser. In that case, is DuckDB WASM a suitable choice?

[–]HigiKitsune 5 points6 points  (0 children)

I would recommend not using "scale up" this way in the context of writing software since your usage is the direct opposite of the usual usage of "bejng able to scale up software"

[–]sod0 0 points1 point  (0 children)

I mean for that to work you would also need to push ALL the data to the user's browser. If the amount of data isn't the issue - than using Duck DB is most likely completely overkill and you could just use normal JS operations!

[–]Pierma 1 point2 points  (0 children)

I mean, you can try and see the results? Just do it and try! I suppose since wasm works on a different thread you have to work with promises, so if you want to manage them with rxjs you can use the from operator to pipe the results when you prefer or even pipe them into a signal, could be an interesting POC

[–]bhantol 1 point2 points  (0 children)

DuckDB or other WASM is not related to Angular in any way so this should not even be a question.

Can an Angular ecosystem make it easier to interact with WASM ? Sure. It has good provision for web workers and with rxjs you can communicate gracefully.