[bisq-network/bisq] Bisq UI very laggy/slow on Windows 8 (#3308)

Anton Luka Šijanec notifications at github.com
Fri Nov 6 18:00:51 CET 2020


I don't think you understand what a web-UI would mean in this case. It
would still work with the level of decentralization Bisq aims to provide,
as you would still host your own server that would do everything the Bisq
client does, but without the interface.

The interface would be accessed via the HTTP protocol, but since it still
just connect to the website you are hosting locally there's no issue with
decentralisation.

This brings many pros:

* The ability to have the Bisq node connected without a desktop/monitor
* the ability to write command line lightweight interfaces
* the ability to host the server on a different machine than the client
(for example on a server that is connected to the internet and turned on
24/7)
* Write APIs and wrappers for automating stuff via HTTP.

V V pet., 6. nov. 2020 ob 17:33 je oseba fresheneesz <
notifications at github.com> napisala:

> @chimp1984 <https://github.com/chimp1984> I agree a web-app wouldn't work
> for the level of decentralization Bisq aims to provide. However, I don't
> think the complexity of the application has anything to do with the
> performance issues Bisq's UI suffers from. The UI technology could very
> well make a huge difference in the operation of the UI. Its pretty clear to
> me that a lot of heavy non-UI processing is done on the same thread as the
> UI runs on. In well designed applications, this isn't the case - UI gets a
> separate thread from the non-UI code for this very reason. This may not be
> an easy thing to fix, but changing to a new UI technology may be a simple
> way to fix it.
>
> —
> You are receiving this because you commented.
> Reply to this email directly, view it on GitHub
> <https://github.com/bisq-network/bisq/issues/3308#issuecomment-723174689>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/AKFM2EUWWRKJTPW4Z44OS6DSOQQMHANCNFSM4IZELNSA>
> .
>


-- 
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/bisq/issues/3308#issuecomment-723189466
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bisq.network/pipermail/bisq-github/attachments/20201106/014671ae/attachment.html>


More information about the bisq-github mailing list