[bisq-network/proposals] Bisq 2.0 - A multi-protocol DEX (working title Misq) (#330)

[Stan]

- **Ambitious**  I would want to work on Misq for the mid/long term, but wonder (like everyone else) if it is possible to build this and keep Bisq going with the current number of devs.  That said, I'm ready to dive in.

- **Roadmap**  You suggest developing a parallel Lisq version separate from Bisq, then integrating Lisq into Misq.  I suggest new work begins on Misq, while calling it Lisq.  As soon as Misq can support Lisq and Bisq, re-name it Misq.  I assume there are components in Bisq that could be used by Lisq, and bits of Bisq integration into Misq can begin at once.

- **Modules**  I worked on an OSGi module based system when Java Modules were just a spec, and it was painful.  But I think building java apps from fine grained modules is a very good way to separate concerns, manage dependencies, and put together multiple apps from pre-defined module lists -- details non techie users do not need to be concerned about.  I assume Java Modules are easier to work with than OSGi of 15 years ago, and we could move Gradle's current responsibility for defining modules to Java Module definitions.  I'm not sure how Gradle works with Java Modules, but I also assume it would not be messier than the current build file.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/bisq-network/proposals/issues/330#issuecomment-826935464
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bisq.network/pipermail/bisq-github/attachments/20210426/6881c446/attachment.htm>