My experience of Squirrel is a good 30 seconds of unresponsiveness when pasting 100 lines or so in the SQL edit window, and I'm not exactly on a slow machine either...
On 30 April 2012 21:57, Ricky Clarkson <[email protected]> wrote: > Squirrel is pretty snappy and if you change the look and feel from the > default, not too ugly. Ricoh's InfoPrint Manager has an ugly but quick > Swing client. My last company has various ugly but quick Swing CCTV > playback applications. > > I wrote a network simulator that was less ugly, and snappy. I wrote a tiny > app that verifies MD5 sums so that non-technical staff could run quality > checks on files being loaded onto hardware just before shipping, and got > asked whether it was really in Java as it was fast and tiny. > > All that's not to say that the Swing-slow statements are unfounded. It > just takes some effort to make sure things are fast. I remember loading a > date picker at startup just because the classloading delay was visible if > that was left to when the user wanted it. Not a large delay, just visible. > > Another part of the story is background tasks, which hopefully just > improved in Java 7 with SecondaryLoop. I'm looking forward to trying that > out. > On Apr 30, 2012 3:38 PM, "Cédric Beust ♔" <[email protected]> wrote: > >> On Mon, Apr 30, 2012 at 11:28 AM, Casper Bang <[email protected]>wrote: >> >>> >>> On Monday, April 30, 2012 8:17:03 PM UTC+2, phil swenson wrote: >>>> >>>> java apps can feel snappy sometimes. but often the first time you hit >>>> a menu item it takes forever to come up. Or if you leave an app >>>> running, leave for another task and come bask - it takes quite a while >>>> to become responsive again. also, garbage collection pauses are >>>> annoying. >>>> >>> >>> I don't think it's the GC, but Swing is just horribly over-engineered. >>> The most successful Java desktop applications (if we can call these >>> >> >> Agreed. I think overall, it's easier to create a reasonably responsive >> SWT application while doing so in Swing requires a lot of time and >> expertise. There are very, very few companies that can pull this off >> besides JetBrains. >> >> -- >> Cédric >> >> -- >> You received this message because you are subscribed to the Google Groups >> "The Java Posse" group. >> To post to this group, send email to [email protected]. >> To unsubscribe from this group, send email to >> [email protected]. >> For more options, visit this group at >> http://groups.google.com/group/javaposse?hl=en. >> > -- > You received this message because you are subscribed to the Google Groups > "The Java Posse" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/javaposse?hl=en. > -- Kevin Wright mail: [email protected] gtalk / msn : [email protected] quora: http://www.quora.com/Kevin-Wright google+: http://gplus.to/thecoda <[email protected]> twitter: @thecoda vibe / skype: kev.lee.wright steam: kev_lee_wright "My point today is that, if we wish to count lines of code, we should not regard them as "lines produced" but as "lines spent": the current conventional wisdom is so foolish as to book that count on the wrong side of the ledger" ~ Dijkstra -- You received this message because you are subscribed to the Google Groups "The Java Posse" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/javaposse?hl=en.
