5 ms·
Those people people were complaining about it 10 years ago. In those times I remember that you could recognize a Java desktop application because you could coun
by mrighele 8y ago
Those people people were complaining about it 10 years ago. In those times I remember that you could recognize a Java desktop application because you could count the seconds that it would take for a menu to open after a click. While the current batch of Electron apps use lot of memory/cpu/battery, they usually fare _much_ better in interactivity, which is what often drives away a user.
- chii 8y ago> count the seconds that it would take for a menu to open after a click if that's really the case, then it was the application writer's fault, as java can be made just as responsive, if not more so, than electron. The GC can be tuned far better tha javascript!
- mrighele 8y agoI agree that a Java desktop application can be responsive, in fact I use a couple of them from time to time that behave quite well. Back in the day though my experience was that most of the Java software had terrible performance. In that case, I think it's correct to blame the platform for making hard to have a smooth experience "by default". (In the same way, for example, that we can blame C for not making it easy to write safe program, even if a programmer should be able to write them properly) > The GC can be tuned far better tha javascript! On this I agree completely! (altough my experience with that is mostly on the server side)
- pjmlp 8y agoThe people that cared about their users already had the option to AOT compile those Java applications, or actually write them properly. Many Java applications got bad reputation because no one bothered to learn how to use Swing properly and were doing everything on the UI thread.