Slashdot Mirror

• The Daily WTF - A daily look at source code that can make one cringe, laugh, and/or cry (site, feed)
• Astronomy Picture of the Day (site, feed)
• Stupid Security (site, feed)
• Cool Tools - "A cool tool can be any book, gadget, software, video, map, hardware, material, or website that is tried and true." (site, feed
• EFF's minilinks - see tomorrow's Your Rights Online posts today (site, feed
• Your Gmail inbox (atom feed)

Are you on crack?

I'm certainly not. Although one might wonder since I'm arguing with a coward.

Azureus:
Redraws slowly when you perform opaque resizes.

Can't really say that I've noticed this. Not that Azureus is the type of application I resize much.

Consumes about 50MB of physical RAM doing nothing.

Nothing? You do realize that Azureus preallocates rather large buffers? That memory isn't going nowhere, it's used to increase performance! Why do you think it downloads faster than the original client? (Actually, early versions would allocate this memory on the fly, but that lead to some memory leakage problems that would eventually require you to restart the program.)

Creates fixed-sized dialogues without concern for viewability of text.

Ok, you've identified a UI issue. Explain to me how this is Java's fault and not the developers'? I've seen many a similar bone-headed mistakes in C programs as well. Or were we just supposed to forget hideous GUIs like GNUTella?

Routinely informs me that I've used it for 90,000+ hours.

Seen that screen once. And I run Azureus fairly often to download multi-gigabyte files. Either way, it's not like it's that annoying, and it certainly has nothing to do with Java.

G2GUI
Sancho

Besides the fact that you've again identified problems of the developers as "Java problems", I really have no friggin' idea what these programs are, nor do I care. Pulling out a random bad program does not demonstrate that a platform sucks. Intelligently explaining the underlying problems of the platform (which you have failed to do) does.

Allow me to point out a few very bad C programs:

XEdit:
The scrollbar is completely non-intuitive and requires the middle mouse button to scroll
It is difficult to understand how the "Search box" functions
Ctrl+C, Ctrl+V don't work
Filenames have to be typed instead of chosen via a GUI
Slow responsiveness
Does not resize without an add-on "Window Manager" program
GUI flashes on every update

FileMatrix:
Uses thousands of highly confusing tabs
Text in many areas does not fit in component
Confusing use of competing colors
Information overload

You can find a whole bunch more C/C++ programs like these on Interface Hall of Shame. I therefore declare that the C language platform is slow and sucks.

Now let's consider IDEA.

How about we take two minutes and consider that IDEA is a developers tool, not an end users program? Visual Studio.NET isn't exactly the smallest and snappiest program either. But both it and IDEA provide a lot of features that DEVELOPERS need. The tradeoff for this power and flexibility is high memory requirements. Since you don't get something for nothing, deal with it.

I can, on a 2.1GHz Thoroughbred B, watch it draw menus, all widgets on resize, paint text when scrolling, and construct dialogues when you load them.

I think you need a new graphics card or something. I run a PIII 733 w/512MB of RAM and a GeForce2 graphics card and I have NEVER seen GUIs that slow. If you can watch things paint on the screen, then there is a serious problem with your graphics card. Either that or your simply a troll who likes to spread FUD.

HAND.