Web Version about dawg

[jsmith]

• https://github.com/GPC-debug/nodebowl
• https://www.npmjs.com/package/memfs-nodebowl

[jsmith]

• https://github.com/olydis/node-in-browser
• https://github.com/facebook-atom/atom-in-orbit

[jsmith]

https://blog.cloudboost.io/how-to-run-node-js-apps-in-the-browser-3f077f34f8a5

[jsmith]

This could be very useful: https://web.dev/native-file-system/

[jsmith]

@heitorsilva just wondering, what do you think about this being a desktop app versus a web app? I really want this to be a web app but I think the biggest issue is having access to the file system (for audio files). The link I posted above makes it seem like we could get near native file system support from chrome if users toggle this experimental feature. Of course we would lose other libraries like audio-decode and node-wav but these could easily be replaced... I think? I'm pretty busy with school/work but once I'm finished my classes next month I plan to maybe work on this :)

[heitorsilva]

@jsmith I think you need to reflect on what is your end goal with this DAW...

do you wanna go all in, like competing with Logic, Ableton, Cubase? or do you want to try to do something different, like a complement to other DAWs, or an open-source web collaborative DAW?

if you have the answer to these questions, probably you will know if you should continue as a web platform, or transform this into a desktop app.

whatever you decide, I'm here to support... just share the vision (maybe even write it down somewhere in the README, Wiki or Website).
; )