OK.... *cracks knuckles*...
#3 - If you were a more "regular" reader of these boards you would have seen me defend Gosling on multiple occasions. I attacked him on this occasion because of my disgust for his arrogance and propagation of misinformation.
"...what is wrong w/ Java or EJB (Enterprise Java Beans)."
Well, for starters, it sucks any hope of scalability from a project. Please, find me a SINGLE project that uses EJB and is even mildly scalable. EJB creates projects that scale about as well as VBCOM+ASP, but are marketed for solutions that demand much more.
I've written MANY applications that followed J2EE and that used EJB, and while some of my pure J2EE apps ran quite nicely, the EJB solutions consistently failed performance wise. It's a case of a design paradigm taking precedence over reality. In an effort to achieve some kind of holy-grail of OOP and modular design, EJB makes it nearly impossible to create useful applications.
I didn't elaborate on my comments originally because I was both in a rush, and have comment on EJB and J2EE extensively before.
"...If it wasn't for Java, we wouldn't have C#."
Why? C# is a language based off C++ just as much as it's based off Java. In fact, I would say it's *more* based off C++ than Java. Consider that C#'s features (with the exception of indexers and attributes) all existed in C++. Many of them (indexers, attributes, operator overloading, unsafe code, etc) didn't exist in Java.
"...but Java really did drive the MS developers to develop a robust managed platform for RAD development."
Read "Breaking Windows" by David Bank to discover the real motivations behind the creation of the .NET Framework. You are incorrect.
"Second, do you even know a damn thing about EJB. Again its was one of the first in its class. ... Again, this was simply a step in the right direction."
EJB is not a server side scripting language. It's a way of encapsulating the data tier into objects, and treating data as objects instead of relational rowsets. It attempts to solve the problem of using a relational database to solve hierarchical problems. So, yes, I DO know a lot about EJB. How many solutions have you built with it?
"u make stupid-ass comments like "Gosling, and whoever designed EJB, should be put on an island and left to eat each other"..."
Perhaps somebody needs to check their humor-detector more often. It was a joke.
#6 - "And just how many programming languages have you authored that are currently used by more than one million developers?"
Ah, argument from authority... yes, a wonderful logical fallacy. Couldn't it also be possible that the very *reason* that Gosling is either staying ignorant or lying about .NET is because he has such a great ego-stake in his accomplishment? Just as some scientists become overly attached to their theories, some programmers become overly attached to their creations.
|