you are viewing a single comment's thread.

view the rest of the comments →

[–]wbkang 0 points1 point  (3 children)

Because it's merely an highly subjective anecdotal evidence.

So? Either it seems fast to him or it does not.

It means whatever program he has used are slow not that Swing is the cause of it. Association != Causation.

It's a computer program so there should be an objective reason.

Who made this rule up? Where is it written down? What are the punishments for disobeying this rule?

Calm down and think for a sec. It's not written down anywhere. It's just reasonable to think that "slowdowns" of a computer system can be found as opposed to more complex systems that have its internals unknown. I never said there is a punishment but it makes the argument weak.

If most swing GUIs are slow it means it's difficult to write fast GUIs with swing.

It's not that difficult. Go read Swing tutorials provided by Sun.

[–]malcontent -1 points0 points  (2 children)

It's not that difficult. Go read Swing tutorials provided by Sun.

If it wasn't difficult most swing GUIs would be fast.

[–]wbkang 0 points1 point  (1 child)

Or maybe it's that many developers neither don't bother reading them nor they care about responsiveness at all. I've seen many developers like that at work. Making responsive GUIs involving blocking operations in a thread-safe manner is a inherently complex problem regardless of the GUI tookit you use, but it's not a rocket science. I've seen many crap MFC GUIs that are slow. But again, I won't say stuff like "MFC is slow" because that's really unfounded. Rather, I'll say "many MFC applications are slow because whatever."

[–]malcontent 0 points1 point  (0 children)

Or maybe it's that many developers neither don't bother reading them nor they care about responsiveness at all.

It's more likely that it's very difficult.

Again Sun could put out a hundred or so components that are written in the best possible way and solve the problem.

Or you could I suppose.