Swing is just Better

Comparing SWT and Swing "SWT is really just a thin veneer over the native toolkit, so as one would expect, all application model data must be copied from application data structures to native toolkit components. Developers can't choose a representation that best matches their applications needs. Consider a spreadsheet application, in which the user is presented with a very large table but the table data is sparse. It is trivial in Swing to create such a model and bind it to a JTable. The time required to construct such a JTable is constant, whether 10,000 or 1,000,000 rows are shown to the user.[3]. The same is not true of SWT. It takes SWT 5 seconds to show a 40,000 row table [4], and I gave up waiting for SWT to display a 100,000 row table after one minute. Additionally, as SWT creates a native widget for each row, memory grows and grows with each additional row. The same is not true of Swing."