Java Swing versus Adobe Flash/Flex
This is really a stupid test, but I'm showcasing this just to give Adobe a little hint. This my JMC based video player playing four FLV encoded videos versus playing one FLV video in the Adobe Media Player. A lot of memory is being used by the AMP streaming logic, syndication system, image cache, theme system, animation engine and such but the memory usage is still pretty spectacular. But that's not the most shocking issue. The CPU usage is for some absurd reason in the same ballpark. Give or take a few ballparks in scientific accuracy.
I should point out that my application drops frames like crazy and that the event system is unbearably slow. So to be fair, the JMC based system is only two or three times faster (wild guess) on my single core CPU. And for some reason the Adobe player uses quite a bit of CPU while doing nothing, so maybe there is some background process screwing things up. But again.. stupid.. non-scientific test and total FUD factor. Also, if I use the Substance Graphite look and feel, JFC/Swing will need another 25Mb of memory.
If only Sun management could make up their damn minds about the future of this technology. People like me just love pissing away months of work based on bullshit statements from incompetent people. I'm playing around with a C# based WPF player as well just to showcase my hostility towards the Sun desktop division. I sometimes wonder if Sun has four competent people fixing bugs and a boatload of college students with straight A's in Procrastination 101. Take a shit or get off the potty. Java One PDFs seems to be fictional literature rather than technical documentation. Like, I'm a nobody and all, but come on. How can Sun's desktop division call themselves competent when a publicly announced API with public documentation is over two years old and still not available in any form ? Because it's not called JavaFX Media Components. Or is Java just a PR label now ?
When I get a more powerful computer I will try nine and sixteen videos. The current setup uses 53 threads (JMC has parallel scalability), so I wonder what I will see then. I'm sort of worried that threading overhead and IO might become a problem if I push this to the extreme. But if Java can handle my J2EE code, then this should be a cakewalk.
Check out Jan Erik Paulsen on Twitter.