3 ms·
I understand that "enterprise java" is something most people loathe, but to be fair it's not the language's fault. Java supports thread pools, callbacks, future
by rootlocus 10y ago
I understand that "enterprise java" is something most people loathe, but to be fair it's not the language's fault. Java supports thread pools, callbacks, futures, etc. just like javascript. It's the developers that choose the threading model.
> In fact, one thread is enough, also for driving complex UI.
Swing and JavaFX are single threaded, and very capable of driving complex UIs. I fail to see how you needed to switch to nodejs (a backend technology) to find this.
> better start driving complex UI in multiple web workers, because, performance.
UIs have never been parallel. One explanation is the complexity of synchronizing the flow of events coming from the OS (ie input) and to the OS (ie drawing). More on that here [1]
[1] https://community.oracle.com/blogs/kgh/2004/10/19/multithreaded-toolkits-failed-dream https://community.oracle.com/blogs/kgh/2004/10/19/multithrea...
- ygra 10y ago> UIs have never been parallel. WPF can have multi-threaded UIs, but it's usually not worth the headache. Although I think every control is bound to the Dispatcher of its containing window, so you can only have one thread per window instead of dividing it finer (not that it matters much, the usual rules of doing nothing computation-intensive on the UI thread still apply).