Yep, GP is a moron. Confirmed. Adobe tools are dead simple.

You sir, are full of misinformation. When you set Swing to use native LaF, it actually uses the system's own drawing of the widgets. That's true on Windows, Mac and Linux/GTK+. Has been for years. Only in certain areas (e.g. the file dialog boxes) can you tell that it's not native, because of the layout and functionality, not the LaF.

Yes there is, it's called RTSP/RTP and it's well-supported by VLC and QuickTime (and by extension their browser plug-ins). http://en.wikipedia.org/wiki/Rtsp

Agreed. Google's algorithm was the best when it came out, but I get the feeling more and more these days that we can do so much better! Fact is, Wikipedia is a more useful source of information than Google for around 1/3 of my searches these days. That's saying something.

That's not it. Instant is annoying because it's implemented poorly from a UI perspective. It jarringly changes the whole layout of the site in a split-second. That's just patently bad UX right there; it's no wonder so many people get annoyed at it. AAMOF most people I ask hate Instant. But they don't know that it can be turned off, so they simply accept it. The only reason only "power" users don't use it while everyone else does is because they are the only ones willing to hunt and peck in order find the "OFF" button.

I don't see how this is a real issue. If you filter for Audio files, that's all you'll get. No danger of viruses there.

Actually LimeWire is great for downloading obscure individual mp3s. This is possible because of the fact that not only the file-sharing itself, but also the search, is peer-to-peer. IMHO this means it is still a better "Napster replacement" than Bittorrent, in the sense that it allows you to explore music rather than simply download it en masse.

I actually downloaded Solaris just to try the CDE experience and see what I was missing. It was very purple with a Windows 3.1 flair and a kind of cool dock. Go for it!

except for the fact that writing "(num1==5 && num2==6)" is arguably easier to read than "(num1 == 5 && num2 == 6)", because white space is only used between expressions and not within them.

whoosh

You *can* write such code, but how long will it take you to build up equivalent APIs in a low-level language that these higher-level languages give you out of the box, taking into account the time needed to eliminate bugs? Here's a hint: it took those multiple companies' worth of advanced programmers over a decade to get to that level.

It's almost as if you exhibit a polar extreme case of Not Invented Here syndrome. Just because you *can* do something does not make it a good or practical solution to real-world problems.

don't forget the chance of identical twins...

Ahaha brilliant!!

don't you mean in 4 years from now? 6*5 != 27...