alt Hacker NewsWell, if you offload heavy compute into an async task, then usually it depends strictly on how many concurrent inputs you are given. But even something as “simple” as a performance editor benefits from this if done well - that’s why JS text editors have reasonably acceptable performance whereas Java IDEs always struggled (historically anyway since even Java has adopted green threads).
Replies
groundzeros2015 • today at 8:50 AM
You think IDEs are written in JS because of the performance benefits of the threading model?
I thought it was because they could copy chromium.
➕ show 1 reply
PunchyHamster • today at 10:04 AM
Maybe you remember performance of IDEs from 15 years ago because that definitely isn't my experience.
jcelerier • today at 12:18 PM
> that’s why JS text editors have reasonably acceptable performance
Absolutely not
Are you sure Java's UI issues are caused by threading and not just Swing being a glitchy pile of junk?
For example, if you don't explicitly call the java.awt.Toolkit.sync() method after updating the UI state (which according to the docs "is useful for animation"), Swing will in my experience introduce seemingly random delays and UI lag because it just doesn't bother sending the UI updates to the window system.